Switch AI tools: test exports and prepare a migration
A service closure, contract change or incomplete export can disrupt an essential workflow. Prepare an exit while the service still works and demonstrate that the data can be reused.

An export is not a restoration
Downloading a file only proves it was downloaded. Check its contents, open it independently and restore a real use case. Dify documents application exports, for example: inspect the exported scope rather than assuming it.
- Dependencies inventoried
- Restoration tested
- Rollback possible
Prepare an exit without disruption

AI-generated illustration 1. Inventory assets
List source documents, useful conversations, instructions, knowledge bases, workflows, logs and accounts. Separate essential data from optional history. Do not include secrets in exports intended for sharing.

AI-generated illustration 2. Define export scope
Check formats and omissions: attachments, permissions, versions, metadata or indexes. Record volume limits and required access. Preserve identifiers linking objects.

AI-generated illustration 3. Test independently
Open a representative document, conversation and workflow in another application. Compare object counts, encoding, references and attachments. Configuration exports may require rebuilding connections and indexes.

AI-generated illustration 4. Rebuild a pilot use case
Import a small batch in an isolated environment and replay a real task. Compare accuracy, access and cost with existing criteria. Check duplicates and external actions before activating workflows.

AI-generated illustration 5. Organise the switch
Define owner, migration window and handling of changes since the export. Avoid two systems writing simultaneously without synchronisation rules. Retain rollback until validation.

AI-generated illustration 6. Close after validation
Verify migrated data and access, then remove unnecessary old connectors and accounts. Examine applicable deletion procedures and retention duties. Archive the decision and acceptance evidence.
Test the available export format before switching
Dify documents an app package that leaves out linked knowledge bases, service keys and logs. An n8n workflow JSON can retain credential names and IDs or authentication headers. Review an export copy before sharing it. In the acceptance test, rebuild a connection with a test account and check that the expected source documents are available after import.
Put the method to work

Practical case
Export a test workspace containing three documents, useful history and a workflow. Restore them in an independent environment.

Evidence to keep
Keep the inventory, formats, missing objects, restoration time and result of a replayed task.

Make the decision
Cancel only after validating essential assets and a rollback procedure.
Demonstrate reuse after exit
Run this workshop with fictional content. The aim is to open and use data elsewhere, not merely observe an archive file.

Content without relationships
- Input to prepare
- An archive retains documents but loses folders and cross-references.
- Expected result
- Useful links can be reconstructed from retained identifiers.
- If the check fails
- Add a mapping table and verify actual reading journeys.

Unreadable outside the service
- Input to prepare
- An exported item opens only in its original service.
- Expected result
- A usable copy exists in an appropriate independent tool.
- If the check fails
- Test conversion and record losses without describing the original file as portable.

Access after departure
- Input to prepare
- A test account is removed after a demonstration copy was exported.
- Expected result
- Service access is revoked; external copies are handled separately.
- If the check fails
- Check every controlled destination and document copies outside administrative scope.
Decision rule. Accept exit after another person performs a recovery trial. List losses, dependencies and work required to restart.
Evidence of reversibility

Completeness
Essential objects and their references are present.

Reuse
An independent tool opens files and uses their values.

Continuity
A real task works after importing.

Access
Necessary rights are recreated without unintended expansion.
Explore deployment modes
Compare document tools, platforms and local solutions. Test exports for each offer and version.
Hugging Face Models
model library
Hugging Face · US
Visit official siteGoogle Antigravity
coding agent
Google · US
Visit official siteDify
workflow building
LangGenius / Dify
Visit official siteHow is this selection produced?
These profiles are linked to the guide’s subject in our editorial catalogue. Inclusion is neither a ranking nor a performance measurement on your documents. Methodology.
Related tool families
Frequently asked questions
When should I test an exit?
Before making an important activity depend on the service, and after changes to plans or export formats.
Should all histories be exported?
Define what has real utility and authorised retention. A considered inventory avoids moving unnecessary data.
Is a self-hosted solution easy to migrate?
Not necessarily. You must also control backups, databases, files, dependencies and restoration.
The references below expand on the concepts and checks discussed. Scenarios and trial frameworks remain editorial proposals; provider documentation describes its own product rather than an independent benchmark.
Source note
Switching AI tools: prepare the export
Before migration, inventory what must follow: conversations, source files, instructions, automations and access rights. Test a small export and verify that the new service can read its formats; a recovered file is not automatically reusable.
Document what does not transfer, including provider-specific integrations and settings. The EU Data Act addresses certain changes of data processing services, but its scope does not mean every AI application offers complete portability.
Choose a folder containing attachments, a long conversation and specific instructions. Check text, dates, file links and accented characters. Opening the first imported file does not demonstrate that document relationships or colleagues’ access rights survived.
Plan a comparison period: identical questions should retrieve the same useful documents in the new environment. Identify automations to recreate and access reviewers. Protect the export until validation, then apply your retention rules; unmanaged copies make data harder to control.
- Inventory
- Separate business data, settings and work history.
- Trial
- Import a sample before ending the old subscription.
- Reversibility
- Keep a verified copy and transition schedule.
Should the old account be deleted immediately after export?
First validate file readability, access rights and essential workflows in the new service. Export, import and deletion are distinct stages to organise under applicable conditions.
Fictional case — a document assistant
An SME exports documents and instructions, then tests ten files in another tool. Attachments transfer but automations need rebuilding, so the migration schedule is adjusted.
Try the reasoning
The export contains conversations but not the referenced files. Is migration complete?
Reasoning: No: inventory conversations, attachments, settings and rights. Test a sample at the destination before closing the old access.
Primary source : European Commission — Data Act explained



