Migrating from Microsoft Dynamics NAV or Business Central On-Premises to Business Central SaaS (cloud) is one of the most impactful — and most underestimated — projects an IT leader can run in 2026. Done right, you unlock continuous updates, Copilot AI features, lower TCO, and a future-proof platform. Done wrong, you risk data loss, broken integrations, weeks of downtime, and frustrated users.

This complete checklist walks you through every phase of a successful BC migration to cloud: pre-migration assessment, planning, data migration, customization handling, testing, and cutover. Use it as your project management framework.

By the end of this guide, you’ll have a complete project plan, realistic cost and timeline expectations, and a clear decision framework for whether to DIY or hire a Microsoft Partner.

Why Migrate from On-Prem to BC SaaS in 2026?

If you’re still running Dynamics NAV 2009-2018 or Business Central On-Premises, here’s why migrating to BC SaaS is increasingly urgent:

• Microsoft’s investment is cloud-first All new features (Copilot AI, advanced analytics, modern UI) ship to SaaS first or only
• NAV is end-of-life Mainstream support for NAV 2018 ended in 2023; extended support ends 2028
• On-Prem updates are manual SaaS gets 2 major releases per year, automatically
• Lower infrastructure cost No SQL Server licenses, no Windows Server, no on-call IT for patches
• Built-in Copilot AI Generative AI features only available on SaaS
• Better integrations Native Power Platform, Dataverse, Microsoft 365 integration
• Mobile + remote work  Browser-based BC works anywhere, no VPN needed
• Security + compliance  Microsoft handles patching, backups, GDPR controls, ISO certifications

Need expert migration help? BizCentralOrbit’s marketplace has Microsoft Solutions Partners experienced in on-prem to SaaS migrations. Browse migration consultants

3 Migration Paths (Pick Your Starting Point)

Your migration approach depends on what you’re migrating FROM:

Path A: Dynamics NAV 2015-2018 → BC SaaS

Difficulty: High
Duration: 4-9 months
Key challenge: NAV uses C/AL code which must be converted to AL extensions. Database schema requires multiple intermediate upgrades.
Microsoft tool: Cloud Migration Tool (free) + Code Modernization tools

Path B: BC On-Premises 14-20 → BC SaaS

Difficulty: Medium
Duration: 2-5 months
Key challenge: AL extensions need cloud compatibility check. Customizations to base objects need rework.
Microsoft tool: Cloud Migration Tool (free)

Path C: BC SaaS → BC SaaS (re-implementation, fresh start)

Difficulty: Low-Medium
Duration: 1-3 months
Key challenge: Decide what data to bring (master only, or transactional history too).
Microsoft tool: Manual data export + Configuration Packages

Pre-Migration Assessment: 10 Questions to Answer FIRST

Before writing a single line of migration code, answer these 10 critical questions. Skipping this step is the #1 cause of failed migrations:

1. What version are we on? NAV 2009 R2, NAV 2018, BC 14, BC 18, etc. Determines upgrade path.
2. How customized is our system? Count C/AL or AL objects modified from standard. Heavily customized = longer migration.
3. What integrations are connected? EDI partners, e-commerce, banks, CRM, payroll. Each needs reconnection strategy.
4. How many users + concurrent users? Affects SaaS license sizing (~₹6,000-8,500/user/month).
5. How much data and how much history? Customer ledger entries, GL entries, item ledger. Drives migration time + cost.
6. What 3rd-party add-ons are installed? Each add-on needs cloud version or replacement.
7. What’s our acceptable downtime window? Determines cutover strategy (big-bang weekend vs phased).
8. Who are the change champions? Identify users who’ll champion adoption + train others.
9. What’s the budget? Realistic SMB migration: ₹15-50 lakh. Mid-market: ₹50 lakh-2 crore.
10. Who owns this project? Need named executive sponsor + project manager + functional + technical leads.

The Complete BC Migration Checklist (5 Phases)

Use this as your project management framework. Each phase has clear deliverables and exit criteria.

PHASE 1  Assessment & Planning (2-4 weeks)

Goal: Understand current state, design target state, build the project plan.

Tasks:

•  Complete the 10-question pre-migration assessment above
• Inventory all C/AL or AL customizations (count objects, lines of code)
• Document all 3rd-party add-ons + check cloud compatibility
• Map all integrations (incoming + outgoing, with protocols)
• Identify which data to migrate (master + how much history)
• Confirm SaaS licensing requirements (Essentials vs Premium, user counts)
• Build TCO comparison (current on-prem cost vs SaaS cost over 3 years)
• Define success criteria (uptime, data integrity, user satisfaction targets)
• Choose migration approach (lift-and-shift vs re-implementation)
• Build project plan with milestones, dates, resources
• Identify executive sponsor + project team
• Get budget approval

Phase 1 Exit Criteria: Signed-off project charter, budget, team, timeline.

PHASE 2  Cloud Migration Tool Setup (1-2 weeks)

Goal: Establish the technical connection between your on-prem system and BC SaaS tenant.

Tasks:

• Provision BC SaaS production + sandbox environments
• Set up Azure AD tenant if not already in place
• Install Cloud Migration Tool on your on-prem BC server (or NAV upgrade path first)
• Configure connection between source (on-prem) and target (SaaS)
• Map source companies to target companies
• Test connection with a small data sample
• Document any connectivity issues + resolutions
• Set up Azure DevOps or GitHub for AL source control
• Create Power Platform environment (for Power BI + Power Automate)

Phase 2 Exit Criteria: Successful test data migration of small sample (e.g., 10 customers + 10 items).

PHASE 3  Data Migration (2-6 weeks)

Goal: Move master data and transactional history (per scope) to BC SaaS.

Tasks:

• Clean master data in source system (remove duplicates, fix invalid entries)
• Document chart of accounts mapping (source target)
• Run pilot migration to sandbox
• Validate data integrity (row counts, sums, totals match source)
• Identify and resolve data conflicts
• Migrate setup data (number series, posting groups, etc.)
• Migrate master data (Customers, Vendors, Items, GL Accounts, Dimensions)
• Migrate open transactions (open invoices, open POs, open production orders)
• Migrate historical data per scope decision (e.g., 2 years history)
• Reconcile financial balances (source vs target)
•  Get sign-off from finance team that financials match

Phase 3 Exit Criteria: Data in sandbox matches source for all critical entities; finance team has signed off on reconciliation.

PHASE 4  Customizations & Extensions (2-8 weeks)

Goal: Rebuild any customizations as AL extensions (not modifications to base objects).

Tasks:

• Convert C/AL customizations to AL extensions (if migrating from NAV)
• Refactor AL customizations to be cloud-compatible (remove forbidden APIs)
• Replace .NET-based functionality with AL or Azure Functions
• Implement event subscribers instead of direct base object modifications
• Update permission sets for new AL objects
• Migrate or rebuild reports (RDLC layouts often need rework)
• Configure web services / APIs for integrations
• Reconnect 3rd-party integrations (test each end-to-end)
• Replace deprecated 3rd-party add-ons with cloud-compatible alternatives
• Test customizations against new BC version (often a newer version than source)
• Code review + security review of all AL code
• Deploy extensions to sandbox environment

Phase 4 Exit Criteria: All customizations working in sandbox; UAT (User Acceptance Testing) completed.

PHASE 5  Cutover & Go-Live (1-2 weeks)

Goal: Switch users from on-prem to SaaS production with minimal disruption.

Tasks:

• Final user training delivered (with refreshers)
• Cutover plan documented (hour-by-hour for go-live weekend)
•  Communication plan executed (notify all stakeholders)
• Freeze on-prem changes 48 hours before cutover
• Final delta data migration (transactions since last full sync)
• Final reconciliation (source = target)
• Deploy extensions to SaaS production
• User access provisioning (assign licenses, security roles)
• Go-live announcement to all users
• Hyper-care support (dedicated team for first 2 weeks)
• Daily issue triage meetings (first 2 weeks)
• Document lessons learned
• Plan formal decommissioning of on-prem system (typically 30-60 days after go-live)

Phase 5 Exit Criteria: Users productive on SaaS, hyper-care issues resolved, on-prem decommissioning plan signed off.

Common Migration Pitfalls (And How to Avoid Them)

Pitfall #1: Underestimating Customization Complexity

Problem: Team assumes “we’ll just rebuild it” without measuring effort. Reality: every customization needs analysis, redesign, AL development, testing.
Fix: Get a partner to do a customization audit upfront. Estimate effort per customization. Expect 4-8 hours per simple customization, 20-40 hours per complex one.

Pitfall #2: Migrating Too Much History

Problem: Moving 10 years of transactional data inflates migration time + cost + ongoing storage.
Fix: Migrate only what’s actively needed (typically 2 years). Archive older data to read-only sources. Most countries require 7-year retention but it can be in archive, not active system.

Pitfall #3: Ignoring 3rd-Party Add-Ons

Problem: Critical add-on (e.g., shipping integration) has no cloud version. Discovered weeks before go-live.
Fix: Inventory ALL add-ons in Phase 1. Contact each vendor for cloud roadmap. Have alternative chosen BEFORE Phase 4.

Pitfall #4: Big-Bang Cutover Without Sufficient Testing

Problem: All users switch at once without UAT. Issues compound, users frustrated, productivity drops.
Fix: Run parallel mode for 2-4 weeks if possible (both systems live). Phased cutover by department reduces risk. Always do full UAT with real business scenarios.

Pitfall #5: Skimping on User Training

Problem: “BC SaaS looks like BC On-Prem, users will figure it out.” Reality: modern UI, new features, removed features cause confusion.
Fix: Budget 2-4 hours of training per power user, 1 hour per casual user. Provide quick reference cards. Run open Q&A sessions weekly post-go-live.

Pitfall #6: Forgetting Permissions + Security Roles

Problem: Users get “permission denied” on go-live day. Frustration + support tickets explode.
Fix: Map every on-prem user to a SaaS security role in Phase 3. Test permissions in sandbox with actual user accounts.

Cost Expectations for BC Migration in 2026

Migration cost depends heavily on company size, customization level, and partner choice. Realistic ranges:

Company Size	Users	Customization Level	Migration Cost (India)	Duration
Small	5-15	Standard / Light	₹10-25 lakh	2-4 months
Small	5-15	Heavy customization	₹25-50 lakh	4-6 months
Mid-Market	16-50	Standard	₹30-75 lakh	4-6 months
Mid-Market	16-50	Heavy customization	₹75 lakh – 1.5 crore	6-9 months
Enterprise	50+	Any	₹1-3 crore+	6-12 months

Plus ongoing costs:

• BC SaaS Essentials: ¹6,000/user/month
• BC SaaS Premium: ¹8,500/user/month
• Team Member: ¹650/user/month (for occasional users)
• Ongoing support: 15-20% of license cost annually

For a detailed breakdown by module, read our BC Implementation Cost Guide 2026.

DIY vs Hire a Microsoft Partner  Decision Framework

Should your team handle the migration internally, or hire a Microsoft Solutions Partner? Here’s how to decide:

DIY Migration Makes Sense If:

• You have an in-house BC functional consultant + AL developer
• Your customizations are minimal (under 10 modified objects)
• You’re migrating from BC On-Prem 18+ (recent versions, easier path)
• You can dedicate 3-6 months of internal team time
• Your data volume is small (under 100K customer records)
• You’re comfortable being your own first-line support post-go-live

Hire a Microsoft Partner If:

• You’re migrating from Dynamics NAV (complex code conversion needed)
• You have significant customizations (50+ modified objects)
• You have many 3rd-party integrations
• You don’t have in-house BC technical expertise
• You need this completed within 3-4 months
• You want documented Microsoft Solutions Partner accountability
• The cost of a failed migration would significantly impact business operations

Hybrid Approach (Most Common):

• Hire partner for migration tooling + customization conversion
• Your team owns data cleanup + user training + change management
• Best balance of cost and risk for most mid-market organizations

Resources for Your Migration Journey

Free Resources

• BizCentralOrbit YouTube Channel â€” Migration tutorials, AL conversion examples
• BizCentralOrbit Blog â€” Articles on BC, AL, MB-800, Power BI integration, cost guides
• Microsoft Cloud Migration Tool docs â€” Official Microsoft migration documentation

1-to-1 Migration Consultant

BizCentralOrbit’s marketplace includes Microsoft Solutions Partners experienced specifically in on-prem to SaaS migrations. They offer:

• Migration assessment + scoping (typically a paid 1-2 week engagement)
• Full migration project delivery (5-9 month engagements)
• C/AL to AL code conversion services
• Post-go-live hyper-care support
• Power BI dashboard setup on migrated data

Browse BC migration consultants on BizCentralOrbit

Related Reading

• Business Central AL Development Beginner’s Guide  For AL conversion work
• Power BI Integration with Business Central  For analytics setup on new SaaS
• BC Implementation Cost Guide 2026  Detailed budget planning
• BC Licensing Explained  Choose right SaaS licenses
• Business Central Certifications 2026  MB-800 + MB-820 cert paths

Frequently Asked Questions

How long does a BC migration from on-prem to SaaS take?

For small businesses (5-15 users) with standard customizations, expect 2-4 months. Mid-market (16-50 users) with heavy customizations: 4-9 months. Enterprise (50+ users): 6-12 months. The biggest variables are amount of customization, number of integrations, and data volume. Migrating from Dynamics NAV (versus BC On-Prem) typically adds 1-3 months due to code conversion complexity.

How much does a BC migration to SaaS cost?

Migration cost in India ranges from ₹10-25 lakh for small businesses with light customization, ₹30-75 lakh for mid-market standard migrations, and ₹1-3 crore for enterprise or heavily customized environments. Plus ongoing SaaS licensing at ₹6,000-8,500/user/month for Essentials/Premium. The cost depends heavily on customization level, data volume, integrations, and partner choice.

Can I migrate from Dynamics NAV directly to BC SaaS?

Not directly in one step. The Microsoft Cloud Migration Tool requires NAV 2015 or later as the source. Older NAV versions need intermediate upgrades first (e.g., NAV 2009 → NAV 2018 → BC SaaS). Additionally, C/AL code from NAV must be converted to AL extensions for cloud compatibility. This conversion is often the longest single task in a NAV-to-SaaS migration.

Will my customizations work in BC SaaS?

Not automatically. SaaS only supports AL extensions (not direct C/AL modifications). All customizations must be: (1) converted from C/AL to AL if coming from NAV, (2) refactored to use event subscribers instead of base object modifications, (3) checked for forbidden APIs (e.g., direct .NET interop is restricted in SaaS), (4) repackaged as proper extensions. This is typically 30-50% of total migration effort for customized systems.

What happens to my data history when I migrate?

You decide. The Cloud Migration Tool can move all historical data or just recent data. Most organizations migrate 2 years of active data and archive older data separately. Migrating less data: faster migration, lower storage costs, easier reconciliation. Migrating more data: full analytics history, no separate archive system needed. Discuss with your finance and compliance teams which approach fits your regulatory requirements.

Can I run on-prem and SaaS in parallel during migration?

Yes, and it’s often recommended. The Cloud Migration Tool supports incremental sync, so you can keep both systems updated for weeks during testing. Some organizations run parallel for 30-60 days post-go-live before fully decommissioning on-prem. This provides a safety net if critical issues emerge but doubles licensing costs for that period.

Do I need a Microsoft Partner to migrate to BC SaaS?

Not strictly required, but recommended for most migrations. DIY makes sense if you have in-house BC functional and AL technical resources, minimal customizations (under 10 modified objects), and 3-6 months of available team time. Hire a Microsoft Solutions Partner if you have heavy customizations, NAV-to-BC code conversion needs, multiple integrations, or want documented accountability. The hybrid approach (partner for technical work, internal team for change management) is most common for mid-market organizations.

Conclusion

BC migration from on-prem to SaaS is one of the highest-impact IT projects you’ll run this decade. It’s also one of the most commonly mishandled. The difference between success and failure isn’t technical skill — it’s project discipline.

Use this checklist as your project framework:

1. Phase 1 (Weeks 1-4): Complete assessment, get budget approval, build team
2. Phase 2 (Weeks 5-6): Set up Cloud Migration Tool + sandbox environments
3. Phase 3 (Weeks 7-12): Migrate and reconcile data
4. Phase 4 (Weeks 13-20): Convert customizations, test extensions, run UAT
5. Phase 5 (Weeks 21-22): Final cutover, hyper-care, decommission on-prem

If your project is larger or smaller, adjust the durations — but don’t skip phases.

Ready to start your migration? Hire a vetted BC migration consultant from BizCentralOrbit â€” our marketplace includes Microsoft Solutions Partners with deep on-prem to SaaS migration experience.