---
title: "Migrate to Business Central: ERP Migration Guide & Service"
description: "Migrating to Business Central? Import limits, the migration checklist and every source we move into it."
url: "https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central"
---

# Migrate to Business Central

Business Central is Microsoft's mid-market ERP whose migration model rewards teams that pre-build the chart of accounts, validate Configuration Packages in a sandbox, and treat the fiscal-period cutover as a separate workstream from master-data load.

Short answer

FlitStack AI migrates financial, supply chain, and operational data into Business Central from 200+ ERPs, including NetSuite, ERPNext, Encompass Production Cloud, Odoo ERP. Every field is mapped to Business Central's objects, history and associations come across, the Business Central setup is configured alongside, and the whole migration stays reversible in one click.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See every source →](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#sources-list)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

From Any source ![](https://flitstack.ai/platforms-trim/netsuite.webp) ![](https://flitstack.ai/platforms-trim/erpnext.webp) ![](https://flitstack.ai/platforms-trim/encompass-production-cloud.webp)

Destination Business Central ![](https://flitstack.ai/platforms-trim/microsoft-dynamics-365-business-central.webp)

NetSuite ERPNext Encompass Production Cloud Odoo ERP Sage Intacct

200+ sources mapped into Business Central

## Systems we move into Business Central

The ERPs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

[NetSuite to Business Central](https://flitstack.ai/migrations/erp/netsuite/to/microsoft-dynamics-365-business-central) [ERPNext to Business Central](https://flitstack.ai/migrations/erp/erpnext/to/microsoft-dynamics-365-business-central) [Encompass Production Cloud to Business Central](https://flitstack.ai/migrations/erp/encompass-production-cloud/to/microsoft-dynamics-365-business-central) [![](https://flitstack.ai/platforms-trim/odoo-erp.webp) Odoo ERP to Business Central](https://flitstack.ai/migrations/erp/odoo-erp/to/microsoft-dynamics-365-business-central) [Sage Intacct to Business Central](https://flitstack.ai/migrations/erp/sage-intacct/to/microsoft-dynamics-365-business-central)

## What Business Central supports, and where its import tools stop

- Deep integration with Microsoft 365, Power BI, and Power Platform means organizations already on the Microsoft stack get identity, reporting, and workflow continuity out of the box.
- Unified financials, sales, service, and operations replace multiple disconnected systems — users report that data entered once flows through purchase orders, invoicing, and approvals without manual re-entry.
- Copilot AI features (predictive analytics, embedded business intelligence) are included in both Essentials and Premium tiers, addressing demand for AI without separate module purchases.
- Named-user licensing with no concurrent model appeals to organizations that want predictable per-seat costs even if some users access the system infrequently.

**Bulk API** OAuth 2.0 (authorization code, client credentials, and on-behalf-of flows supported via Azure AD)

**Rate limits** Maximum 5 concurrent requests per user with a request queue size of 95; HTTP 429 returned when exceeded

| Object                       | Support | Note                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| ---------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Customers                    | full    | 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.                                                                                                                                 |
| Vendors                      | full    | 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                        | full    | 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.                                                                          |
| General Ledger Accounts      | mapped  | 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 Orders and Invoices    | mapped  | 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. |
| Purchase Orders and Invoices | mapped  | 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.                                                                                                                                                             |
| Inventory Transactions       | mapped  | 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 (Project Management)    | mapped  | 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.                                                                                                                                    |
| Employees                    | mapped  | 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 Accounts and Cash       | full    | 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 Assets                 | mapped  | 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 Workflows           | none    | 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.                                                                                                 |

## The Business Central migration guide

## Why teams migrate to Business Central

*The four shapes a Business Central migration takes, and what makes Microsoft's mid-market ERP easier — or harder — than the category average.*

Microsoft Dynamics 365 Business Central is the cloud successor to Dynamics NAV (Navision), released in 2018 and aimed at small and mid-sized organisations[1](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-1). It sits below Dynamics 365 Finance & Operations on price and complexity, and above QuickBooks and Xero on functional depth, with deep ties to Microsoft 365, Power BI, Power Automate and Azure Active Directory.

The typical Business Central customer is a 10 to 300-user mid-market business — manufacturers, distributors, professional services, non-profits — that has outgrown an entry-level accounting package or is exiting an aging legacy ERP. Per-user pricing runs $80/user/month for Essentials and $110/user/month for Premium, with implementation budgets that typically land $30,000 to $100,000+ depending on complexity. Per the Microsoft administrative tooling, a tenant is provisioned with 80 GB of database storage plus a per-user allowance[4](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-4).

The shapes of migration that actually land on Business Central fall into four patterns. First, Dynamics GP exits, driven by Microsoft's announced end of new GP subscription sales on April 1, 2026 and end of support in 2029-2031. Second, NAV-to-BC moves, where on-premises Navision customers shift to the cloud version using Microsoft's purpose-built cloud migration tool[6](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-6).

Third, QuickBooks and Xero graduations, where a growing business hits the ceiling on inventory, multi-entity or manufacturing features. Fourth, NetSuite consolidations, often M\&A-driven, where the parent standardises on Microsoft's stack for the Outlook, Teams and Power BI integration. Each shape has a different difficulty profile: a GP migration ships with Microsoft's own Data Migration Extension that pulls master data plus open transactions, while a QuickBooks move is essentially a re-implementation that uses Business Central's own Data Migration Wizard.

What makes migrating to Business Central easier than the category average is the Configuration Package mechanism built into RapidStart Services — an Excel-based ingestion path that handles master data, opening balances and journal entries with row-level validation before anything posts. The Outlook add-in, Teams card and Power BI embed work out of the box, so the post-migration adoption curve is shorter than for any ERP that needs a separate productivity layer wired in.

What makes it harder than the average is the posting groups architecture — every customer, vendor and inventory item must be assigned posting groups that drive the GL accounts hit on every transaction, and a missing or mis-mapped posting group blocks the entire posting process[9](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-9). The fiscal period and cutover model also bites: Business Central uses a date-based posting framework where unrolled prior periods can be re-posted into, useful for adjustments but unforgiving without deliberate period-close discipline during migration.

Workflows, custom reports, AL extensions and Power Automate flows do not import from the source ERP — they are rebuilt from documentation or re-developed in Visual Studio Code with the AL Language extension[10](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-10). Teams that scope for that work up front finish on time; teams that assume a push-button cloud migration finish late.

> Microsoft markets a push-button migration tool, but moving from GP to Business Central is a full ERP re-implementation — not an upgrade.

## The Business Central data model you need to map into

*Tables, posting groups, dimensions, and the No. fields you'll wire on every import — the destination schema decoded.*

Business Central organises data as tables surfaced through cards in the UI. Master data lives on its own tables — Customer, Vendor, Item, G/L Account — and transactional data flows through journals and documents that post into the General Ledger and subledger entry tables (Customer Ledger Entry, Vendor Ledger Entry, Item Ledger Entry).

Before mapping any source field, you need to know which destination table the row belongs on, its No. (number) format, and which posting groups drive its GL behaviour. The table below summarises the objects you will touch in any Business Central migration.

| Object                                   | What it stores                                                        | Required                                                                                   | Tier                                                                                                 |
| ---------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| G/L Account (Chart of Accounts)          | Ledger accounts for all financial postings                            | No., Name, Account Type, Income/Balance, Direct Posting flag                               | All tiers — foundation of every other table                                                          |
| Customer                                 | Sold-to parties for AR and sales documents                            | No., Name, Customer Posting Group, Gen. Bus./Bus. Posting Group, payment terms             | All tiers                                                                                            |
| Vendor                                   | Pay-to parties for AP and purchase documents                          | No., Name, Vendor Posting Group, Gen. Bus./Bus. Posting Group, payment terms               | All tiers                                                                                            |
| Item                                     | Inventoried and non-inventory products                                | No., Description, Base Unit of Measure, Inventory/Gen. Prod. Posting Group, Costing Method | All tiers (Premium for assembly/manufacturing depth)                                                 |
| Bill of Materials (Item BOM Header/Line) | Multi-level production and assembly structures                        | Parent No., Component No., Quantity per, UoM Code                                          | Premium (manufacturing) or Essentials (assembly only)                                                |
| Unit of Measure / Item UoM               | Base + alternate UoMs with conversion ratios                          | Code, Description, conversion factor on Item UoM                                           | All tiers[11](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-11) |
| Currency / Currency Exchange Rate        | ISO codes plus historical exchange-rate table                         | Code, Starting Date, Exchange Rate Amount, Relational Exch. Rate Amount                    | All tiers[12](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-12) |
| Dimension / Dimension Value              | Financial analytics tags (Department, Project, Location, Cost Centre) | Dimension Code, Code, Name; assignment via Default Dimensions                              | All tiers — replaces the GL sub-account in NAV/GP                                                    |
| Sales/Purchase Header + Line             | Open orders, invoices, credit memos — the document tables             | Document Type, No., Sell-to/Buy-from No., Posting Date, lines with Type + No. + Quantity   | All tiers                                                                                            |
| General Journal Line                     | Manual postings; the canonical path for opening balances              | Posting Date, Account Type, Account No., Amount, Bal. Account, Document No.                | All tiers                                                                                            |
| Fixed Asset                              | Capitalised assets with depreciation books                            | No., Description, FA Posting Group, Depreciation Book + Method                             | All tiers                                                                                            |
| Resource                                 | Time-based capacity (people, machines) for jobs                       | No., Type, Base Unit of Measure, Unit Cost, Gen. Prod. Posting Group                       | All tiers                                                                                            |

Business Central has no universal external-ID field. The canonical primary key is the No. on each card (Customer No., Vendor No., Item No., G/L Account No.), and the canonical match key on import is that same No. Configuration Packages match by primary key — re-running with the same No. updates the existing record rather than creating a duplicate. If source identifiers are non-numeric, remap to Business Central's No. Series and store the original in a Legacy No. field.

Custom-field options are constrained compared with a generic SaaS platform. Out of the box you can add up to 32 custom fields per card via the EOS Custom Defined Fields AppSource app with no developer involvement[13](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-13). For deeper extension you write AL extensions in Visual Studio Code that add fields directly to the underlying table — there is no on-platform field-builder UI for native development[10](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-10).

| Field type                      | Limit                                         | Notes                                                                                                                                                               |
| ------------------------------- | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Code (No. Series)               | 20 chars                                      | Used for primary keys on master and document tables                                                                                                                 |
| Text                            | Configurable, default 100 chars in extensions | Each variable-length text field accounts for 26 bytes in record overhead[14](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-14) |
| Decimal                         | 18 digits total, configurable scale           | Used for amounts; Amount Rounding Precision per currency                                                                                                            |
| Date / DateTime                 | DateTime stored as UTC; Date as work-date     | Posting Date drives GL period; Work Date is user-level                                                                                                              |
| Option (enum)                   | Hard-coded values via AL enum object          | ValuesAllowed property restricts subset per page                                                                                                                    |
| Boolean                         | Yes/No                                        | Imported as TRUE/FALSE in Configuration Packages                                                                                                                    |
| Custom fields via app (no-code) | 32 per card                                   | EOS Custom Defined Fields app; multilingual labels[13](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-13)                       |
| AL extension fields             | Subject to table-level field count cap        | Per Tenant Extensions deploy without AppSource[10](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-10)                           |

Relationships are modelled as TableRelation properties on each field — a Customer No. on a Sales Header points at the Customer table. There is no general-purpose junction object; many-to-many is modelled via explicit junction tables (Item Vendor, Default Dimension, Item Category) with composite primary keys.

**5 concurrent** Tenant concurrency cap Business Central caps concurrent operations at 5 concurrent and 95 queued per tenant. Exceed it and the platform returns a too-many-requests response. Sized parallelism past this number stalls the entire load.

Posting groups are the most consequential concept to internalise before mapping. Customer Posting Group points at the AR control account, Vendor Posting Group at the AP control account, Inventory Posting Group at the inventory and COGS accounts, and General Business + General Product Posting Groups jointly drive sales and purchase line GL via the General Posting Setup matrix[9](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-9). Get the posting groups wrong on master data and every document the customer touches posts to the wrong account.

## Pre-migration prep — the work before you touch Business Central

*What must be true on the source, the destination, and across the team before the first Configuration Package is imported.*

The single best predictor of a clean Business Central migration is how much work you do on the chart of accounts and master data before any package is uploaded. Practitioners consistently report that the most expensive mistakes are caught the day they try to post the first transaction and discover a missing posting group or an unmapped GL.

> Validate as you go. Don't wait until launch week to discover that inventory fields never made it across — that's how launch week becomes panic week.

Treat the source export as raw material that needs to be reshaped to Business Central's expected formats — GL account numbers conformed to a fresh chart, dates in a consistent format, currency codes in ISO-4217, customer and vendor records with payment terms and posting groups assigned before they ever cross the wire.

### Source-side prep

- Audit the chart of accounts in the source ERP and decide whether to lift-and-shift the numbering or restructure. A GP-to-BC move almost always requires restructure — the GP chart was likely built before dimensions existed and uses sub-accounts that should collapse into Business Central dimensions instead.
- Dedup customers, vendors and items in the source before export. A customer that appears twice in QuickBooks under slightly different names will land as two Customer No. records in Business Central with split ledger histories.
- Normalise units of measure — every Item must have a Base Unit of Measure, and alternate UoMs must declare a numeric conversion factor (e.g., Box of 12 = 12 × Each). Missing or zero conversion factors block the Item import[11](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-11).
- Resolve currency exchange rates — pull the full historical rate table from the source for every currency you transacted in, with the Starting Date on which each rate applied. Business Central uses the exchange rate effective on the document's Posting Date, not a single corporate rate[12](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-12).
- Decide on AP/AR open-invoice strategy — load as journal entries against control accounts (simpler, no document detail) or as posted documents (preserves invoice number and aging detail). The right call depends on how often Finance needs to look back at the source document, not on technical ease.

### Destination-side prep

- Create a sandbox environment from the Business Central administration center — sandboxes are full copies of production and can be created in unlimited number for trial runs[19](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-19). Use the sandbox to dry-run every Configuration Package before touching production.
- Build the chart of accounts in production with Account Type, Income/Balance, Direct Posting flag and Totaling ranges set. Header and Total accounts must be structured before any G/L Account can post.
- Configure posting groups upfront — Customer Posting Groups, Vendor Posting Groups, Inventory Posting Groups, General Business and General Product Posting Groups — with the matrix in General Posting Setup filled in before any sales or purchase document import runs[9](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-9).
- Set up fiscal year and accounting periods under Setup → Accounting Periods. Lock prior periods you do not intend to allow postings into during cutover.
- Provision users via Microsoft Entra ID (formerly Azure AD), assign Permission Sets and User Groups, and configure SSO before go-live. Permission Sets control table-level access; missing permissions during user testing surface as cryptic 'You do not have permission' errors at posting time.
- Create dimensions and default dimensions for every Customer, Vendor and G/L Account that needs analytics. Default Dimensions auto-populate journals and documents; without them, every line needs manual dimension entry.

### People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically a full weekend, longer for multi-entity — and communicate it to AP, AR, Sales and Finance. Train department leads on Role Centers, document approvals and posting flows in the sandbox before go-live. A typical Business Central implementation runs three to six months end-to-end; the data move is two to six weeks of that, the rest is process redesign and user readiness.

## Import mechanisms: Configuration Packages, Wizard, and programmatic loads

*Several paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall before posting.*

Business Central exposes several load paths and the right one depends on dataset size, table mix, and whether you need to re-run idempotently. Configuration Packages (part of RapidStart Services) cover most master-data and opening-balance migrations. The Data Migration Wizard handles guided one-shot loads from QuickBooks, GP and Excel. Programmatic loads handle large, repeatable transactional volumes.

### Configuration Packages (RapidStart Services)

The canonical path for any Business Central migration is Configuration Packages, accessed via Setup & Extensions → RapidStart Services → Configuration Packages. A package is a metadata bundle declaring which tables to load, which fields are in scope, validation rules, and processing order.

The workflow: define the package on the destination, export an empty Excel template seeded with the chosen columns, populate from source data, import back, run Apply Package to write into live tables. Apply runs field-level validation against TableRelation, Option enums and mandatory-field rules before any row commits — errors surface as rows with status `Invalid` that you fix and re-apply without re-loading clean rows. Configuration Packages handle master data, historical exchange rates, opening journal entries and document templates.

### Data Migration Wizard (Assisted Setup)

The Data Migration Wizard sits under Assisted Setup and offers guided ingestion from Dynamics GP, QuickBooks Desktop and Online, and plain Excel via Data Templates. For Dynamics GP, a dedicated Data Migration Extension connects to the on-prem GP database, pulls master data plus open transactions, and applies them via the same Configuration Package engine[21](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-21). The Wizard is the right call for a small business with a supported source and little transformation; the wrong call for custom legacy systems.

### Programmatic loads

Business Central exposes programmatic surfaces for the standard entities Customer, Vendor, Item, JournalLine, SalesInvoice and so on[22](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-22). Tenant authentication runs through Microsoft Entra ID. Custom Business Central extensions can expose additional entities for anything not in the standard set.

**5 / 95** Concurrent / queued operations per tenant Hit either ceiling and Business Central returns a too-many-requests response. Naive parallelism sized for typical SaaS limits stalls every transactional load.

The platform-wide ceiling is roughly 5 concurrent operations and 95 queued per tenant, with too-many-requests responses returned when either is exceeded[16](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-16). Choose the programmatic path when the load is over 100,000 records, when you need to push transactional documents (Sales Invoices, Purchase Invoices) at scale, or when the migration needs to be re-runnable and audit-logged from your side.

### Third-party staging tools

Fivetran, Workato, Tipalti and SmartConnect (eOne) all have certified Business Central connectors. The pattern is reverse-ETL: source lands in a warehouse, transforms in SQL or a low-code mapper, then flows in programmatically or via Configuration Packages. Insight Works's Import Export PowerTool is a Business Central-native app that runs imports up to 30 times faster than standard RapidStart. For one-time migrations the value is repeatability under failure; for ongoing syncs, they become the integration system of record.

Under 10,000 master records → Configuration Packages. GP, QuickBooks or pure Excel source → Data Migration Wizard. Over 100,000 records, any high-volume transactional load, or any re-runnable pipeline → programmatic loads.

## Mapping your data into Business Central

*The longest section — because the chart of accounts, posting groups, and opening-balance design decide whether month-one close works.*

Mapping is where every ERP migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether the trial balance ties on day two, whether inventory valuation reconciles on day five, and whether the AP team trusts vendor balances on day thirty.

Work table by table, top to bottom of the import order: G/L Account first (so every other table has somewhere to post), then Posting Groups and Dimensions, then Customer and Vendor, then Item, then Currency and Exchange Rate, then opening journal entries, then AP/AR open items, then historical transactions if in scope.

### Chart of accounts and posting groups

The Chart of Accounts is the foundation. Every G/L Account row needs No., Name, Account Type (Posting, Heading, Total, Begin-Total, End-Total), Income/Balance flag, and a Direct Posting yes/no that controls whether the account can be posted to from journals directly versus only via subledger postings.

| Source                    | Destination                                        | Note                                                                                                                                                            |
| ------------------------- | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| GL account number         | No. (Code, max 20 chars)                           | Restructure if collapsing legacy sub-accounts into Dimensions                                                                                                   |
| GL account name           | Name                                               | Used in lookups; keep consistent with statutory chart                                                                                                           |
| GL type / class           | Account Type + Income/Balance                      | Posting/Heading/Total drives the subtotal structure                                                                                                             |
| Direct-posting flag       | Direct Posting (Yes/No)                            | Set No on AR/AP/Inventory control accounts to force subledger flow                                                                                              |
| Sub-account or department | Dimension Value + Default Dimension                | Replace GP sub-accounts with BC Dimensions                                                                                                                      |
| Posting group mapping     | Customer/Vendor/Inventory/Bank Posting Group setup | Define before any subledger import — drives every transaction's GL hit[9](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-9) |

### GL opening balances

Opening balances enter Business Central through a General Journal with Posting Date set to the last day of the closing prior period and Document No. set to a consistent code (e.g., `OPENING-2026`). Every Debit line needs a balancing Credit line, posted against the Opening Balance Equity holding account (typically account 3990 or similar) so the journal balances[25](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-25).

Once you confirm the trial balance ties to the source, reclassify Opening Balance Equity into Retained Earnings via a separate journal. AP and AR control accounts are loaded zero in the opening journal — their balances arrive via the AP/AR open-invoice load, which posts directly to the control accounts through the subledger.

### Inventory items, BOM and units of measure

Item master data is the most field-rich table in Business Central. Required at minimum: No., Description, Base Unit of Measure, Inventory Posting Group, General Product Posting Group, Costing Method (FIFO, LIFO, Average, Specific, Standard), and optionally Item Category Code and Item Tracking Code for lot/serial numbers.

| Source                           | Destination                                             | Note                                                                                                                                                      |
| -------------------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SKU / Item code                  | No.                                                     | Code field — max 20 chars; respect No. Series if used                                                                                                     |
| Description                      | Description + Description 2                             | 100 chars each — multilingual via Item Translations table                                                                                                 |
| Stock UoM                        | Base Unit of Measure                                    | Foundation for all conversions — cannot be changed once posted[11](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-11) |
| Pack size / case quantity        | Item Unit of Measure (alternate)                        | Conversion factor must be >0; one alternate per pack size                                                                                                 |
| Cost / standard cost             | Unit Cost + Standard Cost                               | Set Costing Method first — changing it later requires inventory revaluation                                                                               |
| Inventory account / COGS account | Inventory Posting Group + General Product Posting Group | Drives Item Ledger Entry → GL postings[9](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-9)                           |
| BOM / recipe                     | Production BOM (Premium) or Assembly BOM (Essentials)   | Header + Lines table; load after Items exist                                                                                                              |
| Vendor item code                 | Item Vendor Catalog                                     | Junction table; supports per-vendor cost and lead time                                                                                                    |

Opening inventory quantities are loaded via the Item Journal with Entry Type Positive Adjmt., which creates Item Ledger Entries and posts inventory value to GL via the Inventory Posting Setup. Lot or serial-tracked items must include tracking lines in the journal or Business Central rejects the row at posting.

### Multi-currency and historical exchange rates

Every additional currency must be defined on the Currency card with code, description, the rounding precisions for amounts and unit amounts, and the GL accounts used for posting realised/unrealised gains and losses[12](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-12). The Currency Exchange Rates table stores the rate history — every row carries Starting Date, Exchange Rate Amount and Relational Exchange Rate Amount, and Business Central uses the rate effective on the document's Posting Date.

For migrations, load the full historical exchange-rate table from the source covering every currency-date combination touched by any open document. If you only load today's rates and then post historical AP/AR with prior posting dates, Business Central converts at today's rate and your statutory reporting breaks immediately.

### Fiscal periods and AP/AR open invoices

Set up the fiscal year and Accounting Periods before importing transactional data. Allow Posting From / Allow Posting To dates on User Setup and General Ledger Setup gate the active window. Recommended pattern: leave the prior year open during the parallel-run window, post late adjustments via General Journal, reconcile, then close the prior year and lock posting forward.

Open invoices migrate two ways. The journal-entry approach posts each as a General Journal line with Account Type \*Customer\*/\*Vendor\*, original Document No., Posting Date, Due Date and Amount — fast, ages correctly, applies cleanly against cash receipts. The document approach creates full Posted Sales/Purchase Invoices with header and line detail — more work, but preserves the invoice document for audit and reprinting.

| Source                 | Destination                                              | Note                                                              |
| ---------------------- | -------------------------------------------------------- | ----------------------------------------------------------------- |
| Customer ID            | Customer No.                                             | Must already exist in the Customer table                          |
| Invoice number         | Document No. on journal line or Posted Sales Invoice No. | Preserve verbatim for audit traceability                          |
| Invoice date           | Posting Date + Document Date                             | Use original dates; period must be open for posting               |
| Due date               | Due Date                                                 | Or derive from Payment Terms Code on Customer                     |
| Open amount + currency | Amount + Currency Code                                   | Historical exchange rate must be loaded for original Posting Date |
| Salesperson / rep      | Salesperson Code (Customer + document level)             | Load Salesperson/Purchaser table first                            |

### Customer, Vendor, payment terms and Dimensions

Customer and Vendor cards are required-field heavy. Beyond Name and Address, the load must include Customer/Vendor Posting Group, Gen. Bus. Posting Group, VAT Bus. Posting Group, Payment Terms Code (e.g., `30D`, `NET60`), and Currency Code if non-local. Pre-create every payment term referenced in the source before importing master data, or rows with unknown Payment Terms Code values are rejected.

Dimensions replace the legacy GL sub-account model — typical dimensions are Department, Project, Customer Group, Salesperson, Location. Define each under Setup → Dimensions, then assign Default Dimensions at Customer, Vendor, Item or G/L Account level. The Value Posting rule (No Code / Same Code / Code Mandatory) enforces dimension capture at posting; use Code Mandatory on revenue-tracking dimensions to prevent unanalysed transactions.

### Historical transactions, files and audit trail

Business Central does not have a generic 'import historical transaction' path that preserves Entry No. integers — Entry No. on every ledger entry is system-assigned at posting. The two patterns are: (1) load each historical document as a posted invoice via the document approach, which gets a new Entry No. but preserves Document No., Posting Date and amounts; or (2) keep the source ERP read-only as an archive for pre-cutover lookups.

Document attachments (PDFs, scanned invoices, contracts) attach to records via the Document Attachments FactBox. As of the 2026 wave 1 release, Business Central supports external file storage for attachments via SharePoint, Azure Blob Storage and other providers, which keeps the database under capacity caps and lets you move large attachment estates without bloating the tenant[26](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-26). Configure External Storage Setup before bulk-loading attachments.

System fields — `SystemCreatedAt`, `SystemCreatedBy`, `SystemModifiedAt`, `SystemModifiedBy` — are Microsoft-managed and stamped on every write. They cannot be overridden during a Configuration Package apply[27](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-27). If audit trail matters, add `Legacy Created Date` and `Legacy Created By` as extension fields and populate from the source export. The on-platform Change Log captures field-level changes from when it is enabled — turn it on after the migration so cutover writes do not flood the log[28](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-28).

## The pitfalls that derail Business Central migrations

*Ten specific failure modes — ranked by impact, each tied to the exact Business Central mechanism that breaks.*

**high Posting groups missing or mis-mapped on master data**

Every Customer needs a Customer Posting Group, every Vendor a Vendor Posting Group, every Item an Inventory Posting Group and General Product Posting Group, and the General Posting Setup matrix must contain a row for every Gen. Bus. × Gen. Prod. combination you will actually use. Miss one and the document fails at posting with `There is no General Posting Setup within the filter` — the most common Business Central go-live error. Build a posting-group coverage spreadsheet before importing master data[9](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-9).

**high Chart of accounts lift-and-shifted instead of restructured**

Teams migrating from Dynamics GP often try to recreate their GP chart verbatim, complete with sub-accounts. Business Central handles segmentation via Dimensions, not sub-accounts — keeping the legacy structure means every department × project combination becomes a separate GL account and the chart bloats from 200 lines to 2,000. Restructure the chart during migration: collapse sub-accounts into Dimensions and let the Default Dimension framework do the analytics.

**high Tenant throttling stalls transactional loads**

Business Central caps tenant throughput at roughly 5 concurrent operations and 95 queued, returning a too-many-requests response once either ceiling is hit. Teams sizing parallelism off the more generous limits found in other SaaS platforms see their migration loops stall on the first big batch of Sales Invoices. Drop concurrency to 4, implement exponential backoff on retry headers, and split very large loads across multiple scheduled windows[16](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-16).

**high Historical exchange rates not loaded before AP/AR**

Business Central converts foreign-currency documents using the Currency Exchange Rate effective on the Posting Date. If you load only today's rates and then post an open AR invoice dated three months ago, the system converts at today's rate and the original transaction's local-currency amount is wrong from day one. Load the full historical rate table from the source — every Starting Date and Exchange Rate Amount touched by any open document — before any AP/AR posting[12](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-12).

**high Configuration Package text fields silently truncated**

Variable-length Text fields in Business Central carry a fixed default size (often 100 characters via the no-code custom-field app, configurable in AL extensions) and each text field consumes 26 bytes of record overhead[14](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-14). Source data with longer product names or descriptions gets truncated on apply with no error if the truncation is silent in the AL flow — a problem widely reported in the broader Dynamics family for products with names over 100 characters[29](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-29). Audit field lengths against the source on every text column before applying the package.

**medium System fields cannot be overridden during import**

`SystemCreatedAt`, `SystemCreatedBy`, `SystemModifiedAt` and `SystemModifiedBy` are stamped automatically on every record write and ignored if you pass them in a Configuration Package. Teams discover this when they pull Customer Ledger Entries for audit and see every entry created on cutover day. The fix is to add Legacy Created Date / Legacy Created By extension fields and populate from the source export — and rewrite any historical-period reports to filter on those fields, not on system fields[27](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-27).

**medium Tenant storage cap and attachment bloat**

Business Central provisions 80 GB of database storage plus a per-licensed-user allowance, shared across all environments in the tenant[4](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-4). Inline-loading attachments at scale (hundreds of GB of scanned invoices) consumes that capacity fast and triggers Microsoft restrictions on creating new environments. The 2026 wave 1 release added external storage support for attachments — point at SharePoint or Azure Blob Storage and the binary lives outside the BC database[26](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-26). Configure it before bulk-loading.

**medium On-premises NAV/BC users do not migrate to cloud**

When you run the cloud migration from on-premises Business Central or NAV to Business Central online, user accounts and permissions on the source do not transfer. Every user must be re-provisioned in Microsoft Entra ID with the right Business Central license and Permission Set on the destination, before they can log in to the migrated environment[30](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-30). Sequence user provisioning early in the cutover plan or the team cannot validate the data on day one.

**medium Data residency locked at environment creation**

Business Central data residency is determined by the environment localization selected when you create the environment, which pins the data to a specific Azure Geo. Public-sector and EU customers with sovereignty requirements who create the environment in the wrong region cannot flip it post-creation without Microsoft-run migration assistance[31](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-31). Confirm the target Azure Geo with Legal before the production environment is provisioned.

**low GP end-of-life pressure compresses migration scope**

Microsoft ended new Dynamics GP subscription sales on April 1, 2026, with full support ending December 31, 2029 and security updates ending April 30, 2031. Teams who delay the move past 2028 face a compressed timeline where they cannot afford process redesign and end up lift-and-shifting GP's structure verbatim — which is exactly the pitfall called out above. Start the migration project with at least 12 months of runway before your hard support cutoff.

## Validation and cutover

*What to verify after each Configuration Package applies, in what order — and how to fail safely when something is wrong.*

Validation is the bridge between the import jobs completing and Finance being allowed to close month-one. The most reliable signal is having department leads — AP, AR, Inventory, GL — run their week-one work in the sandbox and sign off that the numbers tie. Build a reconciliation spreadsheet comparing source and destination on each of these counts; anything outside a $0.01 GL variance or a 0% record-count variance gets investigated before users get login access.

- Trial balance per account — run G/L Account Balances report in Business Central as of the opening-balance date and tie line-by-line to the source ERP trial balance. Any variance traces to either a missing journal line or a GL account that landed with the wrong sign.
- AR aging by customer and aging bucket — run Customer - Top List and Aged Accounts Receivable reports and compare to source aging. Variances usually trace to missing or mis-dated open invoices.
- AP aging by vendor and aging bucket — run Aged Accounts Payable report and reconcile to source. Apply the same logic as AR.
- Inventory valuation per item and per location — run Inventory Valuation report and tie to source inventory subledger. Variance per item points at a missing Item Journal positive adjustment or a wrong Costing Method.
- Customer and Vendor counts vs source — count distinct No. on each table; any duplicates indicate the dedup transform missed cases.
- Item count plus BOM coverage — count distinct Item No. plus count Production BOM Header rows; gaps in BOMs mean assembly orders will fail at release.
- Currency exchange-rate row count per currency — every starting-date row from the source should be present on Currency Exchange Rates; missing rows mean historical revaluation breaks.
- Posting Group coverage matrix — confirm General Posting Setup has a row for every Gen. Bus. × Gen. Prod. combination actually used on imported documents.

On top of reconciliation, run a manual spot-check: pick 20 customers, 20 vendors and 20 items and verify each card against the source UI. Pick the five largest open invoices on each side (AR and AP) and trace the full document — header, lines, dimensions, posting groups. If discrepancies show in three or more of 20, halt cutover, fix root cause, re-apply affected Configuration Package rows.

Change Log must be enabled from cutover day forward — Setup → Change Log Setup, enable per table for every table you want field-level history on. It captures user, timestamp, table, field, old value and new value and is the canonical audit source going forward[28](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-28). India-localised tenants must enable the equivalent Audit Trail functionality for statutory compliance[32](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central#source-32).

There is no native bulk-undo for posted transactions — posting is one-directional, and reversal is via posting an opposite entry, not by deleting the original. For Configuration Package applies that have not yet hit transactional tables, the package can be re-applied with corrected data because primary-key match updates the existing record. For everything posted, stamp every imported row with a deliberate Document No. prefix (e.g., `MIG-`) and post offsetting reversal journals filtered on that prefix if catastrophe strikes.

Cutover sequencing: (1) source ERP goes read-only Friday evening; (2) final delta export captures everything changed during the test-import window; (3) delta applied via Configuration Package on Saturday; (4) reconciliation runs Sunday; (5) Monday users get access with the migration lead on call for two weeks of hyper-care; (6) source decommission scheduled 90 to 180 days out, never the same month.

## Migration partners and tools

*Microsoft Solution Partners, ISVs, iPaaS vendors — what each is good for and how to choose.*

The Microsoft Solution Partner program designates partners by specialisation (Business Applications) and competency level (Solutions Partner, plus the legacy Gold/Silver designations). For Business Central migrations specifically, partners with a stated Dynamics GP-to-BC or NAV-to-BC practice tend to ship cleaner than generalist Microsoft partners.

RSM, Armanino, Western Computer, Synoptek, Itransition, Liberty Grove, Sabre Limited and Enavate are commonly named in the Business Central migration corner of the market, each offering fixed-scope packages and Microsoft-aligned methodologies. eOne Solutions ships SmartConnect and Popdock as BC-native migration tooling, strong on NAV-to-BC and GP-to-BC data movement. Insight Works's Import Export PowerTool is a free app that runs imports up to 30x faster than RapidStart for large master-data loads.

On the ETL and iPaaS side, Fivetran, Workato, Hopp Tech, Tipalti and Apideck all have Business Central connectors. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that conforms posting groups and dimensions, and the ongoing-sync layer that takes over once the one-time migration is complete. Hopp Dynamics specifically targets Dynamics 365 data migrations with a tracking portal and pre-built business-object templates.

Managed-migration cost ranges vary widely. Per market-published guidance, a clean QuickBooks-to-BC move with under 1,000 customers and no manufacturing typically lands $35,000 to $60,000 inclusive of license setup and basic training. A Dynamics GP-to-BC project with multi-entity, manufacturing BOMs, three years of historical AR/AP and Power BI rebuild typically runs $60,000 to $150,000+, with the upper end driven by entity count, custom AL extension scope, manufacturing depth, and the number of integrations that need rebuilding rather than re-pointed.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Business Central migrations and handles the chart-of-accounts mapping, posting-group setup, Configuration Package authoring, opening-balance journal design, historical-exchange-rate loading and reconciliation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on record count, entity count and source platform, with separate line items for manufacturing BOMs, multi-currency depth and AL extension scope so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Microsoft Solution Partner with full implementation scope, an iPaaS-first approach for ongoing-sync needs, a Business Central ISV like eOne for migration-specific tooling, or a specialist migration vendor. \[Explore FlitStack →]\(/contact)

In this guide

## Business Central migration checklist

An exhaustive eight-phase task list for moving finance, inventory, and operational data into a Dynamics 365 Business Central tenant. Typical timeline: 8–24 weeks.

0\. Decide & Plan 10 tasks

- **Document the in-scope objects: Chart of Accounts, Customers, Vendors, Items, Bank Accounts, Fixed Assets, open AR, open AP, open Sales Orders, open Purchase Orders, and any modules in use (Manufacturing, Jobs, Service).** Decide which Business Central tables receive data and which legacy modules will not be carried over. Write this list down before any other work.*If skipped: Scope creep mid-project forces re-do of the configuration package mapping after sandbox tests have already started.*
- **Decide the historical-data cutoff: how many closed fiscal years of GL detail and how many years of posted documents to bring across.** Most teams load only opening balances and the current open year of detail. Anything older stays in the source as a read-only archive.*If skipped: Loading several years of historical entries multiplies storage cost against the 80 GB plus per-user database allowance and slows every report.*
- **Choose the Business Central license tier (Essentials vs. Premium) based on modules in scope.** Premium is required if Manufacturing or Service Management is in scope. The decision affects user-license cost from day one.*If skipped: Re-tiering after go-live forces a re-quote and may block users from modules they were trained on.*
- **Decide the multi-company structure: one tenant per legal entity vs. multiple Companies inside a single tenant.** Business Central uses a Tenant → Environment → Company hierarchy. Inter-company posting is configurable but only inside a tenant.*If skipped: Picking the wrong topology forces a re-implementation when consolidation reporting fails to roll up across entities.*
- **Confirm Azure geography for the production environment to satisfy data-residency rules.** Environment localization at creation time pins the database to a specific Azure geo and cannot be changed later without re-provisioning.*If skipped: GDPR or sector data-residency findings post-go-live force a re-migration into a new environment in the correct geo.*
- **Identify SOC 2, HIPAA, India audit-trail, or industry retention requirements that affect logging, Change Log, and retention policies.** Business Central supports retention policies that auto-purge tracked log tables; the rules must be set before users start posting.*If skipped: Retention defaults silently delete log data that a later audit needs.*
- **Set the target cutover window with a hard freeze date on the source ledger.** Pick a date close to month-end and avoid year-end. The window must cover final reconciliation, cloud-migration replication, and validation.
- **Name a single accountable owner (DRI) for the migration and identify the Finance, Operations, IT, and Microsoft Entra admin counterparts.** Business Central depends on Entra ID for user identity. The Entra admin is needed before any user account can be created.
- **Write the success criteria as falsifiable statements (e.g., trial balance matches the source to the cent, all open AR invoices reconcile by customer, item on-hand quantities match by location).** *If skipped: Without explicit numeric exit criteria the project never formally closes and resources keep getting pulled back for rework.*
- **Document explicitly out-of-scope items: legacy custom reports, third-party add-on data, posted email attachments, deleted-record audit history.** Tell users which decisions were made so expectations match what go-live delivers.

1\. Pre-Migration Prep 25 tasks

- **Run a duplicate-detection pass on the source Customer master keyed on Name plus Tax/VAT Registration No.** Resolve duplicates before export. Business Central enforces unique Customer No. on import and will reject duplicates at load.*If skipped: Duplicate customers create double AR balances and confuse statement runs.*
- **Run the same dedup pass on the Vendor master keyed on Name plus Tax/VAT Registration No.** *If skipped: Duplicate vendors fragment AP aging and cause double payment.*
- **Run a dedup pass on the Item master keyed on Item No. and Description.** Pay particular attention to legacy SKUs that were re-coded mid-life; pick the surviving No. before export.
- **Normalize phone numbers to E.164 and email casing to lowercase on Customer and Vendor records.** Excel TRIM, LOWER, and SUBSTITUTE formulas handle this without a separate tool.
- **Standardize country and state codes against the ISO 3166 list that Business Central expects in the Countries/Regions table.** *If skipped: Non-ISO codes silently drop on import and addresses come in with blank country, breaking tax determination.*
- **Resolve all source records with missing required fields: Customer Posting Group, Gen. Bus. Posting Group, VAT Bus. Posting Group, Payment Terms Code, Currency Code.** These are the fields Business Central refuses to insert a Customer or Vendor without, even via Configuration Package.*If skipped: Records with missing posting groups stop the entire batch import and force a transform re-run.*
- **Re-encode any non-UTF-8 source text (Windows-1252, ISO-8859-1) to UTF-8.** Business Central file handling defaults to UTF-8; mismatched encoding mangles accented characters and currency symbols.*If skipped: Garbled vendor names and addresses look fine in the export file but render as question marks after import.*
- **Export current baseline record counts from the source for every object in scope.** Save the counts in a spreadsheet — they become the reconciliation target in Phase 6.
- **Run a source-side trial balance, AR aging, AP aging, and inventory valuation report as of the planned cutover date.** Lock these PDFs in a shared drive. They are the authoritative reconciliation source.*If skipped: Without a frozen reference run, post-migration variances cannot be traced to a known starting point.*
- **Inventory all custom fields, custom modules, and add-ons in the source and decide for each: rebuild, drop, or hold for later.** *If skipped: Custom data discovered mid-cutover triggers a re-import.*
- **Provision a Business Central production environment and a separate sandbox environment in the chosen Azure geography.** Sandbox is mandatory for test loads. Both count against the tenant environment cap visible in the Business Central administration center.*If skipped: Loading test data into production cannot be cleanly undone without restoring an environment backup.*
- **Create the production Company (and any additional companies for multi-entity scope) using the Assisted Setup or admin center.** Set Company Name, Address, Country/Region, Local Currency (LCY), and Tax Registration No. before any data lands.
- **Configure General Ledger Setup: LCY Code, Local Address Format, Inv. Rounding Precision, Allow Posting From/To dates.** Allow Posting From/To gates which dates can be posted to. Set this generously during cutover and lock it down afterward.*If skipped: A too-tight Allow Posting From/To window blocks the opening journal at the worst moment.*
- **Configure Accounting Periods with the fiscal year start date and period lengths.** Open the new fiscal year. Closed-period gating depends on this table.
- **Provision user accounts in Microsoft Entra ID and assign Business Central license types (Essentials, Premium, Team Member, Device).** User identities flow from Entra. License type controls which Permission Sets the user can hold.
- **Create Permission Sets and assign them via User Groups for the using-team roles (Finance, AP, AR, Inventory, Purchasing, Sales).** *If skipped: Users without the right Permission Set cannot open the pages they need on day one, causing a flood of help-desk tickets.*
- **Create the Chart of Accounts structure (Account No., Name, Account Type, Account Category, Income/Balance, Account Subcategory) in the destination, leaving balances at zero.** Use a Configuration Package to load the COA structure first; balances come later via General Journal.
- **Create General Posting Setup, VAT Posting Setup, Customer Posting Groups, Vendor Posting Groups, Inventory Posting Setup, and Bank Account Posting Groups.** These four-way intersections route ledger entries to GL accounts. The Configuration Package for master data depends on them existing first.*If skipped: Missing one row in General Posting Setup throws a posting error on the very first sales or purchase document.*
- **Define Dimensions (e.g., Department, Project, Region) and Dimension Values used for financial analytics, plus default dimensions on Customers, Vendors, Items, and GL Accounts.** Dimensions in Business Central replace separate analytical ledgers and are easiest to set up before transactions land.*If skipped: Adding a Mandatory Dimension after data is loaded forces a back-fill on every historical entry.*
- **Create Currencies in the Currencies table and seed the Currency Exchange Rates table with historical dates that cover the open-document period.** Each posted multi-currency transaction needs a rate that existed on its document date.*If skipped: Missing historical rates block import of open foreign-currency invoices until rates are back-filled.*
- **Create Locations, Bins, and Warehouse setup if Warehouse Management is in scope.** Item Ledger entries require a Location Code on every quantity posting.
- **Pause or disable production integrations, job queues, and AppSource extensions that should not fire during data load (bank feeds, EDI, email notifications).** Re-enable them only after Phase 5 finishes.*If skipped: An active bank feed during load can double-post incoming bank transactions or notify customers with placeholder data.*
- **Announce the source-system freeze date and time to every team that posts transactions.** Include the channels that will be used for cutover communication (Teams channel, status page).
- **Schedule role-based Business Central training (Finance close, AP entry, sales-order entry, item receipt) for the week before go-live.** *If skipped: Untrained users avoid the new system on day one and continue working in shadow spreadsheets, fragmenting data.*
- **Designate first-responder owners by module for the first 48 hours post-cutover.** Publish a single Teams channel for triage and an escalation chain.

2\. Source Export 17 tasks

- **Export the full source Chart of Accounts including Account No., Name, Type, Income/Balance flag, parent account, and totaling string.** Save as CSV with a UTF-8 BOM. Capture the export timestamp in the filename.
- **Export the source GL trial balance as of the planned cutover date by Account and Dimension.** *If skipped: Without a dimension-level trial balance you cannot rebuild the opening journal with the right analytical splits.*
- **Export the Customer master with all standard fields plus any custom attributes flagged in scope.** Include Tax Registration No., Payment Terms, Currency Code, default Salesperson, default Dimensions.
- **Export the Vendor master with all standard fields plus custom attributes in scope.** Include Tax/VAT Registration No., Payment Terms, Payment Method, Currency Code, default Dimensions.
- **Export the Item master with Description, Base Unit of Measure, Item Category, Inventory Posting Group, Gen. Prod. Posting Group, VAT Prod. Posting Group, Costing Method.** *If skipped: Missing Costing Method on import forces a default that may not match the source valuation.*
- **Export Item Units of Measure and conversion factors against the base UoM for every item that uses alternate units.** Box, case, pallet conversions must travel with the item or quantity math breaks on purchase and sales documents.
- **Export Bills of Materials (BOM) and routing data if Manufacturing is in scope.**
- **Export open Sales Orders, open Purchase Orders, open Sales Invoices, open Purchase Invoices, and open Credit Memos as of the freeze date.** Document the exact freeze timestamp in the filename of each export.*If skipped: Mixing a half-frozen source with a half-loaded destination creates phantom orders.*
- **Export open AR Customer Ledger Entries by document, including Document No., Document Date, Due Date, Original Amount, Remaining Amount, Currency.** *If skipped: Open AR loaded as a single net balance per customer destroys aging and remittance allocation.*
- **Export open AP Vendor Ledger Entries by document with the same fields as AR open items.**
- **Export on-hand inventory by Item, Location, and Lot/Serial if applicable, with quantity and standard or actual cost.**
- **Export Fixed Assets with acquisition date, original cost, accumulated depreciation as of cutover, depreciation book, useful life, and remaining life.**
- **Export Bank Accounts with the last reconciled balance and the list of unreconciled transactions.** *If skipped: Without the unreconciled list the first bank rec in Business Central reports a phantom variance.*
- **Export historical Currency Exchange Rates covering at least the open-document period.** Daily rates if the source used them; otherwise the rate that was actually applied to each open foreign-currency document.
- **Export the user list with roles and reporting structure for re-creation in Entra and Business Central Permission Sets.**
- **Export attachments and associated document metadata (which file belongs to which Document No., Customer, Vendor, or Item).** Capture the binary files plus a manifest CSV that maps each filename to its parent record key.
- **Screenshot or export configuration of source reports, dashboards, automations, and workflows.** These do not migrate. They will be rebuilt in Business Central, Power BI, or Power Automate in Phase 7.

3\. Transform & Map 28 tasks

- **Build a master mapping workbook with one tab per Business Central table (Customer, Vendor, Item, G/L Account, etc.).** For each destination field record: source field, transform rule, nullability, required flag, and whether it is part of the Configuration Package.
- **Confirm the upsert key per object: No. for masters; Document Type plus Document No. plus Line No. for documents; Entry No. for ledger entries.** Business Central enforces these as primary keys. Re-runs depend on stable keys.*If skipped: Re-running an import without a stable upsert key creates duplicate masters that then need manual merge.*
- **Resolve picklist and option-field value mismatches between source and destination (Payment Terms Code, Payment Method Code, Shipment Method Code, Posting Group codes).**
- **Decide handling for source fields with no destination equivalent: drop, concatenate into Description 2, or model as a new field via an AL extension.** Configuration Package fields cannot be customized; a new field requires a Per Tenant Extension built in Visual Studio Code with the AL Language extension.
- **Assign every Customer and Vendor a Customer Posting Group, Gen. Bus. Posting Group, and VAT Bus. Posting Group value at the row level.** *If skipped: Skipping this and relying on a default at import time silently routes entries to the wrong GL accounts.*
- **Assign every Item an Inventory Posting Group, Gen. Prod. Posting Group, and VAT Prod. Posting Group value at the row level.**
- **Convert date and datetime fields to ISO-8601 with explicit UTC offsets where the source stored local time.** Business Central writes datetime to the database in UTC. Source local dates without an offset can shift by a day on import.*If skipped: Off-by-one-day dates on posted documents distort aging and period attribution.*
- **Normalize decimal separators and currency amounts to the format the Configuration Package expects (period as decimal, no thousands separator).**
- **Truncate or split source strings that exceed Business Central field limits.** Standard text fields are 50 or 100 characters; variable-length text adds 26 bytes per field to the record overhead.*If skipped: String-too-long errors halt the entire batch and force a re-export with truncation rules applied.*
- **Escape commas, double-quotes, and embedded newlines in CSV exports per RFC 4180 so the Configuration Package parser does not split a row.** *If skipped: A single un-escaped comma in an address splits the row and shifts every column to the right for the rest of the file.*
- **Re-encode all CSV files as UTF-8 if any non-ASCII characters appear.**
- **Validate that every foreign key in the file (Posting Group codes, Country/Region Code, Currency Code, Payment Terms Code) exists in the destination setup tables.**
- **Decide and document the timestamp strategy for posted documents: re-stamp Posting Date to the cutover date, or preserve the original Document Date and Posting Date.** For open items it is normal to preserve original Document Date for aging and re-stamp Posting Date for compliance with the Allow Posting From window.*If skipped: Re-stamping every document to today destroys aging buckets and historical analytics.*
- **Decide the record-ownership strategy for migrated rows: assign to the named user that owned them in the source, or to a single “Data Migration” service user.** User Code is captured on every posted entry. Once posted, it cannot be edited from the UI.
- **Decide the Change Log strategy during the migration: leave Change Log disabled during load to avoid log bloat, then enable it for production tables before go-live.** *If skipped: Leaving Change Log on during bulk load creates millions of log rows that compete with transactions for database storage.*
- **Decide the attachment strategy: load binaries directly into the Document Attachments table, or store externally and link.** Storing externally keeps the database within the 80 GB plus per-user allowance; inline storage is simpler but costs database space.
- **Build the destination Chart of Accounts mapping with Posting Group setup wired in.** For every source GL account decide the destination Account No., Account Category, Account Subcategory, and any default Gen. Posting Type / Bus. Posting Group / Prod. Posting Group that drives automatic posting.*If skipped: A misnumbered or mis-categorized account distorts every financial statement until it is renumbered, which is painful once entries exist.*
- **Prepare the GL opening-balance General Journal lines with offset against an Opening Balance Equity account.** One line per account per dimension combination. Debits and credits must net to zero against Opening Balance Equity. Backdate the Posting Date to the day before go-live and confirm Allow Posting From is open.*If skipped: Posting the journal with an out-of-balance net forces a manual correcting entry that audit will question.*
- **Prepare an Item Journal (positive adjustment) to load on-hand inventory by Item, Location, and Lot/Serial.** Set the Unit Cost on each line to match source valuation. The Item Ledger entries created here become the opening cost basis.*If skipped: Loading items with zero cost or default cost destroys subsequent margin reporting and COGS posting.*
- **Set up alternate Units of Measure on items and verify the Qty. per Unit of Measure conversion factor matches source.**
- **Load Item Bills of Materials (Production BOM and Assembly BOM) if Manufacturing or Assembly is in scope.**
- **Populate the Currency Exchange Rates table with a row per currency per historical date that any open foreign-currency document references.** Use the exact rate that was applied to each open document, not the spot rate of cutover day.*If skipped: A single missing exchange-rate row blocks import of the open document and cascades into open-AR reconciliation failure.*
- **Build the open-AR load file as Sales Invoice / Credit Memo documents (or General Journal lines that hit Customer Posting Group accounts), preserving original Document No., Document Date, Due Date, and Currency.** Loading open AR as a net balance per customer is faster but breaks remittance matching; loading by document preserves aging.*If skipped: A net-balance load forces manual application of every incoming payment after go-live and destroys customer statement detail.*
- **Build the open-AP load file the same way against Vendor Posting Group accounts.**
- **Configure Accounting Periods and set Allow Posting From / Allow Posting To both at General Ledger Setup and on User Setup to gate which dates can be posted to.** *If skipped: Forgetting to open the User Setup window blocks the migration user even when General Ledger Setup is open.*
- **Pre-populate default Dimension Values on Customer, Vendor, Item, and GL Account masters so transactions inherit the right analytical splits.**
- **Build the Configuration Package: select tables in execution order (setup tables first, masters next, opening journals last), import the package definition, then fill it with the transformed data.** Configuration Packages run validation per row and surface errors before any commit, which is the canonical bulk-load path.
- **Validate the Configuration Package in the sandbox by running Apply Package on a 1–5% sample first.**

4\. Sandbox Test Migration 13 tasks

- **Refresh the sandbox environment from a recent production backup so it matches the production setup tables.** Use the Business Central administration center to copy the production environment into the sandbox slot.
- **Load a 1–5% representative sample of each object via Configuration Package into the sandbox.** Pick rows that include the trickiest data: long names, accented characters, multi-currency documents, lot-tracked items.
- **Spot-check 10 random Customer, Vendor, and Item records field-by-field against the source.** *If skipped: Field-level drift caught after full load forces a destructive re-import.*
- **Test that mandatory fields enforced by AL extensions (e.g., Customer Posting Group on Customer) reject blank rows.** Configuration Package validation surfaces these as row-level errors with a specific field name.
- **Test datetime handling: load a record with a timezone-sensitive datetime and verify the value displayed in Business Central matches the source.**
- **Test special-character handling on names, addresses, and item descriptions.**
- **Load the opening General Journal in sandbox and verify it posts with debits = credits and produces a trial balance that matches the frozen source TB.** *If skipped: A sandbox trial balance that does not tie forces a transform fix before any production load.*
- **Load the Item Journal positive adjustments in sandbox and verify Item Ledger entries are created with correct cost and Location.**
- **Load open AR and open AP samples in sandbox and verify aging buckets match the source aging report.**
- **Run a full-volume timing test if sandbox capacity allows, to extrapolate cutover-window duration.** Business Central throttles concurrent and queued operations at the tenant level; bulk loads must pace themselves below those ceilings.*If skipped: Hitting tenant throttling mid-cutover forces the load to back off and extends the window past business hours.*
- **Test attachment upload to the Document Attachments table for a sample of records.**
- **Have a Finance, Inventory, and AP user spot-check sandbox data using their normal day-to-day workflows.** *If skipped: Issues that only surface in real workflows (statement runs, payment proposals, inventory picks) stay hidden until go-live.*
- **Capture sandbox load times and error counts in a written test report and have the migration sponsor sign off before Phase 5.** *If skipped: Skipping written sign-off means later disputes about whether the sandbox passed at all.*

5\. Production Cutover 14 tasks

- **Confirm the source freeze: verify no posting activity in the source for the last hour.**
- **Take the final delta export of source data covering everything that changed since the Phase 2 baseline.**
- **Verify production Allow Posting From / Allow Posting To windows are open for the opening-journal date.** Check both General Ledger Setup and the User Setup for the migration user.
- **Disable production job queues, AppSource integrations, and notification flows that might fire during the load.** *If skipped: An active recurring job queue can post against partially loaded master data and create orphan ledger entries.*
- **Apply Configuration Packages in dependency order: setup tables (Posting Groups, Currencies, Exchange Rates, Locations, Dimensions, Payment Terms) first.**
- **Apply master-data Configuration Packages next: Chart of Accounts, Customers, Vendors, Items, Item Units of Measure, Bank Accounts, Fixed Assets.**
- **Post the GL opening-balance General Journal with Opening Balance Equity as the offset.** Confirm the trial balance immediately after posting and match it to the frozen source TB before continuing.*If skipped: Continuing past an out-of-balance opening journal compounds the variance into every downstream report.*
- **Post the Item Journal positive adjustments to seed inventory on hand by Item and Location.**
- **Load open AR documents (or the open-AR journal) and verify customer balances roll up to the AR control account on the GL.**
- **Load open AP documents (or the open-AP journal) and verify vendor balances roll up to the AP control account on the GL.**
- **Load open Sales Orders and open Purchase Orders.**
- **Capture every Configuration Package status, row count, and error count from the Config. Package Card.** *If skipped: Without recorded row counts you cannot prove reconciliation later.*
- **Re-tighten Allow Posting From / Allow Posting To windows to lock historical periods.**
- **Re-enable job queues, integrations, and notification flows.**

6\. Validate 22 tasks

- **Run the Business Central Trial Balance report and reconcile to the frozen source trial balance, account by account.** *If skipped: Any unexplained variance carried into go-live will be questioned by audit.*
- **Reconcile Customer Statement totals to the source AR aging by aging bucket and by customer.**
- **Reconcile Vendor Statement totals to the source AP aging by aging bucket and by vendor.**
- **Reconcile Inventory Valuation report to the source inventory valuation by Item, Location, and total.** *If skipped: Inventory variance after cutover usually traces to a unit-cost or UoM conversion error and is expensive to unwind.*
- **Cross-check 25–50 randomly selected records across Customer, Vendor, Item, and GL Account field-by-field against the source.**
- **Compare record counts per object: source baseline vs. Business Central destination. Investigate any delta.**
- **Verify default Dimensions on Customers, Vendors, Items, and GL Accounts came across and flow onto new test documents.**
- **Verify Item Units of Measure conversions produce the right quantity on a test sales order and a test purchase order.**
- **Verify Bills of Materials roll up to the expected parent items.**
- **Verify Document Attachments are accessible from their parent records (Customer Card, Vendor Card, Item Card, posted documents).**
- **Verify Customer–Salesperson, Vendor–Purchaser, and Item–Vendor relationships round-trip from the source.**
- **Enable Change Log on the tables required by audit policy (Customer, Vendor, Item, G/L Account, Posting Setup tables).** Change Log was kept off during load to avoid log bloat; turn it on now.
- **Verify retention policies on log tables align with the retention period agreed in Phase 0.**
- **Confirm the production environment’s Azure geography matches the data-residency decision documented in Phase 0.** *If skipped: A wrong-geo deployment may force a re-migration to comply with GDPR or sector rules.*
- **Run the Audit Trail report and confirm timestamps and user codes on posted entries match the migration strategy chosen in Phase 3.**
- **Have Finance close a test period in the sandbox copy of the post-migration database and confirm no posting blocks.**
- **Have AR run a customer statement and confirm aging matches the reconciliation.**
- **Have AP run a Payment Journal proposal and confirm the right vendors and amounts surface.**
- **Have Inventory pick an item and confirm on-hand by Location matches the count.**
- **Have Sales create a test order through to posting and confirm GL postings hit the expected accounts.**
- **Document every issue surfaced by UAT in a tracked list and triage to fix-before-go-live vs. fix-after-go-live.**
- **Get written go-live sign-off from the migration sponsor and Finance lead before opening Business Central to end users.** *If skipped: Opening up without written sign-off leaves the migration team owning every downstream issue indefinitely.*

7\. Post-Migration Cleanup 12 tasks

- **Communicate go-live to all end users with login URL, MFA setup steps, and a single support channel.**
- **Run role-based training refreshers in the first week using the migrated production data as the example dataset.**
- **Set the source system to read-only and announce the read-only date.** Read-only mode kills the temptation to dual-post.
- **Rebuild source reports and dashboards in Business Central report layouts, Excel, or Power BI.** Reports do not migrate. Recreate the top 10 most-used reports first; backlog the rest.
- **Rebuild source workflows, approvals, and notifications using Business Central Approval Workflows and Power Automate.**
- **Re-establish integrations to Outlook, Teams, Power BI, bank feeds, EDI, payroll, and any other downstream systems.**
- **Connect AppSource extensions that were paused during cutover and verify each one runs against the new data.**
- **Monitor integration throughput against tenant-level throttling for the first two weeks and tune any integration that approaches the cap.** *If skipped: An integration hitting the throttle in production silently fails to deliver bank feed, EDI, or webshop data.*
- **Schedule a 30-day post-migration retrospective with the migration team and key users.**
- **Decide and document the source-system decommission date.** A common interval is 90 days after cutover, after the final retention window passes.
- **Archive all source-system exports, frozen reference reports, Configuration Packages, and load logs to long-term storage.** *If skipped: Throwing away the export files before audit closes their books on the migration year forces a forensic recovery later.*
- **Close the migration project formally with a final status report, lessons-learned doc, and project closure.**

Questions, answered

## Migrating to Business Central: questions

How long does a Business Central migration take?

A small-business migration from QuickBooks or Xero with under 1,000 customers and no manufacturing runs eight to twelve weeks end-to-end. A mid-market project with Dynamics GP source, multi-entity, manufacturing BOMs and historical AR/AP runs four to six months including discovery, sandbox dry-runs, parallel-run, training and a two-week hyper-care window.

Can I migrate from Dynamics GP to Business Central?

Yes — Microsoft ships a Data Migration Extension that connects to the on-premises GP database and pulls master data plus open transactions via Configuration Packages. Plan to restructure the chart of accounts rather than lift-and-shift, because GP sub-accounts should collapse into Business Central Dimensions for clean analytics.

Can I migrate from QuickBooks to Business Central?

Yes — the Data Migration Wizard under Assisted Setup has a QuickBooks Desktop and Online source connector that pulls Customer, Vendor, Item and open balances. Custom fields, classes and items with stock require manual mapping. Plan posting groups before the wizard runs or every transaction posts to the wrong account.

Does Business Central preserve original posting dates?

Partially. Posting Date on journals and documents is user-controlled and can be backdated to historical periods provided the period is open under Accounting Periods and User Setup. But system fields like SystemCreatedAt and SystemModifiedAt are stamped on every write and ignored on import — use Legacy Created Date extension fields.

What's the difference between Configuration Packages and programmatic loads for Business Central?

Configuration Packages are the canonical Excel-based path under RapidStart Services with field-level validation and idempotent re-apply on primary key — best for master data and opening balances under 100,000 records. Programmatic loads handle transactional volumes at scale but share the tenant's five-concurrent-operation ceiling.

Can I add custom fields to Business Central without a developer?

Yes, up to 32 custom fields per card via the EOS Custom Defined Fields AppSource app — no AL coding needed, with multilingual labels. Beyond that limit, custom fields require AL extensions developed in Visual Studio Code with the AL Language extension and deployed as Per Tenant Extensions or via AppSource.

What happens to open invoices and AP/AR balances during migration?

Open invoices migrate either as General Journal lines posted against Customer or Vendor with original Document No. and dates (simpler) or as full Posted Sales/Purchase Invoices with line detail (audit-friendly). Both create Customer or Vendor Ledger Entries that age correctly. Pre-load historical exchange rates first for any foreign-currency open documents.

Is there an undo or rollback for Business Central imports?

Configuration Packages can be re-applied with corrected data because primary-key match updates existing records — that handles master-data fixes. There is no bulk-undo for posted transactions; reversal is via posting opposite entries. Stamp every migration journal with a deliberate Document No. prefix so you can filter and post offsetting reversals if needed.

## Sources

1. [Microsoft Dynamics 365 Business Central — Wikipedia](https://en.wikipedia.org/wiki/Microsoft_Dynamics_365_Business_Central)
2. [Managing Capacity — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-capacity)
3. [Business Central on-premises to online migration — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-business-central-on-premises)
4. [Make Fields Mandatory in Configuration Package — Dynamics Community](https://community.dynamics.com/forums/thread/details?threadid=f3c4a0c6-3469-f011-bec2-7c1e521722dc)
5. [AL development environment — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-al-development-environment)
6. [Set up item units of measure — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/inventory-how-setup-units-of-measure)
7. [Update currency exchange rates — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-update-currencies)
8. [Custom Defined Fields by EOS Solutions — Microsoft AppSource](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.eos_solutions%7CAID.ex067customdefinedfields%7CPAPPID.5d2c2370-931f-423b-bfb5-2128499f89ff)
9. [Object Specifications and Limitations — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-object-specifications-limitations)
10. [Tenant throughput limits for Business Central cloud — Dynamics Community](https://community.dynamics.com/forums/thread/details?threadid=11d54801-6b2c-4006-a41f-695602956448)
11. [Business Central administration center — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center)
12. [Migrate Dynamics GP data to the cloud — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-dynamics-gp)
13. [Web services overview — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/web-services)
14. [How to load General Ledger Beginning Balance for Dynamics 365 Business Central](https://www.youtube.com/watch?v=oVCBen7qoBI)
15. [Store document attachments in external file storage — Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/across-store-document-attachments-externally)
16. [Business Central 'Last Modified Date Time' vs 'Modified At' — Dynamics Community](https://community.dynamics.com/forums/thread/details/?threadid=09788ae6-8443-4d80-b961-1e9fe19bd70b)
17. [Auditing changes (Change Log) — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/across-log-changes)
18. [Importing Products Failed — Truncating Error — Dynamics Community](https://community.dynamics.com/forums/thread/details/?threadid=b28e5ee2-a154-4b84-8901-b66887b4b9fe)
19. [Complete cloud migration — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migration-finish)
20. [Data sovereignty in Dynamics 365 Business Central — Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-sovereign-clouds/public/sovereign-controls-d365-business-central)
21. [Audit trail and edit logs for accounting software in India — Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/localfunctionality/india/india-audit-trail-edit-logs-accounting-software)

Get a quote

## Moving to Business Central?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Business Central setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
