Migrating from SAP Business One to Business Central

SAP Business One (B1) and Business Central compete for the same SMB ERP slot. Migrations between them go in both directions, but the more common direction in markets where Microsoft has strong partner coverage is B1 → Business Central — often driven by total-cost-of-ownership, Microsoft 365 integration, or partner preference.

The functional fit

SAP B1 and BC overlap heavily in scope: financials, sales, purchasing, inventory, light manufacturing, basic CRM, service management. Country localizations exist on both. The data models are different in detail (B1's posting model, item structure, and dimension equivalents diverge from BC's), but the conceptual mapping is straightforward.

Migration strategy.

• Cut-off date. Year-end is cleanest; quarter-end is feasible. Mid-year requires careful opening-balance handling.
• History. Typically migrate balances + open transactions; leave detailed history in B1 read-only.
• Tools. Unlike QuickBooks, BC does not ship a first-party B1 migration wizard. The standard approach is:
  • Export B1 data to CSV/Excel using B1's standard export tools or direct SQL queries against the HANA or SQL Server database.
  • Cleanse and transform offline.
  • Import to BC via Configuration Packages or the REST API.
• Several ISVs publish dedicated B1-to-BC migration accelerators that automate the bulk of this.

Mapping concerns.

• Chart of accounts. B1's account structure and posting groups differ from BC's. Most projects redesign the chart of accounts using the migration as the catalyst.
• Dimensions. B1 has dimension-like cost centres and profit centres; BC's dimensions are richer. Map deliberately — don't carry forward B1's structure unchanged.
• Items. B1 has detailed item attributes (configurable), BOMs, prices, and tracking. BC's item card has different but largely equivalent functionality. Variants, attributes, and tracking need explicit mapping.
• Sales and purchasing documents. Both products use a quote → order → delivery → invoice flow with similar mechanics. Open documents migrate as open BC documents with quantities and amounts preserved.
• Banking. B1's bank module is more sophisticated in some countries; BC's bank reconciliation has caught up and now includes AI matching.

Customisation rebuild

B1 customisations are usually built in SAP B1 SDK / SQL queries / formatted searches — not portable to BC. Re-build them as AL extensions in BC. Many B1 customisations turn out to be unnecessary in BC once standard features are properly used; do the fit-gap honestly before committing to rebuild.

Reporting

B1 reports built in Crystal Reports won't run in BC. Replace with Power BI for analytical reporting and Word layouts for document reports.

The change-management challenge

B1 users are accustomed to a specific UI and a particular vocabulary. BC's terminology and workflow are similar but not identical. Plan training that explicitly addresses the differences, not generic BC training.

Time to live

A typical B1-to-BC migration is 4 to 9 months including configuration, integration rebuild, and testing.

Where to go next

The wider SAP-versus-Microsoft picture is Dynamics 365 vs SAP. Design the target with dimensions design, migrate with Business Central data migration, rebuild Crystal Reports with document layouts and report design, and plan the difference-focused training with training strategies.