NetSuite to Dynamics 365: The ERP Migration Roadmap for 2026

ERP migrations are more than IT upgrades. They shape how a business runs and grows. For global companies, the ERP system is the core of operations. It keeps finance, supply chain, warehouse, service, and reporting aligned. When that system adds more cost than value, migrating from NetSuite becomes the only option.

Let’s look at one example.

The company is global, with subsidiaries in the UK, EU, Canada, and the US. It runs on NetSuite OneWorld. Several third-party systems are connected, but they add cost and complexity. With the NetSuite licence ending in July 2026, the business must act now.

The goal is to move to Microsoft Dynamics 365. Both Business Central and Finance & Operations (F&O) are under review. The new ERP must improve long-term functionality, reduce operating costs, and deliver tighter integration across departments.

The objectives are clear. The business wants to replace WAER WMS with a modern warehouse module in Dynamics. It needs to support electronic invoicing and region-specific localisation to stay compliant. It also plans to roll out real-time reporting in Power BI, removing the need for Phocas BI.

Connections with HubSpot CRM and banking systems are essential. Today, too many workflows are manual, and duplicate data entry wastes time. Dynamics must remove these bottlenecks.

This project is more than a system change. It is about building a platform that supports expansion, simplifies processes, and gives the business control of its operations for the next decade.

Current ERP Landscape

The company’s current setup shows both strengths and weaknesses. At the core is NetSuite OneWorld, which manages financials and inventory with limited CRM features. Automations are handled by SuiteScript, such as invoice emails and automatic currency conversions. While useful, these scripts often feel like patches. They add maintenance work instead of creating long-term stability.

Customisation is limited. Most roles and permissions are standard, with only a few custom fields in use. This makes the system rigid and harder to adapt as the business grows.

The structure of the organisation adds further complexity. Headquarters are in the UK, with subsidiaries in the EU, Canada, and the US. Each entity works with its own tax, reporting, and compliance rules. Transactions span GBP, EUR, CAD, and USD. The ERP must handle these without errors and still provide consolidated group reports.

Third-party systems make the landscape more fragmented. WAER WMS manages warehouse tasks, but it is disconnected from the ERP. HubSpot CRM is in place and will soon power the eCommerce site. Phocas BI supplies reporting, but it lags behind modern analytics and adds cost. On the other hand, Microsoft 365 is already in use across the business, fully cloud-based and aligned with the company’s IT strategy.

This landscape shows why a change is needed. NetSuite has served its purpose, but the lack of flexibility, rising costs, and reliance on third-party tools no longer match the company’s goals.

Dynamics 365: Business Central vs Finance & Operations

The organisation has chosen Microsoft as its future ERP vendor. The remaining question is which Dynamics 365 platform best fits the business: Business Central (BC) or Finance & Operations (F&O). Both are strong cloud-based solutions, but they serve different types of companies.

Business Central is built for mid-sized organisations that want a system to grow with them. It offers full finance, supply chain, and warehouse management capabilities. It handles multi-company and multi-currency operations well, and it integrates tightly with Microsoft 365 and Power BI. Business Central is also faster to deploy and more cost-effective, which makes it attractive when deadlines are tight.

Finance & Operations is designed for larger enterprises. It comes with advanced warehouse management out of the box, deeper supply chain functionality, and powerful tools for financial consolidation. It is ideal for complex businesses with thousands of users and advanced compliance needs. The trade-off is a longer project timeline and higher licensing and implementation costs.

In this case, the organisation has 30–40 users and four subsidiaries. It needs real-time reporting, compliance across regions, and an integrated warehouse solution. These requirements point towards Business Central as the better fit. It offers everything needed at a lower cost and with a faster go-live path. F&O may add value for larger organisations, but here it risks adding complexity without clear benefit.

The choice must still be validated during discovery, but the evidence suggests that Business Central provides the right balance of scalability, cost, and agility for this project.

Modules Required for Go-Live

The project scope calls for all subsidiaries and modules to go live at the same time. This is ambitious, but it ensures the business avoids running two ERPs in parallel for too long. The required modules cover every key area of operations.

Finance is at the centre of the rollout. The system must handle general ledger, accounts payable, accounts receivable, and multi-currency transactions. It also needs localisation and electronic invoicing to meet compliance rules in each country. Without this, the business risks delays and errors in tax reporting and financial statements.

Supply chain management is another priority. Procurement, intercompany trade, and demand forecasting will all sit inside Dynamics 365. By consolidating these processes, the business can gain real-time visibility of supplier performance, future demand, and stock positions across its global operations.

Warehouse management is critical because WAER WMS will be retired. Dynamics 365 must take over with bin control, mobile scanning, and smooth pick and pack workflows. This will improve efficiency and reduce duplicate work in the warehouse.

Customer service is included in scope. The new ERP must support ticket and case management as well as SLA tracking. This ensures that service teams can log, track, and resolve issues without relying on separate systems.

Planning and budgeting will add forecasting and approval workflows. Finance leaders will be able to compare forecasts with actuals in real time. Combined with Power BI, which will replace Phocas BI, reporting will become more accurate and accessible.

Optional modules, such as CRM, HR, intelligent order management, and eCommerce, may be added later. For now, HubSpot continues to handle CRM and website functions, so the initial rollout stays focused on core business processes.

Data Migration: The Make-or-Break Factor

NetSuite data migration is often the most difficult part of a project. It is not just about moving records from one system to another. It is about making sure the new ERP starts with clean, accurate, and reliable information. If this step is rushed, every other process will suffer.

In this case, the business expects to migrate three years of historical data. This includes master records for customers, vendors, SKUs, pricing, and inventory. It also covers open sales and purchase transactions, general ledger balances, and accounts payable and receivable aging. Without this, users would struggle to manage day-to-day operations after go-live.

The role of the vendor is key. They must guide the business through cleansing and deduplication. NetSuite data migration services often reveal duplicate customer or vendor records that can distort reports. Mapping NetSuite data to Dynamics 365 structures also requires expertise. The two systems store information differently, and poor mapping can create reporting errors and compliance risks.

A balanced strategy works best. Migrating decades of history can be costly and unnecessary. Instead, keeping three to five years of active data inside Dynamics while archiving older data ensures reporting integrity without adding unnecessary weight.

Testing is the final safeguard. Running both NetSuite and Dynamics in parallel before go-live helps confirm balances, reconcile transactions, and build user confidence. Vendors like Dynamics Square UK provide proven NetSuite data migration best practices and templates that make the process faster and far less risky.

Integration Requirements

One of the main reasons this business is leaving NetSuite is the number of external systems it relies on. Each extra tool adds cost, risk, and duplicate effort. A smooth migration means replacing or connecting these systems in a way that feels natural inside Dynamics 365. This is where strong NetSuite migration services add value.

HubSpot CRM will remain the system of record for customer data and marketing. The new ERP must connect to HubSpot for orders and customer sync. By using a standard integration, the business avoids custom development and ensures both systems stay aligned.

Power BI will replace Phocas BI. The integration must deliver real-time dashboards inside Dynamics 365. This allows users to move from raw transactions to live analytics in one place. Finance, sales, and operations teams will all gain insight without switching platforms.

Banking integration is also a priority. The current system does not offer automated reconciliations. With Dynamics 365, the business wants direct connections to banking platforms. This will reduce manual entry, speed up closing, and cut down on human error.

Vendors with proven experience as NetSuite migration experts know how to design these integrations without over-engineering. They understand that every custom link creates long-term maintenance costs. Partners like Dynamics Square UK focus on using standard connectors and proven methods. The result is a system that works better on day one and stays easier to manage over time.

Reporting Requirements

Reporting is one of the weakest parts of the current setup. NetSuite relies on Phocas BI for analysis, but this adds cost and slows down access to information. Teams want live insights, not static reports that arrive days late. This is why the NetSuite migration strategy for this project puts Power BI at the centre of reporting.

The business needs clear financial statements, including profit and loss, balance sheet, and cash flow reports. Sales leaders want performance data broken down by region, customer, and channel. The supply chain team needs live inventory status, accurate forecasts, and supplier performance metrics. Managers across all areas want to compare forecasts against actuals without waiting for manual reports.

Role-based access is critical. Finance should see cash flow in detail, while warehouse staff need inventory dashboards. Dynamics 365 with Power BI delivers this by embedding reports directly into the ERP. Teams can view dashboards tailored to their role while still pulling data from the same single source of truth.

This approach marks a shift from reactive to proactive management. Instead of asking why numbers are wrong weeks later, leaders can act in real time. It is a major reason why more companies are choosing ERP migration from NetSuite to Dynamics 365.

Vendor Responsibilities

The choice of vendor will decide whether this project succeeds. The business expects a partner who can deliver the full scope. That begins with discovery and process design. The vendor must map how the company works today and design how it should work tomorrow. They must also recommend the right platform between Business Central and Finance & Operations.

Next comes functional and technical implementation. The vendor must configure modules, workflows, and security roles to meet the needs of each subsidiary. They must also build compliance into the system for the UK, EU, Canada, and US operations. Errors here could cause financial or legal risks, so experience is vital.

Data migration and validation are central tasks. The partner must plan how to move master records, open transactions, and balances from NetSuite into Dynamics.

Integration setup must cover HubSpot CRM, the new eCommerce site, Power BI, and banking connections. Each integration must be tested to remove duplicate data and ensure smooth workflows.

The vendor must also lead user acceptance testing (UAT), training, and change management. A system is only as strong as its adoption. Staff across regions must feel confident and supported in using Dynamics 365.

Finally, the vendor must provide go-live support and hypercare. This includes close monitoring of the system after cutover, rapid issue resolution, and guidance for users adapting to the change.

Conclusion

This project is about more than swapping one ERP for another. It is about leaving behind the limits of NetSuite and building a platform that drives growth, efficiency, and insight. With four subsidiaries, multiple currencies, and a licence deadline looming, the stakes are high.

Between Business Central and Finance & Operations, the evidence points to Business Central as the right fit. It balances functionality, cost, and speed, while still supporting global operations and future expansion.

Yet the platform choice is only half the story. Success depends on the partner that delivers the migration. The right partner brings proven methods, real-world experience, and the ability to guide data, integrations, and users through change.

If your business is planning its own move away from NetSuite, start the conversation now. The deadline may be 2026, but the work begins today.