Migration Assistant deployment
Migration Assistant moves data, packages and most system configurations from a supported source NAS to a supported destination while the destination uses its own storage pool. It is often the cleanest upgrade path when buying a new NAS and new drives because the source remains available for much of the process and the destination can be prepared in advance.
Quick answer
Use Migration Assistant when both models and capacity qualify
The method has model, DSM and storage-capacity requirements. If the pairing is unsupported, Hyper Backup is the safer documented fallback.
Current Amazon listings
Replacement and migration DiskStation options
Product cards are supporting purchase references only; they do not determine whether your failed drives are recoverable or whether a specific migration pairing is supported.
Technical decision
Treat cutover as a service migration, not just a copy job
Plan how clients, network identity, certificates, backups and applications will move after the bulk data transfer finishes.
Interactive recovery tool
Synology Migration Method Selector
This tool routes the symptoms you select to a safer next step. It does not issue destructive commands. Before initializing a disk, deleting a pool, reinstalling DSM or moving the only copy of important data, verify the exact live Synology procedure for your model and DSM build.
Recovery safety checklist
Four rules before you change a failing Synology system
Preserve readable data first
If unique files can still be opened, copy or back them up before changing storage metadata, reinstalling DSM or running stressful diagnostics.
Record drives and bays
Capture drive serial numbers, bay positions, health states and DSM messages before swapping disks or moving them to another chassis.
Match the action to the failure layer
A degraded pool, crashed volume, failed system partition, bad drive and failed bay have different supported recovery paths.
Keep a rollback path
During migration or recovery, do not erase the source system until the destination data, permissions, applications and backups have been verified.
Confirm the model pair before buying hardware
Migration Assistant has source and destination model limitations. Check the current Synology compatibility table rather than assuming all Plus models can clone directly into every newer Plus model.
Inside a Migration Assistant project, confirm the model pair before buying hardware affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Prepare the destination on supported DSM
The destination should be initialized and running an appropriate DSM version. Synology requires destination DSM to meet the migration rules before the assistant can take over.
Inside a Migration Assistant project, prepare the destination on supported dsm affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Build the destination storage pool deliberately
Unlike HDD migration, Migration Assistant lets the new NAS use a newly configured storage pool. Choose RAID, drive sizes and capacity with future expansion in mind before copying the source.
Inside a Migration Assistant project, build the destination storage pool deliberately affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Allow headroom beyond visible user data
Source used space is not the only capacity consideration. Packages, metadata, snapshots and migration working requirements consume storage, so size the destination with margin.
Inside a Migration Assistant project, allow headroom beyond visible user data affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Keep services available during the long copy phase
One advantage of Migration Assistant is that source services can remain online for much of the transfer. Schedule the final synchronization and cutover for a quieter period when brief service interruption is acceptable.
Inside a Migration Assistant project, keep services available during the long copy phase affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Inventory packages that matter to the business
Not every package or configuration migrates identically across hardware generations. Record databases, containers, surveillance settings, certificates and application credentials that need explicit validation.
Inside a Migration Assistant project, inventory packages that matter to the business affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Use wired networking appropriate to the dataset
Large migrations can take many hours over 1GbE. A faster supported LAN between source and destination reduces the transfer window, but both systems and the network path must actually support the speed.
Inside a Migration Assistant project, use wired networking appropriate to the dataset affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Do not change the source unnecessarily mid-migration
Major DSM upgrades, pool changes or package restructuring during the transfer can add variables. Stabilize the source and treat migration as a controlled project until verification is complete.
Inside a Migration Assistant project, do not change the source unnecessarily mid-migration affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Plan destination identity and client remapping
Decide whether the new NAS will inherit the old hostname/IP role or use a new identity. SMB mappings, backup targets, applications and remote-access services must point to the correct destination after cutover.
Inside a Migration Assistant project, plan destination identity and client remapping affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Verify permissions and package data
Open shared folders with real user accounts, test application interfaces and confirm scheduled tasks. A green migration status does not prove every permission or external integration behaves exactly as before.
Inside a Migration Assistant project, verify permissions and package data affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Keep the source untouched through a verification window
Do not immediately wipe source drives. Retaining the old system for a defined period provides a rollback source for files or settings that were missed during validation.
Inside a Migration Assistant project, keep the source untouched through a verification window affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Create a fresh post-migration backup
Once the destination becomes authoritative, run a new backup task from it and perform a sample restore. The old NAS should not remain the only fallback forever.
Inside a Migration Assistant project, create a fresh post-migration backup affects whether the supported source-to-destination clone can complete cleanly on the new storage pool. Confirm the exact model pairing, usable target capacity and DSM relationship before starting the bulk transfer. Treat packages and network identity as explicit validation items rather than assuming that copied data proves application success. This checkpoint should keep the destination's new-drive advantage while preserving a rollback source until users, scheduled jobs and backups have all been tested after final synchronization.
Questions people ask
Synology Migration Assistant Guide questions
What does Migration Assistant move?
It can migrate data, packages and most system configurations for supported model pairs.
Migration Assistant is strongest when the model pair is supported and the destination has a prepared pool with enough usable capacity and a verified rollback plan.
Do I need new drives?
Migration Assistant is especially useful when the destination has its own new drives and storage pool, though the exact design depends on capacity and compatibility.
Can I change filesystem with Migration Assistant?
Synology's general comparison indicates the file system cannot be changed through Migration Assistant; use Hyper Backup when a filesystem change is required.
Does Migration Assistant require downtime?
Services can remain available for much of the transfer, with a shorter final cutover period.
Can I use it between any two Synology models?
No. Source and destination model limitations apply, so check the current support matrix.
How much destination capacity do I need?
Enough usable space for migrated data plus migration requirements and future headroom; do not compare only raw drive capacity.
Should both NAS devices be on the same DSM version?
The destination DSM must satisfy Synology's migration-version rules and generally cannot be older than the source.
What happens to packages?
Many packages and settings migrate, but validate every critical service afterward because architecture or version changes can affect behavior.
Can I keep the old NAS after migration?
Yes, and keeping it intact during a verification window is prudent before erasing or repurposing it.
What if Migration Assistant says the models are unsupported?
Use Hyper Backup or another documented migration method instead of forcing the pairing.
Official references and methodology
Verify the live DSM state before any destructive recovery step
This page evaluates Migration Assistant specifically, rather than all Synology transfer choices. It concentrates on supported source/destination pairing, destination-pool preparation, capacity, DSM versions, service cutover and post-copy validation. Where a planned filesystem redesign, unsupported pairing or drive-reuse requirement conflicts with Migration Assistant's constraints, the guide directs the reader to compare HDD migration or Hyper Backup instead of forcing the tool.
- Synology: Migration Assistant guide
- Synology: Migration methods between Synology NAS systems
- Synology Hyper Backup documentation
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Failure states, DSM behavior, migration compatibility and recovery options can change by model and DSM build. Preserve readable data and verify Synology's current Knowledge Center instructions before initializing drives, deleting pools, reinstalling DSM or changing the only copy of important data.