Upgrading to a newer or larger Synology NAS doesn't mean starting from scratch. Synology documents three migration methods: Migration Assistant, HDD migration, and migration via Hyper Backup, each with different requirements and limitations. Which method to use depends on your upgrade scenario. Drive migration is the faster option when moving within compatible storage pool types. Network migration is more flexible but requires both NAS units to be online simultaneously.
In short: Having enough bays is necessary but not sufficient for HDD migration; also verify drive compatibility, package architecture, filesystem and feature support, volume-size limits, and Synology's other HDD-migration restrictions. Power down the old NAS, move drives to the new NAS in the same order, and boot. DSM detects the existing storage pool and imports data. For migrations using new drives or a different storage layout, Migration Assistant can migrate data, packages, and most configurations, subject to its model, DSM, filesystem, and capacity requirements; Hyper Backup is another documented migration method. Always take a full backup before migrating. Migration failures do happen.
Method 1. Physical Drive Migration
Physical drive migration moves your drives from the old NAS directly into the new NAS chassis. When the source and destination satisfy Synology's HDD-migration requirements, the method can transfer data, packages, and most system configurations; some architecture combinations require package repair or reconfiguration, and unsupported combinations may retain only user data.
When drive migration works:
- Upgrading from a 2-bay to a 4-bay model (e.g. DS225+ to DS425+). Insert the drives in the same slot order as the original NAS
- Upgrading within the same NAS family (e.g. DS923+ to DS1525+)
- The new NAS uses a compatible storage pool format (Btrfs-to-Btrfs or ext4-to-ext4)
- The new NAS's DSM version is the same or newer than the old one
When drive migration doesn't work:
- Migrating from a Synology NAS to a different NAS brand. Not supported
- Moving from SHR (Synology Hybrid RAID) to a different pool type. Requires data migration instead
- Moving from a 4-bay to a 2-bay (you can't migrate more drives than the new NAS has bays)
Synology maintains a compatibility matrix on their website listing which source and target model combinations support drive migration. Check this before assuming migration will work. Surprises at this step are costly.
Drive Migration: Step-by-Step
Before moving any drives:
- Full backup: Run a Hyper Backup to an external drive or cloud storage. This is non-negotiable. Drive migration is low-risk but not zero-risk. If the new NAS has a hardware fault, you need a recovery path.
- Note your current DSM version: The new NAS should be running the same or higher DSM version. Follow Synology's model-specific HDD-migration procedure. Where a destination DSM update is required before an identical-model migration, Synology instructs you to use a separate temporary drive, shut down the NAS, and remove that drive before inserting the source drives.
- Note your drive order: Photograph the drive positions in the old NAS. Record the drive order and install the drives in the same order, as Synology recommends; abort if Web Assistant warns that the drives will be deleted. DSM reads pool metadata. But documenting it removes uncertainty.
Migration steps:
- Power off the old NAS cleanly (shutdown from DSM, not power cut)
- Remove the drives from the old NAS
- Insert them into the new NAS (same slots if possible. Slot 1 to slot 1, etc.)
- Power on the new NAS
- After booting the destination, use Web Assistant or Synology Assistant, confirm that its status is Migratable, and complete Synology's DSM installation and migration wizard.
- After HDD migration, the destination retains the newer supported DSM version; follow the migration wizard's model-specific prompts and review any irreversible operation before proceeding. Read the prompt carefully before accepting, as some pool upgrades are irreversible
The import process takes a few minutes. Data, packages, and most system configurations can carry over, but package repair or reconfiguration may be required and some package tasks or settings can be lost for particular architecture combinations. Some packages may need to be reinstalled from Package Center if their version isn't compatible with the new DSM version.
Method 2. Network Migration via Migration Assistant
Migration Assistant is a DSM package that migrates NAS configurations (user accounts, group settings, shared folder definitions, packages list) from an old NAS to a new one over the network. It migrates data at the volume or block-level LUN level along with packages and most system configurations. You handle data transfer separately after the configuration migration.
When to use Migration Assistant:
- You're changing NAS brands within Synology's portfolio (e.g. replacing a consumer DS model with a rackmount RS model)
- You're changing pool types or the drive count prevents a direct drive swap
- You want to run both NAS units in parallel during transition
- You want a clean DSM install on the new NAS rather than importing an existing pool
What it migrates: data at the volume or block-level LUN level, packages and their settings/data, and system configurations, subject to Synology's documented exclusions. What it doesn't migrate includes the destination DSM version, Synology Account settings, licenses, specified network and external-access settings, push-notification settings, desktop widget/taskbar settings, and Virtual Machine Manager settings.
Migration Assistant: Step-by-Step
Both NAS units must be online and reachable from the same network during migration.
- On the new NAS, install DSM fresh if not already done. Set up a volume but don't create any shares or user accounts yet. Migration Assistant will create them from the old NAS.
- On the new NAS, open Package Center and install Migration Assistant.
- Open Migration Assistant. It scans the local network for compatible source NAS units. Select the old NAS.
- Follow the migration wizard. Choose which settings to migrate (all is fine for a full migration). Enter the old NAS admin credentials when prompted.
- Migration Assistant copies configuration. Migration duration varies with total data volume, network speed, drive performance, package architecture, and system load.
- After the wizard completes, the new NAS has the same users, shares, and package configuration as the old one. Packages may need to be re-activated or configured for the new NAS's storage paths.
Migration Assistant transfers the data as part of its workflow; use rsync, Hyper Backup, or SMB only when intentionally choosing a separate copy or backup-based method.
- rsync over SSH. Most efficient for large volumes. Configure an SSH connection from the new NAS to the old one and use rsync to copy share contents. Actual rsync throughput varies with file sizes, protocol overhead, encryption, disk performance, NAS load, and network conditions.
- Hyper Backup restore. If you took a Hyper Backup before migration, restore from it to the new NAS.
- SMB copy. Connect a PC to both NAS units via SMB and copy data across. Slowest but simplest for non-technical users.
Buying a New Synology NAS in Australia
Current Synology NAS models available in Australia through major retailers:
- DS225+ (2-bay, Intel Celeron, 2GB RAM). Check Mwave for current pricing. Entry-level upgrade target for older 2-bay models.
- DS425+ (4-bay, Intel Celeron, 2GB RAM). Check Mwave for current pricing. Entry-level upgrade target for older 4-bay models.
- DS925+ (4-bay, Quad-core, 4GB RAM). Check Mwave for current pricing. Mid-range upgrade for users wanting more CPU and RAM headroom.
- DS1525+ (5-bay, AMD Ryzen V1500B, 8GB RAM). Check Mwave for current pricing. For power users and small business.
Mwave, PLE Computers, Scorptec, and Umart are all Australian retailers with physical presence and full Australian Consumer Law protections. If a NAS fails to meet an ACL consumer guarantee, remedies can include repair, replacement, or refund; which remedy applies and who chooses it depend on whether the failure is major or minor and the purchase circumstances. These listed Synology models carry three-year hardware warranties in Australia, in addition to applicable ACL consumer guarantees. Purchases via Amazon Global or grey-market importers may not receive local warranty support from Synology AU.
Common Migration Problems
New NAS doesn't recognise the drives: The storage pool metadata may be incompatible with the new NAS. Check Synology's migration compatibility matrix. Check Synology's current HDD-migration limitations, package-architecture table, destination feature support, and drive compatibility; use another migration method when those requirements are not met. Use Method 2 instead.
SHR volume not importing: SHR is proprietary to Synology. An SHR volume may be eligible for HDD migration only when the destination supports SHR and all other model, architecture, drive, DSM, volume, and feature requirements are satisfied. Moving SHR drives to a non-Synology NAS doesn't. SHR is Synology's automated storage scheme built from Linux RAID arrays and, where needed, LVM; this does not make direct migration into another NAS brand a supported procedure.
Packages missing after migration: Migration Assistant migrates packages, package settings, and package data, although packages may require repair or updating when CPU architectures or DSM versions differ. After configuration migration, open Package Center and reinstall any packages that didn't auto-restore. Package settings (like Active Backup tasks) may need to be reconfigured if the data paths changed.
Shared folder permissions reset: After drive migration, verify shared folder permissions in Control Panel > Shared Folder. Audit each share before putting the new NAS into production.
Related reading: our Synology brand guide.
Use our free NAS vs Cloud Migration Cost Calculator to compare the total cost of migrating from cloud to your own NAS.
Related reading: our NAS explainer.
See also: our complete Synology NAS Australia guide.
Can I migrate from a 4-drive SHR-2 array to a new NAS?
Yes, if the new NAS supports the same number of drive bays or more, and the pool type is compatible. SHR and SHR-2 pools can be migrated only when the destination supports the RAID type and all of Synology's HDD-migration, package-architecture, drive, DSM, filesystem, and capacity requirements are met. If you're expanding from 4 to 6 bays, migrate the 4 drives first and add the 2 new drives to expand the pool after migration. Never add new drives during the initial migration step. Complete migration first, verify data integrity, then expand.
Do I need to reinstall DSM on the new NAS before doing drive migration?
If the new NAS arrives without DSM (blank drives, first boot), DSM installation will typically detect the migrated drives after you insert them and offer a migration option. On standard DiskStation models, DSM is stored on system partitions on the installed drives, not internal flash; follow Synology's model-specific HDD-migration procedure to determine whether destination setup or a temporary drive is required. The critical thing is not to initialise the drives on the new NAS before migrating. Initialisation formats the drives and destroys all data.
How long does NAS data migration take?
Drive migration (moving physical drives) is fast. HDD migration avoids copying the entire data set, but completion time varies and may include DSM and package installation, repair, or reconfiguration. The 'migration' is just DSM reading the existing pool metadata from the drives and mounting it. Migration Assistant transfers configurations, packages, and data in one migration workflow; total duration depends on data volume, network speed, drive performance, and system load. A 4TB rsync transfer over Gigabit Ethernet may take many hours; actual throughput depends on file sizes, protocol overhead, encryption, disk performance, NAS load, and network conditions. For very large volumes (20TB+), plan the data copy to run overnight or over multiple nights.
Can I migrate from an older DSM 6 NAS to a new DSM 7 NAS via drive migration?
In most cases, yes. Synology designed drive migration to work across DSM versions. DSM-version migration support depends on the source and destination package architectures and on the destination supporting the newer DSM version; consult Synology's current migration table for the specific models. Some older pool configurations (specifically ext4 volumes from very old NAS models running DSM 5 or earlier) may have compatibility issues. Check Synology's compatibility table for your specific model combination. As always, take a full backup first.
Should I use the same IP address on the new NAS?
For a seamless transition, configure the new NAS with the same IP address as the old one after migration completes. This avoids having to update device mappings, application configurations, and Time Machine/backup targets that reference the old NAS IP. Assign the new NAS a static IP that matches the old one, or update your router's DHCP reservations to assign the old IP to the new NAS's MAC address. Power off the old NAS before bringing the new one online to avoid an IP conflict.
Can I sell my old Synology NAS after migration?
Yes, but securely erase the drives first. Even after drive migration (where you took the drives out), the drive's metadata still contains pool configuration information. In Storage Manager on the new NAS (now running with your migrated data), those drives are active. Don't accidentally wipe them. For drives you're leaving with the old NAS to sell, use DSM's Secure Erase feature on the old unit before selling, or use a separate disk wipe tool. Selling a NAS with drives still containing your data is a significant security risk.
Upgrading your NAS and wondering which model to buy? The best NAS guide for Australia compares current Synology, QNAP, and UGREEN models by use case, price, and Australian availability.