Migrate from ERP BOS to Microsoft Dynamics 365 Business Central

BOS ERP Customer records (with contact details, billing address, credit limits, and account balance) map 1:1 to D365 Customer. Business Central uses the Customer card; D365 Finance and Supply Chain Management uses CustTable. Credit limit maps to CreditMax, payment terms map to PaymentTermsId, and the BOS entity branch assignment maps to a D365 Customer posting profile or responsibility centre. Inactive customers are flagged during scoping and imported as blocked or archived records to avoid inflating the destination CRM.

BOS ERP Vendor records (with payment terms, tax registration, and banking details) map to D365 Vendor. Business Central uses the Vendor card; D365 Finance and Supply Chain uses VendTable. Tax registration number maps to TaxRegistrationNumber, payment terms map to PaymentTermsId, and bank account details map to VendBankAccount. Address records are linked via the Address and Communication sub-entities.

BOS ERP Items (both inventory stock and non-stock products) map to D365 Items or ReleasedProducts. SKU, unit of measure, and standard cost migrate directly. Custom item fields in BOS ERP require field-mapping against the destination schema; any custom fields not available in D365 are held for a custom field provisioning step before import. Multi-level BOMs are extracted in full and flagged for BOM flattening work as a separate configuration step (see gotcha on BOM depth).

BOS ERP BOM structures with routing steps and multi-level assemblies map to D365 Production BOMs (Business Central) or BOM/Formula lines (Finance and Supply Chain Management). We extract the full BOM hierarchy during scoping, document the parent-child relationships, and flatten multi-level BOMs into single-level BOM lines where the destination edition does not support nested BOM nesting. The customer-side production consultant reviews and approves the flattened structure before import.

BOS ERP COA (account codes, descriptions, and classification as Asset, Liability, Income, Expense) maps to D365 MainAccount. Each BOS account requires classification against D365 Account Type (Revenue, Expense, Asset, Liability, Equity), Account Category, and posting definition. The full COA hierarchy is exported as a structured record set; parent-child relationships are preserved via the MainAccount struct in Finance and SCM. Configuration data (account type, posting profile, category group) must be imported before opening balances to satisfy D365 validation rules.

BOS ERP's multi-entity architecture means each branch has a separate ledger with inter-company transaction tracking. We extract per-entity ledgers and assign a destination Company code (Business Central) or Legal Entity ID (Finance and SCM). Inter-company transaction pairs (recorded in BOS ERP as debits and credits across entity IDs) are extracted as a cross-reference table and flagged for D365 elimination journal design. The customer-side finance team reviews elimination account treatment before consolidation data is finalized.

Open AR items migrate as Customer Ledger Entries (Business Central) or CustTransOpen records (Finance and SCM) with open/closed status, due date, amount, and currency preserved. Aged trial balance data is reconciled against the COA control accounts before migration. We flag discrepancies between the AR sub-ledger balance and the COA receivable control account; the customer must reconcile these in BOS ERP before we transfer open items to avoid aged trial balance errors and incorrect credit limit calculations in D365.

Open AP items migrate as Vendor Ledger Entries (Business Central) or VendTransOpen records (Finance and SCM) with open/closed status, due date, amount, and currency preserved. Same AP/AR reconciliation discipline applies: we extract both sub-ledger balances and COA balances from BOS ERP and flag discrepancies. The customer reconciles in BOS ERP before we transfer open items; otherwise the destination system carries forward imbalances affecting vendor payment runs and cash forecasting.

BOS ERP tax codes and rates are extracted from the accounting setup and mapped to D365 tax configuration. Business Central uses Tax Group and Tax Posting Setup; D365 Finance and Supply Chain Management uses TaxCode with TaxGroup and TaxSubGroup hierarchy. We preserve the BOS tax code identifier as a reference field in D365 so that the tax setup can be validated against BOS ERP's jurisdiction configuration during reconciliation.

Bank accounts and cash ledgers in BOS ERP are part of the COA structure. We migrate bank account balances and reconcile against the last BOS ERP statement date. Bank account details map to D365 BankAccount with account number, SWIFT/BIC, and bank name fields. Bank statement history is migrated as journal line records; the customer configures the bank reconciliation workflow in D365 post-migration.

BOS ERP's Service Manager module handles customer enquiry tracking and opportunity management. Open service records migrate with enquiry status, priority, and associated customer link preserved. If the destination D365 deployment includes Service module, service records map to Service Order; if it is Finance and Supply Chain only, they map to Sales Order or Project. Closed service records are archived with a closed status flag rather than imported as open items to avoid inflating the destination service queue.

BOS ERP document management module stores binary files (invoices, images, signed documents) linked to transactions. We do not migrate binary document blobs through the data pipeline. We extract document metadata (document ID, filename, type, linked transaction reference, creation date) and produce a document-index CSV for separate file transfer to SharePoint or D365 Dataverse blob storage. This workstream runs in parallel with the transactional migration to avoid timeout issues with large attachment volumes.