+1 480 485 7373
Microsoft Teams
Three Business One habits that shape the plan
G/L determination by item group
Many Business One companies set G/L accounts by item group or by warehouse. Business Central does this with general business, product and inventory posting groups. A posting setup matrix combines them.
- ✓Each item group becomes an item category plus the right posting groups
- ✓Warehouse-level account rules become inventory posting setup per location
- ✓Revenue and cost accounts set once in the posting matrix
UDFs, UDTs and formatted searches
User-defined fields on business partners, items and documents all need a verdict. So do user-defined tables and objects, and formatted searches that fill fields automatically.
- ✓Reporting UDFs become dimensions
- ✓Operational UDFs become table extension fields
- ✓Formatted search logic becomes defaults, templates or AL code
Distribution rules and profit centers
Cost accounting dimensions with distribution rules split postings by percentage across profit centers. Business Central uses dimensions for the tags and allocation accounts for percentage splits.
- ✓Each B1 dimension becomes a Business Central dimension
- ✓Fixed distribution rules become allocation accounts
- ✓Projects on documents map to projects or a dimension
SAP Business One mapping table
Document chains and what is still open
Business One links documents in a chain. On the sales side it runs quotation to order to delivery to A/R invoice. On the purchasing side it runs purchase order to goods receipt PO to A/P invoice. At cutover some of those chains are half finished, and each break point needs its own treatment. Open sales orders load as new Business Central sales orders with the remaining quantity. Deliveries without an invoice are the trickiest. We either invoice them in Business One before cutover, or load them as shipped-not-invoiced documents so no revenue goes missing.
On the purchasing side, goods receipt POs without an A/P invoice sit in an allocation account in Business One. In Business Central, an interim receipts account holds the same position. We load those receipts, so you can match the vendor invoice when it arrives. Open A/R and A/P invoices come across one by one with their due dates. Down payments and unapplied payments do too. The rest of the ledger arrives as a trial balance by account and dimension. Closed documents stay in the Business One database, which you can keep read-only for lookup and audit.
In an SAP Business One to Business Central migration, inventory loads last. It loads as quantity per item, location, bin and lot, valued at the Business One cost on the cutover date. Business One can value by moving average, standard or FIFO, and can hold costs per warehouse. Business Central sets the costing method per item and can calculate average cost per location. So we agree the method item by item before the first load.
Queries, layouts and add-ons to rebuild
Query Manager SQL
Saved SQL queries become list views with saved filters, analysis mode views or Power BI reports. The choice depends on who reads them.
Crystal and PLD layouts
We redesign invoices, delivery notes and purchase orders from Crystal Reports or the Print Layout Designer as Word report layouts.
Approval procedures
Approval stages on orders and invoices become Business Central approval workflows, with Teams or email notifications to approvers.
SDK add-ons and Service Layer links
AppSource apps, standard features or AL extensions replace add-ons and integrations built on the DI API or Service Layer.
Cutover sequence for a Business One company
- 1
Clean up in Business One
Close stale sales and purchase orders and invoice old deliveries. Merge duplicate business partners and items while users still know the history.
- 2
Extract
Export masters and open documents with Query Manager or directly from the SQL Server or HANA database into mapping workbooks.
- 3
Load masters
Load customers, vendors, items, price lists and BOMs into Business Central through configuration packages and test them in a sandbox.
- 4
Post opening positions
Post the trial balance, open receivables and payables, and inventory by location, bin and lot. Each posts against a clearing account that must end at zero.
- 5
Reconcile and go live
Match aging, stock value and trial balance to Business One on the cutover date, then switch integrations and start transacting.
Business One migration FAQ
Is there a Microsoft tool that moves SAP Business One data into Business Central?
We do not rely on one; an SAP Business One to Business Central migration runs on configuration packages and scripts. The real work is deciding how item groups, UDFs and distribution rules should become posting groups, fields and dimensions. Scripted extracts from the Business One database let us repeat the load in a sandbox until it reconciles. The same scripts then run for the final cutover.
What happens to our user-defined fields?
Each UDF gets one of three outcomes: dimension, extension field, or left behind. Fields used for reporting and analysis become dimensions so they appear on every ledger entry. A small extension adds fields that support a process, such as a delivery route or a customer portal flag. Fields nobody has filled in for a long time stay in the Business One archive.
Do we need Business Central Premium after SAP Business One?
You need Premium if you run production orders; assembly BOMs work in Essentials. Business One production BOMs map to Business Central production BOMs and routings, which are a Premium feature. Sales and assembly BOMs map to assembly BOMs, available in Essentials. Check current licence details on Microsoft's pricing page or in a partner quote.
More SAP Business One to Business Central migration questions
Can we keep our item numbers and business partner codes?
Yes, in almost all cases you can keep them. Business Central item and customer numbers accept alphanumeric codes, so existing codes load as they are. A business partner that is both customer and vendor becomes two records. We usually keep the same code on both for clarity. Codes longer than the Business Central field length are the exception, and we flag those during mapping.
How is inventory costing handled when Business One costed by warehouse?
Business Central can calculate average cost per location, which is the closest match to warehouse-level costing. You set the costing method per item, so standard, FIFO and average items can live side by side. We load opening stock per location at the Business One value on the cutover date. We then run the cost adjustment and compare inventory value to the Business One stock report before go-live.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.