Upgrading to a newer or larger Synology NAS doesn't mean starting from scratch. Synology provides two migration paths that preserve your data, DSM configuration, packages, and user accounts: physical drive migration (moving your drives from the old NAS to the new one) and network migration via the Migration Assistant package. 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: If you're upgrading to a same-generation or newer Synology NAS with the same number of bays or more, drive migration typically works. 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 cross-model or cross-pool-type migration, use Migration Assistant to transfer configurations, then use a data copy method (rsync, Hyper Backup, or SMB) for the data itself. 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. DSM on the new NAS detects the existing Btrfs or ext4 storage pool and imports it, preserving all data, shares, user accounts, and installed packages.
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. If the new NAS ships with a lower DSM version, upgrade it first (create a new volume on the new NAS, install DSM, upgrade to current version, then remove that volume and do the drive migration).
- Note your drive order: Photograph the drive positions in the old NAS. For SHR or RAID 5/6, inserting drives in a different order than expected doesn't break anything. 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
- DSM on the new NAS will detect the existing storage pool and begin importing it
- If the new NAS has a higher DSM version than the drives expect, DSM will offer to upgrade the storage pool format. Read the prompt carefully before accepting, as some pool upgrades are irreversible
The import process takes a few minutes. Shares, user accounts, packages, and scheduled tasks all carry over. 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 does not migrate data. 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: DSM configuration, user/group accounts, shared folder definitions (not content), installed package list, network settings (optionally), and most DSM application settings. What it doesn't migrate: actual data files, large package databases (Surveillance Station recording history, Drive version history).
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. This typically takes 5-15 minutes depending on the number of user accounts and packages.
- 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.
After configuration migration, transfer data using one of these methods:
- 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. Runs at LAN speeds (~100MB/s on Gigabit).
- 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). From $585 at Mwave. Entry-level upgrade target for older 2-bay models.
- DS425+ (4-bay, Intel Celeron, 2GB RAM). From $899 at Mwave. Entry-level upgrade target for older 4-bay models.
- DS925+ (4-bay, Quad-core, 4GB RAM). From $1,029 at Mwave. Mid-range upgrade for users wanting more CPU and RAM headroom.
- DS1525+ (5-bay, AMD Ryzen V1500B, 8GB RAM). From $1,285 at Mwave. 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 new NAS fails within a reasonable expected lifespan, ACL entitles you to repair, replacement, or refund. Don't be put off by the manufacturer's 1-year warranty. 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. If the combination isn't listed, drive migration isn't supported. Use Method 2 instead.
SHR volume not importing: SHR is proprietary to Synology. Moving an SHR volume between Synology models generally works. Moving SHR drives to a non-Synology NAS doesn't. SHR is not compatible with standard Linux mdadm RAID arrays.
Packages missing after migration: Migration Assistant copies the package list but doesn't re-install packages. 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. In some migrations, permission inheritance settings don't carry over correctly. 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.
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 migrate cleanly between Synology models via drive migration. 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. If the new NAS has been set up already (DSM installed on the internal flash, but no user volumes), the migration wizard should still detect the drives on first boot. 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. The actual pool import takes 5-20 minutes, no data copying required. The 'migration' is just DSM reading the existing pool metadata from the drives and mounting it. Network migration via Migration Assistant takes 10-30 minutes for configuration, then however long a data copy takes. A rsync copy of 4TB over Gigabit LAN runs at ~80-100MB/s. Roughly 11-14 hours for 4TB. 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. When the new NAS boots with the migrated drives, DSM 7 will upgrade the pool format if needed. 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.
Best NAS Australia Guide →