Switching software

Before switching software, test the export you expect to rely on

Find out whether files, comments, relationships and history will survive a move before cancelling the old service.

Before switching software, test the export you expect to rely on — editorial illustration
Original editorial illustration by KTB Consult. Image details

Start here

Export a representative sample, inspect it and test the destination import before committing to a move. A downloadable file may preserve only part of the original system. Keep the old service available until essential records and workflows have been checked.

Inventory the information, not just the records

Start with the things the business must keep using: active tasks, customer-facing pages, files, comments, dates, owners and important history. Add relationships such as which file belongs to which task. A list of task names can look complete while losing the discussions that explain the decisions behind them.

Separate business-critical records from convenient extras. Assign an owner to each essential group and decide how they will judge a successful transfer. Do not put confidential customer information into a new trial account until the appropriate access and data-handling checks are complete.

Read the export scope carefully

WordPress.com explains that its content export contains posts, pages and comments, while themes, customisations and plugins are outside that content file. It also explains how media is handled. A content export should therefore not be treated as a complete copy of a working website.

Atlassian documents different Trello export formats, with differences for comments, archived cards and attachments. It also says that exporting JSON or CSV does not provide a built-in way to recreate a Trello board by importing those files. These examples show why the phrase data export is only the start of the investigation. Read the exact scope for your product, plan and destination.

Build a sample designed to reveal missing pieces

Choose a small sample containing one ordinary record and one awkward case: an archived task, several comments, multiple attachments, a custom field or a linked item. Export it using the account and permissions you will actually have on moving day. Open the result in a suitable viewer and compare it with the original.

Then try the destination import in a test area. Count the essential records and inspect a few by hand. Check dates, special characters, ownership and whether attachments are real files or links back to the old service. A link that works while you are logged in may stop working after the old account is closed.

Plan a reversible cutover

Write a cutover checklist with a final export time, an owner for each validation step and a way to record changes made during the move. If both systems stay editable without a rule, they can diverge before the team notices. Tell colleagues which system is authoritative at each stage.

Retain the original export securely and keep a note of its date and scope. Before cancelling the old service, verify the essential workflow, required records, files and access rights in the destination. Retention obligations vary by business and location, so apply your organisation’s requirements rather than an arbitrary deletion date. A successful migration ends when the team can reliably use its information, not when a progress bar reaches one hundred per cent.

ItemCheck in exportCheck after import
Records and datesCounts and representative samplesCompleteness and date meaning
Comments and historyIncluded or explicitly excludedUseful context retained
FilesActual files versus account linksAccess without old login
RelationshipsOwners and linked recordsCorrectly reconnected

Sources and further reading

Source details checked 2026-11-18. Product terms and availability can change; check the relevant seller or provider before ordering.

Editorial guidance, not a claim of hands-on testing. See our editorial policy for how we research guides. Our approach