internet

Export your data before changing or closing an online service

An export is a useful step toward independence from a service, but a downloaded archive is not automatically a working replacement. It may contain several formats, omit some account information or require another application to interpret it. Plan a small migration test before closing the account that currently holds your usable data.

Define what you need to carry forward

List the practical outcomes you want: keep photographs in their original quality, retain contacts, search old messages or continue editing documents. Those outcomes may require different export formats. A screenshot of a contact list preserves appearance but is poor input for a new address book. A static document preserves a reading copy but may not preserve every editing feature.

Decide what history matters. Comments, versions, labels, attachments and ownership details may be important for one workflow and irrelevant for another. Read the service's export documentation and record any exclusions. If a feature is not described, test it with a small sample rather than assuming it is included because the archive is large.

Request a manageable export

Google's data-download guidance describes exporting supported account data, selecting products and choosing an archive arrangement. It also warns that an archive stored in an account you intend to delete must be moved elsewhere first. The general lesson is to treat the export destination as an independent part of the migration plan.

If the collection is large, start with one relevant product or a smaller archive size where the service offers that choice. Confirm how you will receive access and how long the download remains available. Use the service's known account page for the request. An unexpected email offering a ready-made archive deserves verification before you follow its link.

Protect the downloaded collection

An export can concentrate years of information in one place. Store it where only authorised people can access it and use the supported protection available on your device or storage service. Avoid uploading the whole archive to an unfamiliar conversion website merely because one file is difficult to open. Resolve the format question before exposing the contents.

Create a simple inventory of archive names, dates and covered products. Do not rename internal files indiscriminately before understanding how the archive is structured. Some collections use accompanying metadata files to explain the content. Keep an untouched original and work from a copy while exploring formats or testing an import.

Test a representative sample

Open examples from different parts of the collection. For photos, check older and newer images and any associated dates that matter to you. For messages, check attachments and a long conversation. For contacts, inspect entries with several phone numbers, unusual characters and notes. A sample that includes only easy records can miss the problems most likely to matter later.

If moving to another service, import a small batch first and compare the result with the original. Check record counts, duplicate handling and format changes. Be careful about repeating a full import after an error, since some tools may create additional copies. Record the result and adjust the process before scaling it to the remaining data.

Keep access until the move works

Do not close the old account while the new workflow is still uncertain. First verify sign-in to the replacement, important data, recovery arrangements and any services that depend on the old email address. An account may also be used for subscriptions, shared documents or sign-in to other applications; those dependencies need their own transition.

When the migration is complete, retain the protected archive according to your needs and remove temporary copies from shared or borrowed devices. Record known limitations so future you understands what was preserved. A successful exit is one where the information is usable, its protection is understood and no essential workflow silently depends on the account you closed.

Sources and further reading

This original guide was prepared with AI assistance. Examples are illustrative. The edition date is an assigned date in this 2026 catalogue. See our editorial policy and report a correction.

Privacy & cookies

This edition does not load advertising, analytics, social tracking widgets or optional cookies. Search runs locally in your browser. Hosting security may use necessary technical data as described in our privacy policy.

Read the Privacy Policy · Read the Cookie Policy