Google Gemini Tests Import AI Chats and 2K 4K Image Exports with Likeness Control

Google’s Gemini appears to be testing a suite of features that, if released, would lower the biggest practical barrier for people switching AI assistants: moving months — or years — of conversational context into a new platform. Early sightings inside Gemini’s UI show an “Import AI Chats” entry, higher-resolution image download presets (2K and 4K), and a new “Likeness” setting that links to video verification tools. These signals, first published by TestingCatalog and picked up independently by outlets including Android Authority and Android Central, point to a deliberate push from Google: reduce switching friction, improve creative output quality, and add provenance controls for synthetic media — all at once.

Background​

Since conversational assistants became mainstream, one of the unspoken lock-ins has been contextual stickiness. Power users, teams, and hobbyists accumulate threads that contain research notes, code diffs, editorial drafts, contract details, or persona-specific prompts. That information is the currency of productivity inside a given assistant: it’s not just messages, it’s memory. Recreating that contextual wealth when moving to a rival assistant is tedious — and the friction is a major reason people stick with the first assistant that “knows” them.
Multiple outlets independently traced the new Gemini controls to screenshots and internal builds surfaced by TestingCatalog. The reported flow is straightforward: export a conversation archive from the source assistant (for example, platforms that already support exports like ChatGPT), then upload the archive into Gemini’s import control for ingestion. The import action is shown as a beta feature in the snapshots — which means it’s under development, not yet publicly rolled out, and subject to change.
At the same time, testers spotted image download toggles labelled for sharing and printing at 2K and 4K resolutions, and a Likeness settings entry that routes to a video verification tool — a likely step toward addressing concerns about AI-generated media that imitates real people.

---

Why chat imports matter: the economics and UX of context​

Large language models are inherently contextual. The more relevant history they have about a user’s ongoing projects, the fewer prompts are needed to continue the work. That produces two practical effects:

• Reduced friction for ongoing workflows — Legal briefs, iterative code refactors, research threads, and long-running personal planning are all easier to maintain when the assistant has prior exchanges to reference.
• Behavioral lock-in — Users default to the assistant holding their accumulated context because losing it costs time and momentum.

This is not theoretical: analysts and reporters have documented how quickly conversational AI captured mass audiences (ChatGPT reaching 100 million monthly users within months of launch is a widely-cited growth benchmark), and how habits form once people invest effort into an ecosystem. By enabling imported conversation histories, Google would be attacking that very stickiness.
Advantages for users and teams, if Gemini executes well:

• Immediate access to past reasoning, decisions, and artifacts.
• Faster onboarding for team members switching to Gemini.
• Reduced duplication of effort — no need to re-run research or re-annotate documents.
• Better continuity when tools are chosen for specific integrations (Search, Android, Workspace).

But the value isn’t only user-facing. For Google, import capability is a growth lever: make switching friction negligible and the marginal cost of trying Gemini drops substantially.

---

How the reported chat-import flow appears to work​

From the screenshots and write-ups circulating in testing reports, the import flow follows a simple path:

• The user triggers “Import AI Chats” from Gemini’s attachment or "+" menu.
• A popup instructs the user to download an export/archive from their existing assistant (many services already offer export options).
• The user selects and uploads the exported archive to Gemini.
• Gemini ingests the archive, reconstructs threads (text and, where possible, embedded media), and surfaces continued chats in the user’s activity log.

Two practical constraints deserve emphasis:

• Export formats vary: some services deliver plain HTML/JSON archives, others offer richer packages. Compatibility and fidelity will hinge on standardization or on how tolerant Gemini’s importer is to variant formats.
• Media and attachments: many exports do not include uploaded files inline; they may reference filenames without embedding the binary. Accurate migration of images, PDFs, or code attachments may require additional steps.

OpenAI’s ChatGPT already exposes a data export feature (users can request a ZIP containing conversation files), so a realistic import path for ChatGPT-to-Gemini migration is technically feasible. TestingCatalog’s screenshots suggest the import modal in Gemini expects a user-provided archive rather than a direct account-to-account transfer; that’s simpler to implement but leaves the user doing the export step.

---

Fidelity is the linchpin: what matters for a usable migration​

An import feature is only as valuable as its fidelity — how faithfully it reconstructs conversations and context. Key technical factors:

• Chronology and threading: can the importer preserve message order, metadata (timestamps, role labels), and threaded sub-conversations?
• Multimodal content: will images, PDFs, code snippets, and attachments appear inline, or as separate files with broken references?
• System prompts and metadata: many power workflows include system messages or “persona” prompts. Preserving those is essential for continuity.
• Message truncation and format changes: long outputs, tables, or formatted markdown need robust parsing to avoid corruption.

If Gemini reconstructs threads accurately — preserving attachments, channeling metadata, and maintaining chronology — the result will feel seamless. If it mangles formatting, loses files, or flattens threads into a single blob, the feature will be of limited practical use and create a secondary cleanup cost.

---

Privacy, training, and governance: the unavoidable complications​

Imported conversations are rarely innocuous. Chat archives often contain sensitive prose: client notes, credentials, financials, internal roadmaps, or even API keys. The testing reports indicate that imported conversations may be saved into the user’s Activity log and could be used to improve services — language that raises immediate privacy and governance questions.
Three layers of concern deserve attention:

• User consent and transparency: users need clear prompts explaining what will be imported, where it will live, and whether it will be used for model training. The import dialog must avoid fuzzy language and give explicit, granular choices.
• Client-side controls: best practice is to do as much processing as possible on-device or provide local-only import modes. If uploads are done to Google servers, users must be able to decide whether imported content is used for product improvement or model retraining.
• Enterprise governance and audit: organizations will require admin-level controls, policies that block or log imports, and audit trails showing who initiated imports and when. Compliance teams will want DLP scanning and the ability to reject or quarantine imports that violate company policy.

Regulatory context matters here. The GDPR’s Article 20 outlines a data portability right — the legal principle that users should be able to receive their personal data in a structured, commonly used, machine-readable format and transmit it elsewhere. That principle supports the idea of import/export, but it does not undercut the need for safeguards where sensitive personal data or third-party rights are involved. Enterprises in regulated sectors (healthcare, finance, defense) will want to treat imports as potential exfiltration events unless there are robust safeguards.
Finally, there’s a subtle risk: imported material that the user does not own or have rights to (e.g., third-party proprietary content, copyrighted media) may introduce legal exposure if the receiving platform ingests and uses that material for model improvements without proper licensing or consent. Google will need to make the legal treatment of imported content explicit.

---

Security specifics: what organisations and users should worry about​

• Credential leakage: many engineers paste API keys, tokens, or passwords into chats during troubleshooting. Exports often capture this verbatim. Before importing, users must sanitize archives for secrets.
• Malicious payloads: imported files could include scripts, macros, or malformed media intended to exploit parsing vulnerabilities. Import parsers must be hardened and sandboxed.
• Data residency and encryption: organizations will ask where imported data is stored, how long it is retained, and whether it is encrypted at rest and in transit.
• Access controls: who in an organization can import chats into shared or managed Gemini workspaces? Role-based controls and approval workflows will be mandatory for enterprise adoption.

---

Image-resolution upgrades: 2K and 4K downloads​

Alongside chat imports, testers saw Gemini image export presets for 2K and 4K. That’s significant for creative workflows: upscaling outside the app used to be a necessary step for teams producing print or high-resolution assets.
Why this matters:

• Native 2K/4K downloads reduce the need to chain multiple tools (generator → upscaler → export).
• Labeling choices such as “best for printing” indicate a positioning toward professional or marketing use-cases.
• If coupled with color profile options or layout templates, Gemini could become part of a streamlined content pipeline for small marketing teams and creators.

Caveat: advanced print workflows also require CMYK profiles, bleed/margins, and vector export — capabilities that are not the same as simply offering higher pixel counts. High-resolution raster output helps, but it’s not an automatic replacement for specialized design tools.

---

Likeness controls: provenance and synthetic media detection​

A reported “Likeness” entry in Gemini settings routes to a video verification page. The naming echoes industry movements to detect, label, and provide recourse for synthetic media that impersonates people.
What this could be:

• A detector that flags whether an uploaded clip appears to be AI-generated.
• A reporting path for creators to request takedowns or for the platform to surface provenance metadata.
• An interface for users to opt into or out of likeness protections, or to register approved images/voice signatures.

This area is still under-specified in the leaks, but integrating a likeness/verification control into a major assistant is sensible given rising regulatory and public pressure to manage deepfake risks. If Google builds expressive, user-centric controls here (including appeal processes and creator protections), it will set a higher bar for responsible multimodal AI. If not, the feature risks becoming performative.

---

Competitive stakes: how importability could reshape market dynamics​

Streamlined migration affects competition in a single, decisive way: it lowers the cost of trying an alternative. When users can import their existing context, they can test a new assistant’s integrations (Search, Workspace, Android) without losing their memory.
Potential outcomes:

• Faster user trial cycles: more people will test Gemini while maintaining work continuity.
• Increased churn risk for incumbents: rivals that lack easy import/export will feel more pressure to add portability features.
• Greater scrutiny from regulators: moves that intentionally reduce lock-in could be seen positively by competition authorities, but data handling and training practices could attract regulatory attention.

The broader point: portability isn’t neutral. It changes the architecture of user decisions. If Google pairs import capability with better multimodal outputs and robust safety controls, that combination becomes a potent conversion strategy.

---

Practical guidance: how to import safely (for power users and admins)​

If you’re considering importing conversations into Gemini once the feature arrives, follow this checklist to reduce risk:

• Export only what you need. Use a targeted export (single-thread or date-range) where possible.
• Sanitize the archive:
• Remove or redact API keys, credentials, and personally identifiable information.
• Strip attachments you don’t want migrated.
• Scan with DLP tools before upload. If you’re in an organization, route exported archives through centralized scanners.
• Check the import preview. If Gemini shows a reconstruction preview, verify chronology and media mapping before finalizing.
• Use a local-only import if available. Prefer client-side ingestion modes that keep material from being used for training.
• For managed accounts, require admin approval. Use an approval workflow or quarantine import until compliance reviews occur.
• Keep an audit trail. Document who exported, sanitized, and imported the archive and why.
• Test with a small subset first. Confirm fidelity before moving entire histories.

These steps should be baked into company policy — importing entire chat archives without review is a governance risk.

---

What could go wrong: key failure modes​

• Poor fidelity: messy imports that break threading or lose attachments will create cleanup costs and user frustration.
• Data misuse: ambiguous training-consent language or automatic use of imported data to improve models could trigger privacy complaints or regulatory scrutiny.
• Security gaps: if import parsers accept malformed files, they could open attack vectors.
• Legal exposure: imported copyrighted content, or third-party data, may create licensing or copyright liabilities if used by the receiving platform.
• False sense of continuity: users might trust an imported “memory” in ways that are unsafe (e.g., relying on out-of-date legal or financial advice preserved in a thread).

---

What to watch for next​

• Official documentation and rollout notes from Google: these will clarify supported formats, retention, and training opt-outs.
• Admin controls for Gemini Workspace: enterprise readiness will depend on import governance and audit trails.
• File format standards: any move toward structured conversation formats (conversations.json, structured archives) will help portability across vendors.
• Fidelity benchmarks: independent tests that import real-world threads (with sanitized data) will reveal whether Gemini can truly continue a conversation or just archive it.
• Regulatory responses: privacy authorities may review any language about training-use of imported data; watch for guidance or complaints.

---

Bottom line​

The reported Gemini features — chat imports, higher-resolution image exports, and likeness verification — represent a coherent strategic push: make it easy to try Gemini, improve creative outputs, and position the assistant as a safer place for multimodal work. The user upside is tangible: frictionless continuity unlocks real productivity gains. But the operational and legal complexity is real, and execution will determine whether these features empower users or open new liability pathways.
If Google ships a robust importer with clear, granular privacy controls, local import options, and enterprise governance primitives, Gemini could meaningfully lower the switching cost for serious users who’ve built long-running knowledge assets in rival assistants. If Google treats imports as a simple upload-and-ingest feature without robust safeguards, the upside will be limited and the trust gap may widen — especially among teams and organizations that handle regulated or sensitive information.
For now, the feature is in beta testing and subject to change. Power users and IT teams should prepare policies for safe export/import practices, insist on auditability, and watch vendor documentation closely when the feature becomes available. The promise of genuine portability in consumer AI is exciting — but it’s only as valuable as the controls that protect the people and organizations who rely on these systems.

---

Source: findarticles.com Google Tests Easy Chat Imports For Gemini

Google’s Gemini appears to be quietly testing a small but strategically significant set of features that could make it far easier for people and organizations to switch away from rival chatbots — or to consolidate multiple assistants into a single workspace. The most notable of the new controls is an Import AI chats beta flow that surfaces in Gemini’s attachment/menu UI and promises to let users upload exported conversation archives from other assistants so Gemini can ingest and resume existing threads. Early sightings also show higher-resolution image-download presets (2K and 4K) and a new Likeness control that seems tied to video verification and synthetic‑media provenance. These features are behind a feature flag or only visible in internal/test builds so far; independent testers and reporting teams have been unable to reproduce them consistently across accounts.

Background​

The underlying problem this feature targets is simple but powerful: contextual lock‑in. Users who keep long‑running threads — research projects, coding sessions, editorial drafts, client work, or personal knowledge stores — effectively make those assistants a form of stateful workspace. Losing that accumulated context is costly, and that cost is a major reason people stay with the first assistant that “knows” them. By offering a direct import path, Gemini would reduce the friction of switching and make trialing or consolidating AI assistants a more realistic option for power users and teams.
TestingCatalog first surfaced UI screenshots and a short workflow description; PCMag UK and other outlets picked up on the leak and confirmed the controls in early builds, but note that the import option remains hidden for most users and appears to be unfinished. The import flow is shown as a beta feature in the snapshots, which is consistent with it being actively developed rather than broadly released.

---

What the leaked flow looks like​

How the control appears in Gemini​

• The new entry shows up under the plus/attachment menu in Gemini’s home UI as Import AI chats, with an icon that resembles a chat bubble. It sits beneath options such as NotebookLM access. Activating the entry opens a popup instructing the user to download an archive from their source assistant and then upload it to Gemini for ingestion.
• The popup text in the leak cautions that uploaded data will become part of the user’s Gemini activity and may be used to train Google models in the future. That message signals a data‑use policy that is explicit — but also one that will matter greatly to privacy‑conscious users and enterprise buyers.

Supporting features spotted alongside imports​

• Image download presets labeled 2K and 4K suggest Google is preparing higher‑fidelity export options for generated images, likely intended for production sharing and printing.
• A Likeness setting appears in the leaked UI and seems connected to video‑verification or identity‑provenance tooling — possibly related to Google’s broader work on synthetic‑media provenance and YouTube’s Likeness controls. The precise function is not included in the screenshots.

---

Why chat imports matter (and the stakes for users and vendors)​

Moving conversation histories between vendors removes one of the most concrete forms of switching friction in conversational AI: the loss of accumulated context. That matters for multiple user segments:

• Power users and creators: Ongoing projects (manuscripts, design revisions, codebases) are often persisted in chat threads. Being able to resume a thread in a new assistant saves time and preserves nuance.
• Teams and small businesses: Importing chat histories can shorten onboarding time when migrating tenants or testing alternative assistants for workflows that involve Drive/OneDrive/Slack attachments and iterative edits.
• Enterprise buyers: Reduced switching costs change procurement dynamics: vendors will compete more on features, integrations, and governance rather than relying on sticky context to keep customers locked in.

From a vendor strategy perspective, enabling imports is a lever for growth. If Google can offer an easy import path and pair it with Gemini’s distribution across Search, Android, Chrome, and Workspace, the marginal cost for a user to test or adopt Gemini falls substantially. That’s why a migration tool — simple as it sounds — can be a meaningful competitive differentiator.

---

Technical realities: what an importer must do to be useful​

An import button is the easy part; fidelity and compatibility are the harder technical problems. A usable importer must address:

• Format parsing and schema mapping. Export formats vary widely (JSON/HTML archives, ZIP bundles with metadata, platform‑specific structures). A robust importer needs to accept multiple schemas and normalize them into Gemini’s conversation model. OpenAI (ChatGPT) already offers a downloadable ZIP with JSON and HTML artifacts, which makes a ChatGPT→Gemini import technically feasible if Google supports those formats.
• Thread reconstruction. Long-running or multi‑branched chats often contain forks, nested replies, and participant metadata. Preserving chronological order, role labels (system/user/assistant), and threaded structure is essential to retain the thread’s utility.
• Media handling. Many exports either embed binaries or provide references to separate files. Images, PDFs, code attachments, and linked documents must be re‑attached or re‑hosted to remain useful inside the destination assistant.
• System prompts and hidden metadata. Power users rely on system messages, persona prompts, and other non‑visible context items. If those aren’t preserved, the assistant won’t behave consistently after import.
• De‑duplication, sanitization, and format conversion. Exports may include platform‑specific markup, custom tokens, or third‑party plugin outputs that require cleaning before ingestion.

Early leaks suggest Gemini’s import expects a user‑provided archive rather than an account‑to‑account transfer — a pragmatic early approach that minimizes cross‑service integrations but makes the user responsible for export steps. That flow is straightforward to implement, but it also places the burden of fidelity on the importer’s parsing logic rather than on automated transfers.

---

Privacy, training, and governance: the red lines​

The leaked popup explicitly warns that uploaded conversation archives will be stored in Gemini activity and may be used to train Google models. That single line changes the calculus for many users and organizations.

• Users who assume “private import”: If the importer stores the uploaded conversations and allows them to be used for training, many privacy‑sensitive users will balk. Individuals and businesses that handle regulated or client data need clear contractual terms and controls — ideally a non‑training option or administrative blocks on tenant imports.
• Enterprise governance: IT admins will require audit logs, role‑based controls, and DLP (data loss prevention) tools that can inspect exported archives before import. Enterprises commonly prohibit uploading PHI/PII or client data to consumer services without explicit contractual safeguards.
• Regulatory scrutiny: Data‑protection frameworks and regulations that favor portability (e.g., data‑protection principles in many jurisdictions) may support portability features — but they also raise obligations around consent, notice, and cross‑border data movement. Vendors will need to clarify processing locations and retention policies.
• Transparency and trust: If Google intends to use imported user data for model training, that policy must be transparent and offer options: opt‑in training, opt‑out, or enterprise non‑training contracts. Otherwise, the feature may be marketed as a convenience while simultaneously entangling users’ private archives in future model updates. Leaked copy suggests Google warns users, but specifics are absent from the screenshots. Treat the training claim as not yet fully specified pending an official release.

---

Interoperability: where the unknowns still matter​

Key unknowns make the feature’s practical value uncertain:

• Which source platforms will be supported? The screenshot instructs users to “download your chat history” from another platform but does not list supported sources. While OpenAI/ChatGPT provides a ZIP export mechanism, not all major services expose easy, standardized exports that preserve conversation structure and attachments. The ecosystem lacks a de‑facto standard for assistant exports today.
• Which file types will Gemini accept? The leaked UI does not specify accepted archive or file formats. Will Gemini accept ChatGPT’s ZIP out of the box? Will it support HTML, JSON, or a proprietary schema? Those details will determine real‑world interoperability.
• Will exports be two‑way? The leak shows imports into Gemini, but it’s unclear whether Google will allow users to export Gemini conversations in a format that rivals can consume. Two‑way portability would be a more durable solution for market competition; one‑way lock‑ins disguised as “imports” would simply shift stickiness around. These are open questions and should be treated as unverified until Google publishes product documentation.

---

Security and compliance considerations for IT teams​

If your organization depends on long‑running chat threads, start treating exported archives as data assets that require the same controls you apply to other archives.

• Pre‑import checklist (recommended):
• Scan exported archives with corporate DLP tools to detect sensitive identifiers, PHI, or restricted content.
• Confirm the source export includes sufficient metadata (timestamps, thread IDs, role labels) to make reconstruction meaningful.
• Validate that the target service offers non‑training or enterprise training controls if regulatory or contractual constraints exist.
• Ensure audit trails record who performed the import and what was uploaded.
• Stage imports in a sandbox environment before doing tenant‑wide migrations.
• Policy updates: Update Acceptable Use Policies to define when and how exported chat data can be uploaded to third‑party vendors. Treat assistant exports like other data transfers: require approvals, scanning, and, where appropriate, encryption at rest.

---

User recommendations: how to prepare if you plan to test Gemini​

• Export a representative sample of your chat history now, and store it under version control or in an archive that tracks provenance. That will let you test fidelity without risking production data.
• Verify how well third‑party import tools (where available) or vendor imports preserve:
• Thread chronology and nested replies
• Inline code blocks and syntax highlighting
• Embedded media and attachments
• System prompts and persona instructions
• If you’re a creator who relies on image outputs, test the 2K/4K presets (once they arrive) to confirm color, metadata, and licensing metadata survive export. High‑resolution presets are promising for production pipelines but not sufficient without clear licensing and rights management.
• Demand contractual guarantees for non‑training on sensitive data or explicit opt‑out controls for training use before migrating tenant assets en masse. The leaked UI warns that data may be used for training — don’t assume otherwise.

---

Competitive implications: how this could reshape assistant churn​

If Gemini ships a robust importer that handles the real complexities listed above, it reduces the marginal cost of switching and encourages experimentation. That will exert pressure on other vendors in two ways:

• They’ll need to offer equivalent import/export flows to remain competitive for power users and enterprise customers.
• Vendors may compete on governance and portability guarantees (non‑training clauses, tenant admin controls, audit logs) rather than purely on model quality.

In short, portability moves the battleground from “who keeps you locked in” to “who provides the cleanest migration, the best controls, and the most useful integrations.” That’s a healthy market dynamic for users — provided portability is implemented transparently and with enterprise‑grade safeguards.

---

Risks to watch and how vendors could get this wrong​

• Surface‑level portability: A simple import that recreates message text but drops attachments, system prompts, or threading will feel useful at first glance but fail power users. Fidelity matters more than checkbox functionality.
• Opaque training use: If imported data is automatically added to training corpora without granular opt‑out or enterprise non‑training contracts, organizations will be reluctant to migrate sensitive material.
• False sense of security: Users might assume imported conversations are sandboxed or immutable; without robust audit trails and retention policies, imported content could be retained indefinitely or shared across internal features in ways users did not expect.
• Regulatory and contractual exposure: Uploading client or regulated data to a third‑party service without explicit contractual protections could violate legal obligations or ethical duties.
• Fragmented standards: Without a shared export format or metadata standard, the importer will always be playing catch‑up as vendors change their export schemas. The market would benefit from an industry effort to define a portable conversation exchange format.

---

The Likeness control and synthetic‑media provenance​

The leaked Likeness setting is tantalizing but undefined. It could be a way for users to register or assert identity control over generated media (for example, preventing others from producing videos that misuse someone’s likeness), or it could be a verification flow that ties a user’s identity to generated content to support provenance. Given rising concerns about deepfakes and identity misuse, a built‑in provenance or verification control would be a meaningful addition — but the screenshots do not include detailed behavior, and linking it to existing YouTube tools is speculative at this stage. Treat the Likeness feature as an emerging capability worth watching rather than an established product.

---

What we still need from Google (and other vendors)​

For portability features to be genuinely useful and safe, vendors should publish specific documentation that answers:

• Which source platforms and export formats are supported?
• Which file types are accepted, and how will media/attachments be reconstructed?
• Will imported data be used for model training? If so, what opt‑out or non‑training contractual options exist for enterprise customers?
• What audit logs, retention policies, and admin controls are available for tenant administrators?
• Will exports be two‑way so users can leave a vendor as easily as they arrive?

Until vendors answer those questions in writing, treat early UI leaks as a signal of direction rather than a fully specified product promise.

---

Final analysis: promising, but execution is everything​

The idea behind an Import AI chats flow is both obvious and consequential: reduce switching friction and make chat threads portable. The leaked UI and popups suggest Google is thinking about this seriously and pairing it with production‑grade features such as higher‑resolution image downloads and a Likeness control for provenance. Those moves align with a product strategy that leverages Google’s distribution while trying to remove one of the major behavioral lock‑ins users face.
But there’s a significant gap between a visible import control and a migration experience that enterprises and power users will trust. The critical tests are fidelity, privacy controls, and transparent training policies. If Google ships a robust importer with clear non‑training options for enterprise customers, comprehensive DLP hooks, and a documented list of supported formats and edge‑case behaviors, the feature could meaningfully change assistant market dynamics. If instead the import is superficial, opaque about training use, or missing attachment and system‑prompt fidelity, it will be a nice headline with little operational value.
For WindowsForum readers who treat chats as durable workspaces: prepare now. Export representative archives, audit them with your existing DLP and governance tooling, and demand clear contractual terms before attempting tenant‑wide imports. The leak is an important signal that portability is on vendors’ roadmaps — but the real value will be decided by execution, governance, and transparency.

---

Conclusion
Google’s leaked import flow for Gemini is a strategic feature with the potential to reduce one of the thorniest forms of vendor lock‑in in conversational AI: accumulated context. Early evidence shows a promising UI and complementary features (2K/4K image downloads, a Likeness control), but the practical value will be determined by format support, fidelity, privacy/training policies, and enterprise governance controls. Until Google publishes formal documentation and rolls the feature out of beta, treat the reports as the first step in a necessary verification process: test exports now, set governance guardrails, and demand contractual clarity before moving sensitive work into any newly imported assistant environment.

---

Source: PCMag UK Google Gemini Tests a Tool to Help You Switch From ChatGPT, Other AI Chatbots