Migrate from Unit4 ERP to Microsoft Dynamics 365 Business Central

Unit4 Customer records carry billing and delivery addresses, payment terms, currency, and tax registration. We map these to Dynamics 365 Customer records (Business Central) or CustTable (Finance and Operations). Credit limits, payment days, and any custom address-role extensions transfer as custom fields or dimension values in the destination. Customer type (person vs company) maps to the Dynamics 365 CustomerType field.

Unit4 Supplier master records include bank details, W-9/W-8 status, multi-address support, and tax registration. We map these to Dynamics 365 Vendor records, preserving remittance addresses and payment terms. 1099 and withholding tax configuration migrates as vendor tax settings in the destination.

Unit4 supports multidimensional account structures with cost centres, departments, and projects as natural axes. Dynamics 365 Finance and Operations uses a Main Account (6-digit or longer code) with up to 10 financial dimensions (such as BusinessUnit, Department, CostCentre, Project). We extract the customer's full account structure from Unit4's relational tables, propose a dimension-mapping strategy during scoping (which Unit4 dimension maps to which Dynamics 365 dimension), and configure the Account Structure in the destination before any account master data loads. Business Central uses a simpler COA with optional default dimensions rather than mandatory dimensional structures.

Unit4 General Ledger account masters (account code, description, account type, posting controls, currency settings) map to Dynamics 365 Main Accounts. Account type (Revenue, Expense, Asset, Liability, Equity) maps directly. We flag any accounts with posting rules that do not map cleanly to Dynamics 365 posting profiles and resolve during the sandbox migration phase.

Unit4 Items include GL mapping, cost price, sales price, item type (Stock, Service, Resource), and stock control flags. We map to Dynamics 365 Item (Business Central) or Released Product (Finance and Operations), preserving pricing matrices as sales prices and purchase prices, and stock flags as inventory posting groups. Complex pricing matrices in Unit4 require a per-item strategy discussion during scoping because Dynamics 365 represents trade agreements differently.

Outstanding Unit4 AP and AR invoices (document headers, line items, due dates, amounts, currency, payment terms) carry forward as open records in Dynamics 365. We preserve the original invoice numbers as references, due dates, and currency codes. AR invoices load as open Customer Transaction records; AP invoices load as open Vendor Transaction records. Payment terms and cash-discount terms migrate from Unit4 to Dynamics 365 payment terms.

Posted Unit4 journal entries with header, lines, and audit stamps (posting date, source reference, user ID) transfer as locked records in Dynamics 365 General Journal. We preserve posting dates, source document numbers, and user stamps to maintain audit trails. Only the last 12-36 months of journal history migrates by default; the date window is agreed during scoping. Journal batch names and posting profiles map to Dynamics 365 journal names and posting profile settings.

Unit4 holds country-specific tax matrices with rates, jurisdictions, and posting rules. We map these to Dynamics 365 Tax Groups and Tax Codes, flagging any jurisdiction combinations that do not have a direct Dynamics 365 equivalent. VAT/GST, withholding tax, and sales tax configurations require separate mapping workstreams because tax posting accounts in Unit4 must resolve to corresponding main accounts in Dynamics 365.

Unit4 Asset master records include depreciation schedules, cost centres, insurance values, and asset groups. Dynamics 365 supports fixed asset books with depreciation methods (Straight-line, Declining Balance, Units of Production). We align per-asset-class depreciation methods during scoping—Unit4 and Dynamics 365 may use different default conventions, and a conversion table per asset category resolves the difference. Depreciation posted to date in Unit4 becomes the acquisition cost and accumulated depreciation in Dynamics 365.

Unit4 stores document attachments against transactions and master records via its document management API. We extract these files and re-associate them in Dynamics 365 as record attachments. File-size limits (typically 10 MB per file in Dynamics 365 Business Central; configurable in Finance and Operations) may require splitting larger documents. We document any attachments that exceed these limits for customer review.

Unit4 bank account masters with currency, account type, and reconciliation settings migrate to Dynamics 365 Bank Accounts. Opening balances map to bank account balances in the destination. We reconcile opening balances post-migration against Unit4's trial balance to confirm the bank account balances in Dynamics 365 are accurate before the first bank reconciliation cycle.

Unit4 HCM holds employment history, compensation, job titles, department assignments, and effective-dated changes. We map to Dynamics 365 Worker (Finance and Operations with HR) or Employee (Business Central). Effective-dated changes in Unit4 require careful sequencing because Dynamics 365 HR stores employment information differently—position hierarchies, employment events, and compensation structures each need a separate mapping workstream. Employee cost rates and billing rates used in project accounting transfer as cost price and sales price on the related Worker or Employee records.

Unit4 Projects are the primary work-identification layer with WBS elements, cost objects, billing rates, and resource assignments. Dynamics 365 Finance and Operations Project Management or Business Central Jobs require mapping the Unit4 project structure to a project type (Time and Material, Fixed Price, Investment). Cost categories in Dynamics 365 must be mapped to Unit4 cost object types. Hourly billing rates from Unit4 migrate to Dynamics 365 Transactions > Hour categories. Project manager assignments resolve to the Worker or User lookup in the destination.

Unit4 Grant Management handles donor restrictions, fund balances, and reporting for nonprofits and public-sector bodies. We map grant codes to Projects with dedicated financial dimension values (such as a Grant dimension or Project dimension) that carry the funding restriction across every transaction line. Spend-vs-budget records map to budget planning in Dynamics 365 Finance and Operations or to custom budget-check workflows. Donor restrictions are preserved as dimension values so that reporting against fund restrictions is possible without custom development. This mapping requires extensive scoping for organisations with complex grant structures.