Migrate your Microsoft Dynamics 365 Business Central data

Customer master records with addresses, contacts, payment terms, and credit limits are exposed as standard data entities. We map source CRM accounts or contacts directly to the Customer entity using the primary address and contact fields. The customer-posting group assignment controls where GL entries land and must be set during migration to avoid posting errors.

Vendor master records mirror Customer structure with pay-to addresses, payment terms, and vendor posting groups. We map source vendor records and preserve the vendor-posting group so that AP ledger entries are routed correctly. Vendor-level blocked status must be explicitly carried over to prevent open PO acceptance in the new system.

Items are the inventory or service product records that drive sales and purchase transactions. Business Central distinguishes Inventory Items, Services, and Non-Inventory Items. We map source product SKUs to the appropriate Item Type, copy Unit of Measure relationships, and preserve the inventory posting group. Bill of Materials (BOM) structures for manufactured items are migrated as separate Production BOM entities.

The Chart of Accounts defines the posting structure and must align with the selected country/localization template (e.g., US, UK, DE). Source GL accounts may use a different numbering scheme, so we map account numbers and carry forward the account category and subcategory assignments. Account type restrictions (Posting, Heading, Total) are preserved to maintain financial reporting hierarchies.

Sales Documents (Orders, Invoices, Credit Memos) are header-line structures with customer references, lines, and amounts. We map open orders from the source system, preserving document dates and due dates. Already-invoiced history is migrated as posted sales invoices linked to the customer ledger. Pricing and discount logic on sales lines must be explicitly transferred because Business Central stores line discounts as a combination of invoice discount groups and line discount percentages.

Open purchase orders are migrated as Purchase Orders with expected receipt dates and quantities. Posted AP invoices are mapped to the Vendor Ledger and G/L registers. Prepayments on purchase orders are supported in Business Central but require specific setup — we flag these and migrate the related prepayment invoice entries separately.

Item Ledger Entries, Value Entries, and Warehouse Entries are separate but related tables. We migrate open item ledger entries (quantity on hand, pending receipts, shipments) and preserve cost layers. Historical posted entries can be migrated selectively — we scope with the customer whether full inventory history or just open quantities are needed, as large transaction histories increase migration time significantly.

Jobs in Business Central combine WBS-style task breakdowns, resource time entries, and job journal postings. We map source project or work order records to Jobs, create task lines matching the source WBS hierarchy, and migrate time entries as Job Journal lines. Jobs-Personnel interaction requires that the resource be set up as a Resource with a cost and price.

Employee records include demographic data, employment information, and bank account details for payroll integration. Business Central's HR capabilities are basic compared to dedicated HRMS platforms. We migrate active employees as Resources when job costing or job scheduling is in scope, and map employment-effective-dated changes to the Employee record's job history section.

Bank Account records store bank details, statement formats, and posting groups. We map source bank account records and carry forward the bank account posting group. Open bank account ledger entries (outstanding checks, deposits in transit) are migrated as unreconciled bank ledger entries for the customer to reconcile post-go-live.

Fixed Asset records include acquisition cost, depreciation books, and insurance coverage. We map source fixed asset registers, preserve depreciation schedules and book assignments, and carry forward accumulated depreciation balances as opening FA journal entries. Budget information on fixed assets is migrated as separate FA Budget entries.

Approval workflow definitions are tied to specific user accounts, delegate settings, and response limits configured within Business Central. These are environment-specific and not portable between tenants via API. We do not migrate approval workflow definitions; we document the workflow structure and recommend the customer rebuilds approval routing in the destination environment post-migration.