Practice leaving software before you need to

Define what must survive the move

An exit rehearsal starts with the work, not the export button. List the information a future user must recover and the actions they must still perform. A project might need readable notes, attached files, dates, record relationships and an explanation of who owns the next decision.

Separate those needs into content, behavior and access. Content is the material itself. Behavior is what the application lets you do with it. Access is who should be able to see or change it. This original framework keeps a successful file download from standing in for all three.

Choose a small representative sample

Create a disposable example with no confidential information. Include the structures your real workflow uses: a linked note, a small table, an attachment and one item with restricted access. Write an expected result for each before exporting anything.

Keep the sample small enough to inspect by hand. A thousand identical rows add less insight than one record that uses a feature you depend on. Mark the example as a test so it cannot later be mistaken for a real customer, credential or operational instruction.

Inspect the documented exit, then the artifact

Notion’s export guide warns that reuploading an export does not instantly recreate a workspace. Obsidian documents its notes as local Markdown files. Those are different starting points, but both still require checking whether the next reader can use the material needed for the task.

Use the supported exit route for the actual product and account you are evaluating. Open the resulting sample in its intended destination. Compare the contents with your expected result and record any structure that needs manual rebuilding. A familiar file extension does not establish that the entire workflow survived.

Sources: Notion · Obsidian

Treat protected exports as a recovery process

Bitwarden’s encrypted export documentation distinguishes account-restricted files from password-protected exports with different restore conditions. Proton Pass also documents a specific encrypted export and import route. The important general lesson is to check the required destination, account and recovery material before calling an export usable.

For sensitive categories, keep the rehearsal fictional. Do not upload real exports to a general-purpose assistant to ask whether they look correct. Record how an authorized person would perform the supported recovery without placing recovery secrets in the same shared checklist.

Sources: Bitwarden · Proton

Check who can continue the work

Ask a second appropriate person to follow the sample handoff using only the record you prepared. Can they find the file, identify the current version and understand what remains to be rebuilt? Can they distinguish a source record from an exported copy?

Also inspect access at the destination. A restricted page becoming a broadly accessible file is a change even when every word arrives intact. If the new system cannot reproduce an important boundary, document a different arrangement before moving real material.

Keep a short exit record

Save the product and plan checked, the export route, the sample date, the destination and the known gaps. Assign an owner to repeat the rehearsal when the workflow begins depending on a new feature or when the provider changes the relevant export behavior.

The result should be a decision you can use: the exit is adequate for this task, needs a particular manual step, or remains unverified in a named area. No product needs to win a universal portability contest. It needs an exit path that matches the work you would actually have to continue.