In this blog post Planning NAS Migration to Azure NetApp Files Without Surprises we will explain how to assess your existing storage, choose the right Azure design and move critical file data without unexpected costs or disruption.
NAS migrations often look simple on a project plan: copy the files, update access paths and retire the old hardware. The problems usually appear later, when applications slow down, permissions fail, storage costs exceed the forecast or the final cutover takes much longer than expected.
Azure Migrate and Azure NetApp Files address different parts of this problem. Azure Migrate helps you understand what you have and where it could go. Azure NetApp Files provides managed, high-performance file storage in Azure for workloads that need more speed, scale or consistency than a standard file share.
How the technology works
Azure Migrate is Microsoft’s central assessment platform for planning moves into Azure. Its NAS discovery capability can connect to supported NetApp ONTAP and Dell PowerScale systems using read-only credentials, then inventory SMB, NFS and S3 shares. These are the common methods used by Windows, Linux and data-intensive applications to access shared storage.
CPI Consulting helps organisations design, build and secure Azure AI solutions, from Azure OpenAI and Microsoft Foundry to agents, governance and production deployment.
Visit CPI ConsultingThe assessment reviews capacity, usage and performance information. It can then compare possible destinations, including Azure Files, Azure Blob Storage and Azure NetApp Files, and provide readiness findings, sizing recommendations and estimated costs.
Azure NetApp Files is a Microsoft-managed file storage service powered by NetApp technology. It supports Windows-oriented SMB shares, Linux-oriented NFS volumes and dual-protocol configurations. Microsoft operates the underlying storage platform, while your team controls the volumes, network access, identity settings, performance and data protection policies.
Importantly, assessment and migration are separate steps. Azure Migrate helps you make the decision; it does not automatically guarantee that every share will move cleanly. The transfer method, testing process and cutover plan still need to be designed.
1. Start with measured usage rather than allocated capacity
A 100 TB NAS does not necessarily need 100 TB of premium cloud storage. It may contain snapshots, abandoned project folders, duplicate data and files that have not been opened for years.
Azure Migrate can provide an assessment based on the current configuration or observed performance. When performance data is available, it can help avoid copying the old environment’s overprovisioning into Azure.
Check whether assessment figures were measured directly or estimated using standard formulas. An estimate is useful for an initial business case, but a critical workload should be observed through normal business cycles, month-end processing and other peak periods before you commit to a design.
Our earlier guide to safer NAS migration planning with Azure Migrate explains the discovery and assessment process in more detail. The next step is turning that data into an Azure NetApp Files design that fits the business.
2. Use Azure NetApp Files for the workloads that justify it
Not every department share needs high-performance storage. General office documents may be better suited to Azure Files, while archived data may belong in lower-cost object storage such as Azure Blob Storage.
Azure NetApp Files is usually considered for workloads where storage delays affect the application or the business. Examples include engineering datasets, large user profile environments, analytics platforms, databases, media production and applications that depend on fast NFS or SMB access.
A mixed approach often produces a better outcome than forcing everything into one service. Azure Migrate can compare migration paths at the share level, helping you separate ordinary file storage from workloads that genuinely need Azure NetApp Files.
If much of your estate consists of conventional Windows shares, review our guide to moving file shares to Azure Files before selecting one destination for the entire NAS.
3. Design capacity and performance together
Azure NetApp Files pricing is influenced by provisioned capacity and performance. Choosing a high service level for every volume may deliver excellent speed, but it can also create an unnecessarily large monthly bill.
Map each share against four practical questions:
- How much data is genuinely active?
- What performance is required during peak periods?
- How quickly is the data growing?
- How much downtime can the workload tolerate?
Service levels and capacity pools can then be designed around groups of workloads with similar needs. Flexible performance options may also allow capacity and throughput to be managed separately, reducing the need to buy more storage simply to obtain more speed.
Inactive data can sometimes remain available while being moved to a lower-cost tier. Our article on Azure NetApp Files cool access covers where that approach can reduce ongoing costs.
4. Select the migration method before promising a cutover date
For supported NetApp ONTAP environments, the Azure NetApp Files migration assistant can use ONTAP’s replication technology to transfer volumes and synchronise later changes. This can reduce the final outage because most data is copied before the cutover window.
Other NAS platforms may require NetApp Data Migrator, a specialist migration product or file-based tools. The right option depends on the source platform, data volume, available network bandwidth and whether permissions, timestamps and other file details must be preserved.
Plan at least one pilot migration and one rehearsal. Test application behaviour, user access, file permissions, transfer speed, rollback and the time needed for the final synchronisation. A successful copy is not the same as a successful business cutover.
5. Build security and recovery into the target
Moving storage to Azure does not automatically make it compliant or resilient. Network access, administrator permissions, snapshots, backups and disaster recovery must be deliberately configured.
Use private network connectivity where practical, restrict privileged access and separate storage administration from everyday user access. New Azure NetApp Files volumes should use Standard network features, and older designs should be reviewed against our network features upgrade checklist.
Snapshots can support fast recovery from accidental deletion, while backups and cross-region or cross-zone replication address different failure scenarios. These controls should be mapped to recovery targets and the Essential 8, the Australian government’s cybersecurity framework that many organisations use to reduce cyber risk.
A practical migration scenario
Consider a 200-person engineering company with an 80 TB NAS. An initial assumption that all 80 TB required premium storage made the Azure proposal difficult to justify.
Assessment showed that only 18 TB supported performance-sensitive design work. Another 27 TB was suitable for standard business file storage, while the remainder consisted largely of inactive projects and retained data.
Separating those workloads produced a more practical design: Azure NetApp Files for active engineering data, Azure Files for general shares and lower-cost storage for the archive. The business gained predictable application performance without paying premium rates for every file.
Your pre-migration decision checklist
- Confirm every NAS cluster, volume, share, protocol and business owner.
- Collect performance data across normal and peak operating periods.
- Compare Azure NetApp Files with Azure Files and Blob Storage by workload.
- Validate identity, permissions, networking and application compatibility.
- Choose and test the data transfer method.
- Calculate costs for capacity, performance, networking, backup and recovery.
- Rehearse cutover and document a rollback plan.
- Define who will manage and optimise the service after migration.
Plan the business move, not just the data copy
The safest NAS migration is based on evidence rather than assumptions. Azure Migrate provides the inventory and sizing information, while Azure NetApp Files can provide the performance and enterprise file capabilities needed by critical workloads.
CloudProInc is a Melbourne-based Microsoft Partner and Wiz Security Integrator with more than 20 years of enterprise IT experience. We help organisations across Australia assess storage, design Azure environments and plan hands-on migrations without the overhead of a large, faceless provider.
If you are unsure whether Azure NetApp Files is the right destination, or whether your current migration estimate reflects real usage, we are happy to review the plan with you — no strings attached.