Migrate from BusinessCloud to Microsoft Dynamics 365 Business Central

BusinessCloud General Ledger accounts map to Business Central G/L Accounts. Account type (header, posting, total) maps to Account Category and Direct Posting fields. Account number and name migrate directly. If BusinessCloud uses cost center or profit center dimensions, we map those to Business Central dimensions by creating dimension values under the Dimensions table before account import so that the Dimension ID reference is satisfied at insert time. Balance carryforward requires posting an opening balance journal entry as the final step of the migration sequence.

BusinessCloud customer master records map to Business Central Customer records. BusinessCloud address data (stored as a single formatted string in many regional ERPs) must be split into Address Line 1, Address Line 2, City, State, ZIP, and Country Code fields using a parsing transform applied during staging. Customer posting group and payment terms map to Business Central Posting Group and Payment Term ID respectively. Currency code from BusinessCloud maps to Currency ID on Customer if the destination uses multi-currency configuration.

BusinessCloud vendor master records map to Business Central Vendor. Address parsing logic mirrors the customer address transform described above. Vendor posting group and payment terms map to Posting Group and Payment Term ID. If BusinessCloud stores vendor-specific tax registration numbers (TRN for UAE, VAT number for KSA), these map to the Tax Registration Number field on Vendor in Business Central. Vendor balance carryforward posts as a vendor ledger entry journal after all open purchase documents are migrated.

BusinessCloud items map to Business Central Item records with Type (Inventory, Service, Non-Inventory) inferred from the item's inventory tracking settings in the source. Unit of Measure must be resolved because BusinessCentral requires a Unit of Measure Code on Item; we extract the primary UOM from BusinessCloud's item record or apply a default (EA for each). Standard Cost and Unit Price migrate to Unit Cost and Unit Price fields. If BusinessCloud uses product dimensions (size, color, style), we create Business Central variants under the parent Item.

Open BusinessCloud sales orders migrate to Business Central Sales Order records with status set to Open. Order number becomes External Document Number. Customer number, shipment address, and payment terms map from the Customer migration step. Sales order lines map with Item number, quantity, unit price, line discount, and tax information. BusinessCentral requires the Item to already exist in the destination before the sales order line is inserted, enforcing the Items-before-SalesDocuments dependency order. Header discounts and charges require mapping to Business Central Invoice Discount fields or invoice posting groups.

Open BusinessCloud purchase orders migrate to Business Central Purchase Order records. Vendor number, buy-from address, and payment terms map from the Vendor migration step. Purchase order lines map Item number, quantity, direct unit cost, line discount, and tax information. The dependency chain requires Vendor before Purchase Order, and Item before Purchase Order line, enforced as a phased migration sequence.

Posted BusinessCloud sales invoices migrate as Sales Invoice records with status Posted. Invoice number becomes External Document Number. Customer and address map from the Customer migration step. Invoice lines carry Item, quantity, unit price, tax amount, and discount. Posted invoices in BusinessCentral cannot be edited; we validate all field mappings and tax calculations during the staging phase before inserting. If historical invoices span closed fiscal years, we post them as read-only journal entries rather than editable invoices per BusinessCentral date-based posting restrictions.

Posted BusinessCloud purchase invoices migrate as Purchase Invoice records with status Posted. Vendor and address map from the Vendor migration step. Invoice lines carry Item or G/L Account number, quantity, direct cost, tax, and discount. The same closed-fiscal-year restriction applies: invoices in locked accounting periods migrate as journal entries with a reference to the original invoice number rather than as editable purchase invoices.

BusinessCloud inventory transactions (receipts, issues, adjustments, transfers) map to Business Central Item Ledger Entry records (quantity tracking) and Value Entry records (valuation tracking). Each transaction type generates the appropriate entry type in BusinessCentral: Positive Adjustment for receipts, Negative Adjustment for issues, Transfer for movements. Inventory valuation method (FIFO, Average, Standard) from BusinessCloud maps to Costing Method on Item, which must be set before any inventory transactions post.

BusinessCloud employee records migrate to Business Central Employee if the HR module is in scope. Employee number, first name, last name, address, and employment status map directly. If the Business Central edition deployed does not include HR ( Essentials tier does not include Human Resources ), employees map to Contact records with a custom Contact Type field set to Employee. The scope decision between Employee and Contact migration is confirmed during discovery based on the BusinessCloud data dump contents.

BusinessCloud notes and file attachments associated with master records (Customer, Vendor, Item) and transactional records (Sales Order, Purchase Order) migrate as Business Central Record Link entries. The Link URL field stores the attachment reference, and the Note field stores text notes. Binary attachments migrate as Incoming Document records in BusinessCentral or as file references in a linked SharePoint or Azure Blob container if the customer uses document management integration.

Any custom entities discovered during BusinessCloud schema probing migrate to Business Central as custom tables built using the Extension model or as custom fields added to standard tables. BusinessCentral allows unlimited custom fields on standard tables (Customer, Vendor, Item, G/L Account, Sales Header) using field extension pages. We pre-create the destination schema, including custom field types, ranges, and option values, before the first data insert. The discovery phase may reveal custom objects unique to the customer's BusinessCloud configuration (such as project trackers, compliance logs, or MENA-specific entities) that require bespoke mapping logic.