Storage and File Migration: NAS, File Servers and Archives to Cloud
Storage and file migration moves file servers, NAS shares and archives to cloud file or object storage while keeping permissions, folder paths and timestamps. NTSPL profiles the data by age and access, chooses file, object or hybrid-cache targets per share, runs repeated delta syncs, and cuts users over in a short final sync on AWS, Azure or Google Cloud.
Delivered on
In scope
What Makes File Migrations Harder Than They Look
File data grows quietly. A 2015 NAS holding design files, scanned invoices and department shares now has 40-150 TB, 30 million files, NTFS permissions set by people who left years ago, and paths longer than 260 characters. Most of it has not been opened in two years, yet users expect the mapped drive letter to work on Monday. Copying it with a script over a weekend fails on locked files, broken ACLs and time.
NTSPL profiles before moving: file counts, sizes, age, last access and permission complexity per share. Hot shares go to managed file services, cold data to object storage tiers, and branch shares to a hybrid cache where local speed matters. Transfers run as repeated delta syncs over days or weeks, so the final cutover only copies what changed since the last pass, usually under an hour.
Signals Your File Estate Is Ready to Move
Signals you need Storage & File Migration
- NAS or file server hardware is out of support and holds 10-500 TB.
- More than 60% of files have not been accessed in 12 months but sit on primary disk.
- Branch offices copy large files over the WAN and complain about speed.
- Ransomware recovery from current file backups would take more than a day.
When to choose something else
- If files are application data inside a database or ECM system, migrate the application instead.
- If the goal is collaboration on Office documents, a move to SharePoint or Google Drive may fit better than file shares.
Profiling, Target Choice, Sync and Cutover
Data profiling
Per-share counts, sizes, age, last access, path length and permission complexity.
Target design
Managed file share, object storage tier or hybrid cache chosen per share, with identity integration.
Permission handling
NTFS ACLs, SMB share permissions and POSIX modes preserved or cleaned up as agreed.
Delta sync
Initial copy and repeated deltas with verification logs for each pass.
Cutover and redirection
Final sync, DFS namespace or drive-mapping change, and source set to read-only.
Profile-Sync-Cutover File Migration Pipeline
Profile-Sync-Cutover Pipeline for File and Archive Data
Profiling sorts shares into hot, warm and cold, which sets the target per share. Agents run repeated delta syncs with verification, then a final sync and namespace change move users across.
Select any component
Profile-Sync-Cutover Pipeline for File and Archive Data: click any of its 7 components to see its role and the design choice NTSPL makes for it, or trace the 6-step primary path.
File and Object Storage Targets by Cloud
DataSync copies SMB and NFS shares with metadata into FSx or S3. FSx for ONTAP suits NetApp sources because SnapMirror can replicate directly.
Azure File Sync keeps a cache on a branch Windows server with cloud tiering, which suits offices with slow links; AzCopy handles bulk copies of cold data into Blob tiers.
Storage Transfer Service uses on-prem agents for file systems; Transfer Appliance helps where links cannot carry the volume.
File Target Choices: Shares, Objects, Caches, Tiers
File share or object storage
Keep data on SMB or NFS shares when users or apps open files by path and edit in place. Move to object storage when files are written once and read rarely, such as scans, logs, media archives and backups. A common split is 25-40% to file shares and the rest to object tiers, which can cut storage cost by half or more.
Permissions: preserve or clean up
Preserve ACLs when shares are well managed. Where profiling finds broken SIDs, direct user grants or Everyone access on more than 10% of folders, clean up first using group-based permissions per department. Cleaning during migration is cheaper than after, because users are already expecting change. Get each share owner's sign-off on the new model.
Hybrid cache for branches
Use a hybrid cache, such as Azure File Sync or a cached gateway, where a branch works on large files over a link under 50 Mbps. Size the local cache to 20-30% of the share; cloud tiering keeps the rest in cloud. Do not cache branches with fast links; direct access to the cloud share is simpler to run.
Cutover method
If you use a DFS namespace, change targets and users see no path change. Without DFS, change drive mappings by group policy or login script. Set the source read-only at cutover rather than deleting it, and keep it for two to four weeks. Run the final delta during a quiet window; for most shares it takes under an hour.
File Migration Sequence by Share
Profiling and permission review
Share reports, ACL issues and hot or cold split agreed with owners.
Target build and identity
Shares, object buckets, caches and AD or Entra integration set up.
Initial copy
Bulk transfer with throttling and verification logs.
Delta passes
Nightly or weekly deltas until change volume is small.
Cutover and source hold
Final sync, namespace or mapping change, source read-only.
What you receive
File Transfer Integrity and User Impact Measures
| KPI | Typical target |
|---|---|
| Files with checksum or metadata mismatch | Zero at final pass |
| Final cutover duration | Under 1 hour per share |
| Share of data on cold or archive tiers | 50-75% |
| Access-denied tickets in the first week | Under 1 per 100 users |
Permission, Path and Lock Problems in File Moves
| Risk | How NTSPL prevents it |
|---|---|
| Paths longer than 260 characters or invalid characters fail to copy. | Profiling lists them, and owners shorten paths before the initial copy. |
| Open or locked files are skipped silently. | Every pass logs skipped files, and the final pass runs with users disconnected. |
| Permissions break and users lose access on Monday. | A pilot group tests access a week before cutover, and ACLs are verified by sample. |
Azure Files with File Sync or a NetApp-based cloud file service?
Choose Azure Files with File Sync for Windows-centric estates with branches on slow links, standard SMB use and moderate performance needs; it is simple and cloud tiering keeps local caches small. Choose a NetApp-based service, such as Azure NetApp Files, FSx for NetApp ONTAP or Google Cloud NetApp Volumes, when the source is already NetApp, when you need NFS and SMB on the same data, or when workloads need sub-millisecond latency and high throughput, such as CAD rendering. NetApp services cost more per TB but migrate NetApp sources with SnapMirror and preserve snapshots.
Key facts: Storage & File Migration
Storage & File Migration in Practice
2 Storage & File Migration scenarios, from Footwear brand and Freight forwarding and customs brokerage, plus related platform case studies.
Footwear brand moves 42 TB of design files to Azure Files with caches at two studios
Freight forwarder moves 96 TB of shipment records to Cloud Storage with retention locks
Regional-language OTT service halves video start time and cuts origin egress by 82%
News channel moves 1.4 PB of footage from LTO tape to tiered Blob Storage
Storage & File Migration: Frequently Asked Questions
Will users have to change drive letters or paths?
Not if you use a DFS namespace, because only the target behind the namespace changes. Without DFS, we update drive mappings through group policy at cutover. Users usually see the same letter and folder structure on the next login. We test this with a pilot group first.
How long does a file migration take?
For 20-100 TB, plan 6-9 weeks: two weeks of profiling and setup, three to four weeks of initial copy, then delta passes and cutover. A 1 Gbps link moves about 8-9 TB a day at full use, but business-hour throttling usually halves that.
What does file migration cost?
Services for a 50 TB estate typically run INR 6-15 lakh, depending on permission clean-up and branch caching. Transfer services are low cost or free. Moving cold data to archive tiers often cuts monthly storage cost by half compared with keeping everything on primary storage.
How are permissions preserved?
Transfer tools copy NTFS ACLs, owners and timestamps when the target is joined to the same identity source. We review permissions first, fix broken SIDs, and test access with a pilot group a week before cutover so issues are found early.
How do we keep statutory records safe in cloud?
Records such as GST invoices or customs documents go to object storage with retention locks matching your legal retention period. They cannot be deleted early, even by admins. Data stays in Indian regions, and access logs are kept 180 days for CERT-In.
What happens to the old NAS?
It stays read-only for two to four weeks after cutover as a fallback. Once owners confirm nothing is missing, it is wiped to NIST SP 800-88 or physically destroyed, with a certificate, and its support contract is ended. Its rack space and power are freed.