Skip to content
Get a quote

Sage Intacct to Business Central migration

We migrate GL histories, open AP/AR, dimensional transaction tags, customer and vendor masters, and project structures from Sage Intacct into Microsoft Dynamics 365 Business Central, resolving the posted-vs-non-posted account state, the no-sandbox API constraint, and every Dimension that lacks a native Business Central equivalent before any record moves.

Short answer

FlitStack AI migrates g/l accounts, general journals, analysis column or account segments, vendor ledger entries + purchase lines and customer ledger entries + sales lines from Sage Intacct to Business Central, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 5-8 weeks.

By

Source Sage Intacct
DestinationBusiness Central
G/L AccountGeneral JournalAnalysis Column or Account SegmentVendor Ledger Entries + Purchase LinesCustomer Ledger Entries + Sales Lines
Mapped field by field · sample run · one-click rollback

What moves from Sage Intacct to Business Central?

Moving from Sage Intacct to Microsoft Dynamics 365 Business Central is a schema redesign, not a direct record copy.

Read the full summary

Sage Intacct attaches Dimensions (department, class, location, customer, project) as analytical tags on every GL transaction and uses a multi-entity hierarchy with inter-company routing; Dynamics 365 Business Central uses a traditional segment-based chart of accounts and multi-company or intercompany setup. We pre-design the destination COA to absorb the most important dimensional categories as account segments or Analysis columns, and we flag the rest in a dimensional gap report for the customer's admin to handle post-migration. Sage Intacct's posted vs. non-posted transaction state affects open AP/AR migration because drafts cannot be imported as posted records in Business Central. We do not migrate Workflows, Approval Routes, Sage Intacct Planning scenarios, or document attachments as those objects have no transferable equivalent or are inaccessible via API. We deliver a written inventory of every active automation and workflow for the customer's admin to rebuild in Dynamics 365.

1:1

General Ledger Accounts → G/L Account (Chart of Accounts)

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.

How it maps

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.

1:1

Journal Entries → General Journal

Historical journal entries migrate to Business Central General Journal lines.

How it maps

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.

configuration

Dimensions → Analysis Column or Account Segment

Sage Intacct Dimensions (department, class, location, customer, project) are a core architectural concept with no direct equivalent in Business Central.

How it maps

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.

1:1

Accounts Payable Bills → Vendor Ledger Entries + Purchase Lines

Open Sage Intacct AP bills migrate to Business Central Vendor records and Purchase Invoice lines.

How it maps

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.

1:1

Accounts Receivable Invoices → Customer Ledger Entries + Sales Lines

Open Sage Intacct AR invoices migrate to Business Central Customer records and Sales Invoice lines.

How it maps

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.

1:1

Customers → Customer

Sage Intacct Customer master records map to Business Central Customer records, including addresses, payment terms, and default posting groups.

How it maps

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.

What moves15 objects
Sage IntacctBusiness Central
  • General Ledger AccountsG/L Account1:1
  • Journal EntriesGeneral Journal1:1
  • DimensionsAnalysis Column or Account Segmenttransformed
  • Accounts Payable BillsVendor Ledger Entries1:1
  • Accounts Receivable InvoicesCustomer Ledger Entries1:1
  • CustomersCustomer1:1

+ 9 more in the mapping below

How Sage Intacct and Business Central differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionSage IntacctBusiness Central
Analytical tagging modelDimensions as tagged values on every transaction (department, class, location, customer, project)Segment-based COA with optional Analysis columns; no native per-transaction dimension tagging at Business Central level
Multi-entity architectureParent-child entity hierarchy with cross-entity GL routing and inter-company eliminationsMultiple company databases or Intercompany setup; entity consolidation requires separate configuration post-migration
Pricing modelCustom per-organization subscription; per-user costs scale aggressively beyond 5 finance usersPer-user per-month starting at $70/user; Business Central Essentials includes core financials, Supply Chain, and Project Management in one flat tier
API sandbox availabilityNo sandbox; trial accounts expire at 30 days and must be recreated per regionSandbox environments available in all tiers for development, testing, and validation before production migration
Custom field API namingCustom fields prepend '!' in REST API payloads (e.g., !region) but display without prefix in UICustom fields follow standard naming conventions; custom fields on standard tables use field-level extension objects
Project accounting depthNative task-level billing, revenue recognition, and grant tracking with per-project WIPProject Management module covers job costing and time/expense; grant tracking requires a nonprofit-specific extension or third-party add-on
Fixed asset depreciationDepreciation schedules fully configurable per jurisdiction; fixed asset register migratableFixed Asset module available but depreciation recalculation required post-migration due to jurisdictional convention differences

What to watch for in a Sage Intacct to Business Central migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Dimensions have no native equivalent in Business Central

Sage Intacct Dimensions (department, class, location, customer, project) are tagged on every transaction at the API level and appear in every report without manual column setup.

How we handle it

Microsoft Dynamics 365 Business Central does not have a native per-transaction dimension tagging model equivalent to Sage Intacct's. We map the most operationally critical Dimension types to Business Central Analysis Columns and account segments, but Dimensions that exceed Analysis Column capacity require a manual setup pass post-migration. We produce a dimensional gap report listing every Dimension value that cannot map natively so the customer's finance team can decide whether to re-tag historically or accept the reduced analytical granularity.

high

No sandbox environment forces trial-only API validation

Sage Intacct does not provide a sandbox or development environment.

How we handle it

Trial accounts expire after 30 days and must be recreated per region. We test all API calls and schema discovery against a short-lived trial tenant before running the production migration. Any changes to custom objects or custom fields must be validated in the trial first. This constraint means that if the production schema differs significantly from the trial (which is common after months of live use), we may discover additional unmapped fields only during the production migration run. We mitigate this by running a schema snapshot via Sage Intacct's REST API against production before the trial expires.

medium

Posted vs. non-posted AP/AR states require explicit flagging before import

Sage Intacct distinguishes between posted and non-posted transactions, and draft or pending-approval AP bills or AR invoices cannot be imported as posted records in Business Central.

How we handle it

When migrating open AP/AR, we run a pre-export filter to flag every record in a draft or pending approval state and surface it to the customer's controller before migration begins. The customer decides whether to post those records in Sage Intacct before export or to re-enter them as drafts in Business Central after import. Skipping this step results in Business Central rejecting unmapped draft records with posting group validation errors.

medium

Sage Intacct API rate limit overages are billed in transaction packs

Sage Intacct enforces a default rate limit of 180 requests per minute with a burst of 10 calls per second.

How we handle it

Migrations that exceed their contracted API transaction quota incur overage charges billed in packs of ten. We monitor transaction counts via the Sage Intacct Usage Insights report before and during migration and throttle our API calls to stay within contracted limits. For migrations with large historical GL volumes or many custom object records, we negotiate a temporary rate-limit increase with the customer before starting the migration job to avoid unexpected overage billing.

low

Custom fields use '!' prefix in Sage Intacct REST API only

Sage Intacct prepends a '!' character to custom field names in the REST API but not in the UI.

How we handle it

A field called 'Region' in the Sage Intacct UI appears as '!region' in API payloads and responses. We discover all custom fields on every object during schema mapping, apply the '!' prefix in our extraction scripts, and verify field values land in the correct Business Central extension field location after import. Failing to apply the prefix results in silent field omissions during export that are difficult to trace back after the source system is closed.

How the migration runs

  1. Discovery and migration scope definition

    We audit the source Sage Intacct environment: entity count, GL account structure, dimensional coverage (which dimensions are populated on historical transactions vs left blank), open AP/AR volume and approval state distribution, project count and status, fixed asset register size, custom object schemas and relationships, and active workflow/approval definitions.

    What this step covers

    We pair this with a Dynamics 365 Business Central edition assessment: Essentials ($70/user) covers core financials, supply chain, and project management; Premium adds service management. The discovery output is a written migration scope document that defines what migrates, what maps natively, and what goes to the dimensional gap report.

  2. Dimensional gap analysis and COA design

    We analyze every Sage Intacct Dimension type (department, class, location, customer, project) and determine which map to Business Central Analysis Columns, account segments, or custom fields on G/L Entry.

    What this step covers

    For Dimensions that cannot map natively, we document the gap and recommend whether the customer's finance team should re-tag historically, accept reduced granularity, or implement a Business Central extension for full dimensional reporting. We then design the Business Central Chart of Accounts structure to absorb the approved dimensional categories, and configure Analysis Columns for the primary analytical views.

  3. Trial schema validation and custom field discovery

    We run all schema discovery and API validation against a Sage Intacct trial account before the 30-day expiration.

    What this step covers

    We extract every custom object definition, every custom field on every standard object, and the full dimensional value lists. We map custom field names (including the '!' API prefix stripping) to Business Central extension field names. Any schema gaps discovered in trial that differ from production are flagged in the migration scope addendum before production migration begins.

  4. Multi-entity routing design and entity structure extraction

    We extract the complete Sage Intacct entity hierarchy, inter-company transaction routing rules, and consolidation mapping configuration.

    What this step covers

    We map this to either a multiple-company Business Central deployment or an intercompany single-database setup, in coordination with the customer's implementation partner. Cross-entity GL entries receive a dedicated migration pass to ensure each line routes to the correct destination company. We produce a company mapping table as the handoff artifact for the customer's Dynamics 365 partner.

  5. Production migration in dependency order

    We run production migration in this order: G/L Accounts (with account type and opening balance), Dimensions (as Analysis Column definitions or segments), Customers, Vendors, Items, Fixed Assets (acquisition data only), open AP/AR (filtered to posted records, with draft-state records listed separately), Projects and Job Tasks, Journal Entries with dimensional tags, Budget Entries, Custom Objects (after standard object dependencies are resolved), and Employee records.

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. Open AP/AR draft-state records are surfaced in a separate queue for the customer's controller to resolve before closing the Sage Intacct instance.

  6. Cutover, dimensional gap handoff, and automation inventory delivery

    We freeze Sage Intacct writes during cutover, run a final delta migration of any records modified during the migration window, then enable Business Central as the system of record.

    What this step covers

    We deliver the dimensional gap report listing every Sage Intacct Dimension value that cannot map natively, with step-by-step manual setup instructions for Business Central's Analysis Columns or extension fields. We also deliver the written inventory of every Sage Intacct Workflow, Approval Route, and Planning scenario for the customer's admin or Dynamics 365 implementation partner to rebuild in Business Central. Document attachments are inventoried separately for SFTP or SharePoint migration. We support a one-week hypercare window for reconciliation issues.

Sage Intacct Business Central
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Business CentralRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

5-8 weeksTypical, smaller accounts
12-20 weeksLarge or heavily customised accounts

A quote scales with historical GL volume, dimensional tagging density, number of entities, and whether open AR/AP carries a significant draft-vs-posted split. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Sage Intacct to Business Central →

Why teams move from Sage Intacct to Business Central

  • Sage Intacct's per-user pricing becomes prohibitively expensive at scale. Growing from 5 to 20 finance users inflates the monthly bill significantly, while Dynamics 365 Business Central Essentials bundles core financials, supply chain, and project management at a flat per-user rate that Microsoft reports as $70 per user per month for the Starter tier. Organizations with large finance teams cite this as the primary cost driver for switching, with G2 reviewers noting the pricing differential widens as headcount grows beyond the five-user sweet spot that Sage Intacct's pricing was designed around.
  • Sage Intacct's implementation requires a certified Sage Partner and multi-month consulting engagements that add substantial cost beyond the software subscription. Dynamics 365 Business Central has a broader ecosystem of implementation partners and a more documented migration path from competing ERPs, including third-party tools purpose-built for Dynamics GP to Business Central migrations. Reviewers switching from Sage Intacct to Dynamics 365 on TrustRadius cite faster implementation timelines and lower partner fees as a secondary benefit.
  • Dynamics 365 Business Central offers manufacturing, warehouse management, ecommerce, and field service modules that Sage Intacct does not include natively. Organizations expanding beyond pure financial management need these operational modules, and Sage Intacct's response is a marketplace of third-party integrations rather than native capability. Companies planning to grow into operations or supply chain management choose Dynamics 365 for the integrated ERP footprint rather than stitching together separate systems.
  • Sage Intacct's frequent bugs and slow error resolution generate consistent negative sentiment across Capterra and G2. Reviewers cite a 62% negative sentiment around software reliability and support responsiveness, with post-vs-non-posted transaction handling adding friction to month-end close. Organizations running complex multi-entity environments report that Sage Intacct's error messages lack the specificity needed to resolve issues quickly, leading to extended close cycles and audit exposure. Dynamics 365 Business Central's support tiers include Microsoft 24x7 support with defined SLA response windows.
  • Organizations already committed to the Microsoft ecosystem—Azure Active Directory, Microsoft 365, Power Platform, Teams, SharePoint—see Dynamics 365 Business Central as the natural financial layer. Single sign-on, native Teams integration, Power BI reporting, and Power Automate workflows reduce the integration overhead that Sage Intacct imposes on non-Microsoft stacks. Reviewers on Reddit's r/intacct community note that the Microsoft ecosystem advantage compounds over time as new employees arrive already familiar with the Microsoft tooling.

Questions, answered

Sage Intacct to Business Central migration questions

How long does a Sage Intacct to Microsoft Dynamics 365 migration take?

Most migrations land between five and eight weeks for environments with under 50,000 GL lines, two or fewer entities, and no complex dimensional tagging requirements. Migrations with five or more entities, multi-year GL histories, incomplete dimensional coverage on historical source records, fixed asset depreciation schedule preservation, or multiple custom object schemas move to twelve to twenty weeks because of the dimensional gap analysis, multi-entity routing pass, and fixed-asset recalculation coordination. Dynamics 365 Business Central implementation partners typically add three to twelve months on top of migration for full configuration and testing.

Do Sage Intacct Workflows, Approval Routes, and Planning scenarios migrate to Dynamics 365?

No. Sage Intacct Workflows, Approval Routes, and Planning scenarios are not migratable as code. Sage Intacct uses a property-triggered workflow model with dimensional conditions that has no direct equivalent in Business Central's workflow engine. We deliver a written inventory of every active Workflow and Approval Route in Sage Intacct with its trigger conditions, approver chains, and recommended Business Central workflow equivalent (Workflow on Purchase Orders, Workflow on Sales Orders, or Approval Workflows), plus a separate Planning module gap report recommending Microsoft Dynamics 365 Finance and Operations or a third-party FP&A tool as the scenario planning replacement. The customer's Dynamics 365 implementation partner rebuilds these post-migration.

What happens to my dimensional transaction history during migration?

Sage Intacct Dimensions (department, class, location, customer, project) tag every transaction at the API level. We map the primary dimensional categories to Business Central Analysis Columns, which are available natively in all Business Central tiers. For Dimensions that exceed Analysis Column capacity or lack a native mapping, we produce a dimensional gap report listing every Dimension value that cannot map, with manual setup instructions for the customer's admin. Historical GL lines without dimensional tagging in the source system (a common issue when dimension adoption was inconsistent) migrate as summary lines without analytical granularity, and we flag which report views are affected.

Can Sage Intacct's multi-entity structure be preserved in Business Central?

Partially. Sage Intacct's entity hierarchy, inter-company routing rules, and consolidation mappings require a separate Business Central configuration pass. We extract the complete entity structure and map it to either multiple Business Central company databases (for strict data isolation) or a single-database intercompany setup (for shared chart of accounts). We produce a company mapping table as the handoff artifact for the customer's Dynamics 365 implementation partner, who configures the destination architecture. Cross-entity GL entries receive a dedicated migration pass to ensure each line routes to the correct destination company.

How do we handle Sage Intacct AP/AR drafts and non-posted transactions?

Sage Intacct distinguishes between posted and non-posted transactions, and Business Central cannot import a draft-state record as posted. We run a pre-export filter to identify every AP bill and AR invoice in a draft, pending approval, or non-posted state in Sage Intacct and surface this list to the customer's controller before migration begins. The customer decides whether to post those records in Sage Intacct before export or to re-enter them as drafts in Business Central after migration. We do not convert draft records in the transform step because doing so could create posting date conflicts in Business Central's fiscal period.

Are document attachments migratable from Sage Intacct?

Document attachments stored within Sage Intacct are not accessible via the REST API for bulk export. We provide a written inventory of every document attachment location in Sage Intacct (linked to specific records, vendors, customers, or projects) for the customer's IT team to handle via an alternative method—typically SFTP file transfer, SharePoint migration, or OneDrive synchronization alongside the record migration. We map the inventory to the corresponding Business Central record so that the file-structure migration preserves document-to-record associations.

Do we migrate Sage Intacct Payroll data to Business Central?

Employee master records, compensation history, and PTO balances migrate where the Sage Intacct Payroll module is in scope. Actual payroll runs, tax configurations, and jurisdiction-specific payroll setups do not migrate because they require jurisdiction-specific setup in Business Central's Payroll module. If the customer does not have Sage Intacct Payroll deployed, we migrate only the employee master (name, address, employment status, manager relationship). The customer should verify which Payroll tier is active in Sage Intacct during discovery so that we scope the employee migration appropriately.

Get a quote

Moving from Sage Intacct to Business Central?

Tell us roughly how many records and objects you have. We scope the mapping and the Business Central setup with you, then send a quote.

Get a quote