Switching cloud storage providers is more than copying folders from one account to another. A careful migration protects file access, sharing permissions, version history, metadata, backup coverage, and recovery options. This cloud storage migration checklist gives you a repeatable way to plan the move, transfer files safely, verify the result, and review the setup again when your needs or provider terms change.
Overview
A cloud migration can be personal or business-related: moving family photos to a new service, consolidating files after replacing a device, or transferring a small company’s shared workspace. In each case, the main risk is assuming that a completed upload means the migration is complete. Files may arrive without their original folder structure, shared links may stop working, older versions may not transfer, and a synchronization tool may create duplicates instead of a clean copy.
Before you switch cloud storage providers, define what “success” means. A successful migration should leave you with:
- A complete inventory of the files and folders being moved.
- A documented map between the old provider and the new provider.
- Working access for owners, editors, viewers, and other permitted users.
- A clear decision about version history, comments, links, and deleted files.
- At least one separate backup or export before the old account is closed.
- A tested recovery process for representative files.
Provider capabilities differ, so check the current export options, transfer tools, file-size limits, retention rules, and security settings for both services before starting. Do not cancel the old plan or delete its contents until the new environment has been checked and the retention period you need has passed.
For broader planning, compare storage capacity, sharing controls, recovery features, and business suitability in this cloud storage comparison for personal and small-business files.
What to track
1. Build a provider-to-provider inventory
Start with a simple spreadsheet or document. Record each top-level folder, its purpose, approximate size, owner, access group, and migration status. Include folders that are easy to overlook, such as shared folders, device backups, archived projects, application exports, and files stored in a provider’s recycle bin.
Use a mapping template like this:
- Source location: old provider, account, shared drive, or device.
- Destination location: new provider, account, and folder path.
- Owner: person or business account responsible for the files.
- Access: users, groups, roles, and external collaborators.
- Transfer method: direct transfer, desktop sync, export archive, or manual upload.
- Status: planned, in progress, transferred, verified, or excluded.
- Notes: links, versions, comments, encryption, or special handling required.
2. Separate active files, archives, and disposable data
Do not migrate everything automatically. Divide the inventory into active working files, records that must be retained, personal media, device backups, temporary downloads, and duplicates. This is an opportunity to reduce storage use before paying for space in the new account. Keep a record of anything excluded and why, particularly for business or tax records.
3. Record permissions and sharing dependencies
For every important shared folder, note who can view, edit, download, or reshare its contents. Capture important shared links and identify any files embedded in websites, project tools, email templates, or customer instructions. A link copied from the old provider may not work after migration, even if the file itself transfers successfully.
Business users should also record service accounts, automated workflows, application integrations, and former employees’ access. Recreate only the permissions that are still necessary. A migration is a good time to remove outdated access rather than carry it forward by default.
4. Track backup coverage separately from synchronization
Cloud synchronization is not automatically the same as an independent backup. If a file is deleted or corrupted and that change synchronizes everywhere, you may not have a separate recovery copy. Before transferring files, confirm where the additional copy exists, how long it is retained, and whether you can restore it without relying on the old provider.
Use the cloud storage cleanup and backup audit checklist to review old files, backup gaps, and recovery expectations before migration.
Cadence and checkpoints
Before the transfer
- Review the new provider’s capacity, account structure, supported file types, file-size limits, and export or import process.
- Confirm that the destination account has the right owner and recovery email or administrator.
- Export or copy critical files to a separate location. For especially important records, keep more than one accessible copy.
- Pause large edits where practical, or announce a cutover time so people know which system is authoritative.
- Run a small test with different file types, nested folders, shared files, and a file with an existing version history.
During the transfer
Use the least complicated reliable method that fits the data. A provider-to-provider transfer may preserve more structure than downloading and re-uploading, while a local export can provide a useful independent copy. Desktop synchronization can work for ordinary folders, but it requires enough local disk space and careful attention to sync status.
Transfer in batches rather than moving an entire account without checkpoints. Record the batch name, source path, destination path, start date, completion status, and any errors. Watch for skipped files, unsupported shortcuts, changed file names, and conflicts created when two people edit the same document during the move.
Immediately after the transfer
Do not rely only on the provider’s item count. Open a sample of documents, images, videos, spreadsheets, and compressed files. Check that names, folder paths, file sizes, dates, and previews appear reasonable. For a business account, test access using representative roles instead of only the administrator account.
Review the destination’s sharing settings, link permissions, two-step sign-in options, recovery contacts, encryption choices, and activity alerts. Reconnect approved applications one at a time and remove unused integrations.
Weekly or monthly during the transition
While both services remain available, compare new files in the old account with the destination. Resolve edits made during the cutover and keep the old account read-only if the provider supports that arrangement. Maintain a short exception log for files that need manual attention.
How to interpret changes
A lower file count is not automatically a problem: you may have removed duplicates, temporary files, or unsupported shortcut objects. A higher count can also be misleading if the transfer created conflict copies or included hidden application data. Interpret counts alongside folder-level checks, storage usage, error reports, and sample file tests.
Pay particular attention to these warning signs:
- Files are present but cannot open: check incomplete transfers, file corruption, unsupported formats, or permission problems.
- Shared links fail: create new links and update every place where the old links were published.
- Version history is missing: retain an export or archive of the old versions if they are important; a normal copy may preserve only the current file.
- Storage use is unexpectedly high: look for duplicate folders, conflict files, retained deleted items, and duplicated device backups.
- Users see different content: compare group membership, inherited permissions, and individual sharing settings.
- Backups are reported as complete but cannot be restored: perform a real recovery test instead of accepting a dashboard status as proof.
For a recovery test, choose several representative items: a recently edited document, an older archive, a large media file, and a shared business file. Restore them to a separate location, open them, and confirm that the result is usable. Document how long the process took and which account or permission was required.
When to revisit
Review the migration monthly during the first few months, then at least quarterly if the account holds important personal or business files. The review does not need to repeat the entire migration. Focus on the variables most likely to change: storage usage, active users, sharing permissions, backup success, recovery results, subscription terms, export limits, and connected applications.
Start a fresh review when any of these events occurs:
- You replace a computer, phone, or local backup drive.
- You add a business user, contractor, department, or external collaborator.
- The provider changes its plan structure, storage limits, pricing, retention, or security controls.
- You notice duplicate files, missing versions, failed synchronizations, or unexplained storage growth.
- You close an account, change an administrator, or move from personal to business storage.
- You need to recover a file and discover that the documented process is unclear or incomplete.
At each checkpoint, confirm that the destination remains the authoritative copy, the independent backup is still readable, and former accounts or integrations no longer have unnecessary access. If the service no longer fits your needs, repeat the inventory and mapping process rather than starting an unplanned bulk download.
Final action: create a migration record today with the source account, destination account, folder map, backup location, last verification date, and next review date. Then test one restore. That small checkpoint turns a file transfer into a maintained storage plan—and gives you a reliable starting point the next time you change providers.
