Colour theme
Book a consultation

Testing whether you can move your cloud data

Test whether cloud exports and backups include the records you need, work outside the original service, and support a realistic migration plan.

A person connecting a cable to a portable drive beside a laptop, with a camera and memory cards on the desk.

Your cloud application may offer both an export button and a backup service. Before treating those as an exit plan, test what each produces and where you can use it.

Restoring a record inside the current platform and moving it into a different one are separate requirements. Finding that distinction before renewal gives you time to resolve missing records, conversion work and costs.

Define what another system would need

Choose one business process, such as producing an invoice or retrieving a completed client file. List the information needed to carry it out: records, attachments, relationships between records and any history that must remain available.

Include settings and dependencies that aren’t ordinary files. For example, an exported customer list may omit the workflow that assigns work, the permissions that restrict access or links to documents in another service. The person responsible for that process should help identify the gaps.

Don’t assume every historical item must move into the live replacement. Decide which records need an accessible archive, subject to your retention requirements. Our retention guide can help organize that review.

Compare the export with the backup

Ask the provider to describe supported formats, included data and restore destinations. Can a backup restore only to the same tenant or service? Does an export preserve file versions, relationships and attachments? Who can perform it, and what permissions or licences are needed?

For example, Microsoft 365 Backup documents restore operations for SharePoint, OneDrive and Exchange data. That restores data within Microsoft 365. It won’t move it into another provider’s application.

Google Workspace’s organization-export documentation sets out administrator requirements, export coverage and exclusions. Read the equivalent documentation for your own service. An export being available doesn’t mean every record or setting is included.

Run a controlled portability test

Agree on a representative sample and a restricted test location. Use made-up or de-identified records where possible. If you need real client data, decide who can use it and where it’s stored before you export it.

Have IT carry out the test without changing or deleting production records:

  1. Export the sample and record the method, date and product version.
  2. Open the files outside the original application’s normal interface.
  3. Check record counts, attachments, character encoding and dates.
  4. Try the agreed process in a test destination or independent reader.
  5. Record missing history, relationships, permissions and manual repairs.

An ordinary spreadsheet viewer will show the values are readable. It won’t tell you whether the next system can import them correctly. Have the business owner check the result, including a few difficult cases such as credit notes, duplicate names or files with multiple versions.

Measure the dependencies and cost

Record how long preparation, export, download, conversion and validation take. Identify any step that needs vendor support, a special licence or a paid migration tool. Ask about volume limits and the export window before cancellation.

Put the estimate in Canadian dollars, and note any supplier charges quoted in another currency. Include staff time, temporary storage and a period of overlapping subscriptions. Avoid projecting a full migration from one small sample without checking service limits and data volume.

Keep recovery and exit plans separate

The Cyber Centre’s backup guidance recommends encrypted backups, restricted access and regular restoration checks. Continue those checks alongside portability testing. A readable export isn’t necessarily a complete recovery copy.

Secure the export and any temporary administrator access. Record who can use the files, how encryption keys are held and when test copies will be removed. Retest after changes that affect the data model or export process.

Once a move is planned, our cloud-service exit guide covers handover, cutover and cancellation. Build that plan on what the portability test found.


Featured Image Credit