[object Object]

A 90-employee distributor outgrows QuickBooks and asks a partner for ERP recommendations. The shortlist is Business Central, NetSuite, and a vertical solution. Six weeks into evaluation the team realizes the choice is less about features and more about implementation cost and time to value. Business Central wins these evaluations when the partner can show a 90-day live date with a tightly scoped initial deployment.

Who It Is For

Small and mid-sized orgs running full ERP — finance, inventory, sales, purchasing, manufacturing (light). Cloud-first but on-prem available. Tier 2 pricing compared to F&O. The sweet spot is 25 to 250 employees, single or few legal entities, and operations that fit the standard BC modules without heavy customization.

BC fit signals:
- Need full ERP, not just accounting
- Currently on QuickBooks, NAV, GP, or a vertical accounting tool
- Inventory and purchasing matter to the business
- Microsoft 365 already in use (Teams, Outlook, SharePoint)
- IT department under 5 people or partner-supported

Core Modules

Finance (GL, AP, AR), Sales and Marketing, Purchasing, Inventory, Manufacturing, Service, Projects. Fewer knobs than F&O; faster time-to-value. The modules ship on by default; enable only what you need to keep the user experience focused.

Module enablement order:
Week 1-4: Finance, AR, AP
Week 5-8: Inventory, Purchasing
Week 9-12: Sales, Service
Post-go-live: Manufacturing, Projects, advanced features

The 90-day go-live target is realistic when the data migration is clean and the customizations are minimal.

Extending BC

AL language extensions run on the BC server. AppSource hosts thousands of industry and country extensions. Do not modify base objects — extend. Modifying base objects breaks upgrade compatibility and forces you off the standard release cadence. Extensions preserve upgrade safety.

pageextension 50100 "Sales Order Card Ext" extends "Sales Order"
{
    layout
    {
        addafter("Sell-to Customer No.")
        {
            field("ctn_PriorityFlag"; Rec."ctn_PriorityFlag")
            {
                ApplicationArea = All;
                ToolTip = 'Mark as priority order';
            }
        }
    }
}

The extension model is the modern standard. AppSource extensions follow the same pattern, which means upgrades from custom to AppSource solutions are usually clean.

Power Platform Integration

Dataverse virtual entities expose BC data to Power Apps. Common pattern: BC as source of truth, Power Apps for niche UI, Power BI for reporting. The virtual entity pattern means Power Apps developers can read BC data without learning AL.

Common integration patterns:
- Power BI for executive dashboards on BC data
- Power Automate for cross-app workflows (BC + Outlook + Teams)
- Power Apps canvas for mobile field apps over BC
- Custom connectors for non-Dataverse integrations

Migration from NAV / GP

Automated migration tools cover a lot of NAV to BC. GP to BC is harder (different data model). Budget conservatively. Partner engagement for data migration is usually worth it. The NAV migration is mostly a version upgrade plus some object cleanup; the GP migration is more of a re-implementation.

NAV to BC effort:
- Lift base data: 2 to 4 weeks
- Convert customizations to extensions: 2 to 8 weeks
- UAT and reconciliation: 4 weeks
- Total: 2 to 4 months for typical mid-market

GP to BC effort:
- Map data model differences: 3 to 6 weeks
- Rebuild reports and customizations: 6 to 12 weeks
- UAT and reconciliation: 6 weeks
- Total: 4 to 8 months for typical GP customer

Localization

BC supports country localizations through extensions, including tax engines and statutory reporting. The localization quality varies by country. Tier 1 markets (US, UK, Germany, Australia) have mature localizations; smaller markets sometimes need partner-built supplements.

Sizing Tenants

A single BC tenant supports multiple companies (legal entities). Most multi-entity orgs use one tenant with one company per legal entity. Cross-company reporting works through Power BI; native cross-company posting requires careful chart of account alignment.

Going Live and Ongoing Operations

The go-live week is intense; plan for it. Cutover the financial period at month-end, freeze data entry in the legacy for 24 to 48 hours, run the migration, validate trial balance, and open BC for production. Ongoing operations require one or two trained super-users in the customer organization plus partner support for monthly close issues.

What to do this week

If you are evaluating BC, run the fit checklist with your finance lead. If you are mid-implementation, audit your customizations for base-object modifications and convert to extensions. Plan the cutover weekend in detail before you commit to a date.

[object Object]
Share