Migrate from Sage Intacct to Microsoft Dynamics 365 Business Central

Sage Intacct GL accounts map to Business Central G/L Account records via the REST API or Data Delivery Service export, with account numbers, names, types (Balance Sheet vs Income Statement), and active/inactive status preserved. The account hierarchy in Sage Intacct (parent/child accounts) maps to the Business Central Account Category structure. We flag any accounts with a Balance type that will require opening balance journal entries in Business Central at cutover.

Historical journal entries migrate to Business Central General Journal lines. Sage Intacct's dimensional tags (department, class, location, customer, project) require explicit mapping to Business Central Analysis columns or account segments during import. Source records without dimensional tagging are imported as summary lines without the analytical granularity, and we document which GL lines lost dimension coverage so the customer's finance team can evaluate whether re-tagging is cost-effective post-migration.

Sage Intacct Dimensions (department, class, location, customer, project) are a core architectural concept with no direct equivalent in Business Central. We map Dimensions to Analysis Columns (Business Central's built-in dimensional reporting feature) where supported, and to account segments or custom fields on the G/L Entry table for Dimensions that exceed Analysis Column capacity. We produce a dimensional gap report listing every Sage Intacct Dimension value that cannot map natively, with recommended manual post-migration setup steps.

Open Sage Intacct AP bills migrate to Business Central Vendor records and Purchase Invoice lines. We flag any Sage Intacct bills in a 'pending approval' state because Business Central requires posted invoices or approved purchase orders—no draft state equivalent that auto-posts on import. Vendor payment terms, default dimensions, and purchase posting groups map to Business Central's Vendor Card and Vendor Posting Group fields.

Open Sage Intacct AR invoices migrate to Business Central Customer records and Sales Invoice lines. We map customer balance-forward vs open-item AR settings from the source to Business Central's Customer Posting Group configuration to preserve collection history. Any AR invoices in a draft or non-posted state in Sage Intacct are flagged for the customer's admin to decide whether to post before migration or re-enter as drafts in Business Central.

Sage Intacct Customer master records map to Business Central Customer records, including addresses, payment terms, and default posting groups. Custom fields on Customer objects (up to 100 in Sage Intacct) require explicit schema discovery and mapping to Business Central Customer-specific extension fields. Customer-to-Contact relationships in Sage Intacct map to the Contact subtable in Business Central Customer card.

Sage Intacct Vendor master records map to Business Central Vendor records, including addresses, payment terms, and default GL accounts. Vendor custom fields require the same explicit schema discovery pass as Customer custom fields. Vendors with multi-entity assignments in Sage Intacct require intercompany setup in Business Central as a separate configuration step.

Sage Intacct Item records (description, unit price, cost, GL association) map to Business Central Item records. Bundle and matrix items in Sage Intacct require explicit parent-child relationship mapping; these map to Business Central as BOM/family items or as product variants under a common item number. Unit of measure mappings must be reconciled between the two systems' UoM tables before import.

Sage Intacct Project headers and task hierarchies migrate to Business Central Job and Job Task records. We preserve project status, billing type, customer association, billable vs non-billable flags, and WIP calculations. Revenue recognition schedules require recalculation in Business Central because Sage Intacct and Dynamics 365 use different recognition engines. Grant tracking from Sage Intacct's nonprofit module maps to Job WIP fields; a full grant management replacement requires a nonprofit-specific Business Central extension.

Sage Intacct Fixed Asset records migrate to Business Central Fixed Asset cards, preserving acquisition cost, acquisition date, asset class, and serial number. Depreciation schedules require recalculation in Business Central because each jurisdiction uses different conventions (straight-line, declining balance, sum-of-years digits). We transfer the complete asset register and document the original depreciation convention so the customer's accountant can verify the Business Central schedule before first depreciation run.

Sage Intacct budget line data can be exported and re-imported into Business Central Budget Entries, but the Planning module scenarios and what-if models do not have a native equivalent in Business Central. We map budget periods and amounts to the correct fiscal year and G/L account combinations in Business Central. If the customer used Sage Intacct Planning extensively, we recommend Microsoft Dynamics 365 Finance and Operations or a third-party FP&A tool as the scenario planning replacement.

Sage Intacct custom objects (database-table-equivalent objects with API access) map to Business Central custom tables created via AL extensions. We pre-create the destination schema including all custom fields, lookup relationships, and validation rules before data import. Sage Intacct's '!' prefix on custom object fields in the API requires explicit stripping or replacement during the transform step. Custom object naming must be reviewed against Business Central's reserved word list to avoid API conflicts.

Sage Intacct's entity hierarchy, inter-company transaction rules, and consolidation mappings require Business Central to be configured either as multiple company databases or as a single database with Intercompany setup. We extract the full entity-to-entity routing rules from Sage Intacct and map them to Business Central's Dimensions, Business Units, or Intercompany Chart of Accounts setup depending on which approach the customer's implementation partner recommends. Cross-entity GL entries receive a separate migration pass to ensure they resolve to the correct company in the destination.

Document attachments stored within Sage Intacct are not accessible via the REST API for bulk export. We recommend a parallel document migration strategy such as SFTP file transfer or SharePoint/OneDrive migration alongside the record migration. We provide a written inventory of document attachment locations in Sage Intacct for the customer's IT team to handle via the chosen file migration method.

Employee records, compensation history, and PTO balances migrate via Sage Intacct's REST API to Business Central Employee records where the Payroll module is in scope. If Sage Intacct Payroll is not deployed, we migrate only the employee master (name, address, employment status). Actual payroll runs and tax configurations do not migrate because payroll processing is module-gated in both systems and requires separate jurisdiction-specific setup in Business Central.