---
title: "Encompass Production Cloud to Business Central Migration"
description: "Migrate Encompass Production Cloud to Business Central with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/erp/encompass-production-cloud/to/microsoft-dynamics-365-business-central"
---

# Encompass Production Cloud to Business Central migration

We migrate batch production records, Bills of Materials, Inventory lots with genealogy chains, production variances, QC records, open sales orders, and purchase orders from Encompass Production Cloud into Microsoft Dynamics 365. Because Encompass Production Cloud has no documented public REST API, we extract from in-app reports and reconstruct lot traceability relationships that standard exports do not surface, then load into Dynamics 365 Finance and Operations or Business Central via the destination API with all parent-record lookups resolved before any child record is written.

Short answer

FlitStack AI migrates production order or production orders, bom and bom version or bom and production boms, job card or production order route or production order routing lines, items and item tracking code / lot number relation or lot trackings from Encompass Production Cloud to Business Central, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 5-7 weeks.

![](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 what moves →](https://flitstack.ai/migrations/erp/encompass-production-cloud/to/microsoft-dynamics-365-business-central#what-moves)

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

Source Encompass Production Cloud ![](https://flitstack.ai/platforms-trim/encompass-production-cloud.webp)

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

Production Order or Production Order BOM and BOM Version or BOM and Production BOM Job Card or Production Order Route or Production Order Routing Line Item Item Tracking Code / Lot Number relation or Lot Tracking

Mapped field by field · sample run · one-click rollback

## What moves from Encompass Production Cloud to Business Central?

Moving from Encompass Production Cloud to Microsoft Dynamics 365 is a beverage-production ERP migration with a specific constraint: Encompass Production Cloud does not publish a public bulk-export API, so data extraction relies on in-app report generation with post-export relational reconstruction.

Read the full summary

We extract Batches, BOMs, Production Schedules, Inventory Lots, Production Variances, QC records, Sales Orders, and Purchase Orders from structured in-app exports, manually reconstruct the lot genealogy chains that Batch Backtrace stores as linked records, and load into Dynamics 365 Finance and Operations or Business Central via the destination platform's OData v4 API or Data Management Framework. BOM versioning, lot dimension configuration, and TTB traceability documentation require explicit customer decisions during scoping. We do not migrate workflows, production scheduling automations, or reporting configurations; these are documented and handed off for the customer's Dynamics 365 admin to rebuild.

1:1

### Batch → Production Order (Finance & Operations) or Production Order (Business Central)

Encompass Batch records map to Dynamics 365 Production Order headers.

How it maps

Each Batch links to a BOM version, a production schedule, ingredient lot assignments, and finished-goods inventory output. We extract batch records from in-app production reports (no public API available), resolve the BOM version reference and ingredient lot IDs at migration time, and create Production Orders with status set to Scheduled or Started depending on the customer's cutover window. Because Encompass has no bulk-export API, we validate the extraction completeness against inventory movement records and QC checkpoint records before committing to import scope.

1:1

### Bill of Materials (BOM) → BOM and BOM Version (Finance & Operations) or BOM and Production BOM (Business Central)

Encompass BOMs define recipe formulations with ingredient quantities, unit-of-measure conversions, and cost allocations.

How it maps

Multiple active BOM versions in Encompass represent reformulations, seasonal substitutions, or TTB-mandated changes. We extract all BOM versions and present a versioning strategy decision to the customer during scoping: migrate the current active version only, or include historical recipe variants for audit traceability. Dynamics 365 BOM tables store version and effective date ranges natively, so each Encompass BOM version becomes a separate Dynamics BOM Version record linked to the parent BOM.

1:1

### Production Schedule → Job Card or Production Order Route (Finance & Operations) or Production Order Routing Line (Business Central)

Production Schedules capture planned run quantities, start/end times, and assigned production resources.

How it maps

We map schedule lines to Dynamics Job Card or Route operations depending on the destination tier. The resource-linkage model differs between platforms: Encompass assigns production staff directly to a batch run, while Dynamics 365 assigns routes to Work Centres. We extract the resource assignments from Encompass schedules and map them to configured Work Centres during the production-line configuration phase.

1:1

### Inventory Lot → Item (with Lot Number dimension group enabled)

Encompass Inventory Lots track raw materials and finished goods with quantity, location, cost, and TTB-relevant attributes.

How it maps

Dynamics 365 requires explicit lot and serial number dimension groups to be configured in the Item master before lot-tracked inventory can be migrated. We include a pre-flight check to confirm that the customer's destination environment has lot tracking enabled for the relevant item categories (raw ingredients, packaging materials, finished goods). Lot genealogy chains must be reconstructed separately from the lot record migration.

configuration

### Lot Genealogy (Batch Backtrace) → Item Tracking Code / Lot Number relation (Finance & Operations) or Lot Tracking (Business Central)

Encompass Batch Backtrace stores lot genealogy chains (ingredient lot to finished-goods lot) as linked records rather than a flat table.

How it maps

Standard in-app exports do not include the full chain. We extract genealogy as a separate data extraction step, reconstruct the parent-child lot relationships, and write them into Dynamics 365 as Item Tracking entries. The genealogy chain must be complete and validated before production batch records are imported because Dynamics 365 validates that ingredient lot references exist at the time of production order confirmation.

1:1

### Production Variance → Production Journal or Production Order Report (Finance & Operations)

Encompass Production Variance records capture planned vs. actual consumption for each batch run: material usage, labour time, and yield discrepancies.

How it maps

We export variance records keyed to their parent Batch ID, map variance types to Dynamics 365 production journal line categories (Consumption, Output, Scrap), and write variance amounts to the appropriate cost ledger accounts. Variance records are imported after BOM and Batch records are confirmed complete because the variance amount calculation references the BOM cost structure.

******What moves 12 objects

Encompass Production Cloud Business Central

- Batch Production Order or Production Order 1:1
- Bill of Materials BOM and BOM Version or BOM and Production BOM 1:1
- Production Schedule Job Card or Production Order Route or Production Order Routing Line 1:1
- Inventory Lot Item 1:1
- Lot Genealogy Item Tracking Code transformed
- Production Variance Production Journal or Production Order Report 1:1

\+ 6 more in the mapping below

## How Encompass Production Cloud and Business Central differ

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

| Dimension                  | Encompass Production Cloud                                                                            | Business Central                                                                                                |
| -------------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Platform focus             | Purpose-built for craft beverage producers (beer, spirits, THC, NA)                                   | General ERP with optional production and supply chain modules (Business Central or Finance & Operations)        |
| Public API for data export | No documented public REST API or bulk-export endpoint; extraction relies on in-app reports            | Fully documented OData v4 API, Data Management Framework for Finance & Operations; API-first design throughout  |
| Beverage production model  | Native batch management, Batch Backtrace, production variances, and QC checkpoints for TTB compliance | Production Orders and Job Cards require configuration to match beverage-specific workflow; no native TTB module |
| Pricing model              | Per-user per month starting at $110, scaling with headcount including floor staff                     | Per-user per month from $70 (Business Central) to $430 (Finance & Operations tier); no per-floor-worker billing |
| Integration ecosystem      | Limited third-party integrations; immature API tooling for EDI and analytics                          | Over 3,500 AppSource apps; Azure integration, Power Platform connectors, and mature EDI frameworks              |
| Lot traceability           | Batch Backtrace stores genealogy as linked records (ingredient lot to finished-goods lot)             | Lot tracking via dimension groups; genealogy chains require manual configuration and post-load validation       |
| BOM versioning             | Multiple active BOM versions tracked per recipe (seasonal reformulations, regulatory changes)         | BOM versions with effective date ranges supported; version selection strategy is a migration design decision    |

## What to watch for in a Encompass Production Cloud to Business Central migration

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

high

### No public API means extraction depends on in-app report completeness

Encompass Production Cloud does not publish a public REST API reference for bulk data export.

How we handle it

All extraction relies on in-app reports that the customer generates with appropriate role permissions. Standard in-app reports may not include lot genealogy chains, BOM version references, or QC corrective action fields. We assess the completeness of every in-app export during discovery and flag extraction gaps before committing to migration scope. If critical relational data is absent from the reports, we discuss whether it can be reconstructed from inventory movement records or whether the customer should engage Encompass professional services for a data extract before migration begins.

high

### Lot dimension group configuration required before inventory migration

Dynamics 365 requires lot and serial number dimension groups to be explicitly configured on the Item master before lot-tracked inventory can be imported.

How we handle it

If the destination environment does not have lot tracking enabled for raw ingredients, packaging materials, and finished goods, the migration will fail at the inventory load phase with a dimension group validation error. We include a pre-migration checklist step that confirms lot tracking configuration on all relevant item categories before any inventory data moves. If configuration is missing, we document the required steps and pause the inventory phase until it is resolved.

medium

### BOM versioning requires explicit customer strategy before import

Active BOMs in Encompass Production Cloud frequently have multiple versions representing reformulations, seasonal ingredient substitutions, or TTB-mandated changes.

How we handle it

Dynamics 365 BOM tables support version and effective date ranges natively, but the migration must decide which version(s) to import. Migrating all versions creates a complete audit trail but multiplies BOM record volume and may confuse users who only need the current formulation. Migrating only the active version loses historical recipe context for producers who need TTB traceability across reformulation dates. We present both options during scoping and require a documented decision before BOM import begins.

medium

### Lot genealogy chains require post-extraction manual reconstruction

Encompass Batch Backtrace stores genealogy as linked records (ingredient lots connected to production batch lots) rather than as a flat table with a single parent-child field.

How we handle it

Standard in-app exports include the batch record and the lot records independently but not the genealogy join table. We include genealogy reconstruction as a standard step in our Encompass migration workflow: we extract the backtrace linkage records, build the parent-child chain, and validate that the chain forms closed circles before confirming migration completeness. If the genealogy records are absent from the in-app export, we flag this gap and discuss manual extraction options with the customer before proceeding.

medium

### Chart of Accounts mapping is the most manual object in scope

The Encompass chart of accounts reflects a beverage-production cost structure with COGS accounts tied to BOM cost allocations and production variance postings.

How we handle it

Dynamics 365 uses a different account segment structure and posts production costs through the production journal rather than directly to COGS accounts. We require a customer-supplied mapping spreadsheet for all account numbers and cannot automate account mapping because the segment structures (department, division, natural account) differ by company. We sequence Chart of Accounts migration after BOM import so that inventory valuation accounts are confirmed before GL mapping is finalised.

## How the migration runs

1. ### Discovery and extraction assessment

   We conduct a structured discovery session covering the Encompass Production Cloud tier (Basic, Standard, Enterprise), production segments in use (beer, spirits, THC, NA), BOM versioning strategy, QC configuration, open order and PO volume, historical transaction depth, and the customer's target Dynamics 365 tier (Business Central Essentials, Premium, or Finance & Operations).

   What this step covers

   We assess the completeness of available in-app exports against our standard extraction checklist. If critical relational data (lot genealogy, BOM version references, QC corrective actions) is absent from standard reports, we document the gap and discuss options: manual extraction from Encompass, professional services engagement with Encompass, or accepting a reduced-scope migration with a written gap inventory.

2. ### Dynamics 365 pre-flight and schema configuration

   Before any data extraction begins, we confirm the destination Dynamics 365 environment has production, inventory, and finance modules configured with the appropriate dimension groups, number sequences, and posting profiles.

   What this step covers

   Specifically: lot tracking is enabled on relevant item categories, BOM version and date-range structures are configured, production journal types are set up, and the Chart of Accounts segment structure is defined. We document any missing configuration and work with the customer's Dynamics 365 admin to resolve gaps before migration data is written. This step prevents the most common class of post-import validation failures.

3. ### Data extraction, cleansing, and genealogy reconstruction

   We extract Batches, BOMs (all versions), Production Schedules, Inventory Lots, Production Variances, QC records, Sales Orders, Purchase Orders, Chart of Accounts entries, and Open AP/AR records from Encompass using in-app reports and any negotiated professional services exports.

   What this step covers

   Lot genealogy chains are extracted separately as linked records and reconstructed into parent-child lot relationships. We cleanse extracted data: de-duplicating lot records, resolving BOM version conflicts based on the customer's versioning strategy decision, validating date formats against Dynamics 365 posting date ranges, and confirming all vendor and customer IDs are present before AP/AR import.

4. ### Chart of Accounts and BOM mapping

   We map Encompass accounts to Dynamics 365 Chart of Accounts entries using the customer-supplied mapping spreadsheet, paying particular attention to COGS accounts tied to BOM cost allocations and production variance postings.

   What this step covers

   BOM records (with all selected versions) are mapped to Dynamics 365 BOM and BOM Version records, with ingredient lines converted to BOM Components referencing the migrated inventory item numbers. BOM and Account mapping must be validated before production order and inventory migration begins because production records reference both.

5. ### Sandbox migration and reconciliation

   We run a full migration into a Dynamics 365 Sandbox (Full Copy or Partial Copy) using production-equivalent data volumes.

   What this step covers

   The customer's operations lead reconciles record counts (Batches in, BOM versions in, Inventory Lots in, Sales Orders in, Purchase Orders in), spot-checks 25-50 batch records against the Encompass source for lot number accuracy and genealogy chain completeness, and reviews the Chart of Accounts mapping against the source trial balance. Any mapping corrections, BOM version decisions, or genealogy gaps are resolved before production migration begins.

6. ### Production migration in dependency order

   We run production migration in record-dependency order: Chart of Accounts (validated against trial balance), BOM and BOM Versions (with version strategy applied), Inventory Items with lot dimension configuration confirmed, Inventory Lots (with genealogy chain validated), Production Orders (Batches with BOM and lot references resolved), Production Variances, QC Records, Vendors and Customers (before AP/AR), Purchase Orders, Sales Orders, Open AP/AR ledger entries, and Historical Transactions (prior and current fiscal year only by default).

   What this step covers

   Each phase emits a row-count reconciliation report and a sampling validation before the next phase begins. We flag any BOM lot references that resolve to lots not yet imported and hold those production orders until the lot is available.

7. ### Cutover, validation, and inventory handoff

   We freeze Encompass writes during cutover, run a final delta migration of any records created or modified during the migration window, then enable Dynamics 365 as the system of record.

   What this step covers

   We validate production order cost postings against the source batch variance records to confirm COGS reconciliation. We deliver a written inventory of production scheduling automations, QC order configurations, and any reporting settings that require rebuilding in Dynamics 365. We support a one-week hypercare window for reconciliation issues raised by the customer's operations or finance team. We do not rebuild Encompass production workflows as Power Automate flows or configure TTB compliance documentation as part of the migration scope; these are documented for the customer's Dynamics 365 admin to address as a post-migration configuration task.

![](https://flitstack.ai/platforms/encompass-production-cloud.png) Encompass Production Cloud ![](https://flitstack.ai/platforms/microsoft-dynamics-365-business-central.svg) Business Central

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Business Central Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**5-7 weeks** Typical, smaller accounts

**10-16 weeks** Large or heavily customised accounts

A quote scales with record volume, BOM versioning scope, genealogy reconstruction complexity, and the number of distinct production segments (beer, spirits, THC, NA) to route. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Encompass Production Cloud to Business Central →](https://flitstack.ai/contact)

## Why teams move from Encompass Production Cloud to Business Central

- Encompass Production Cloud has no documented public REST API or bulk-export endpoint, forcing producers to rely on in-app report generation for data extraction. Growing producers building distributor EDI integrations, custom analytics pipelines, or third-party BI dashboards hit a ceiling where no self-service export mechanism exists without engaging professional services. Microsoft Dynamics 365 exposes a fully documented OData v4 API, Azure Data Factory connectors, and a Data Management Framework that supports automated recurring export jobs, removing the extraction bottleneck that Encompass imposes as operations scale.
- Encompass Production Cloud uses per-user pricing that scales with every named account, including brewing, packaging, and seasonal floor staff. Producers with large hourly workforces or seasonal headcount spikes find that licensing cost tracks labour rather than production volume. Microsoft Dynamics 365 Business Central and Finance & Operations use per-user tier pricing with named-user plans that can be scoped to finance and admin staff while production floor operations are covered through different access models, reducing total seat cost for teams where not every worker needs full ERP access.
- Enterprise producers, distributor networks, and investors increasingly require ERP platforms with audited SOC 2 Type II compliance, GDPR data residency options, and documented API governance as a condition of partnership and due diligence. Microsoft Dynamics 365 carries Microsoft's enterprise compliance certifications and data residency commitments across Azure regions. Producers preparing for equity financing or distributor EDI compliance find that Encompass Production Cloud's limited compliance documentation creates friction in procurement and onboarding processes that Dynamics 365 eliminates.
- The Microsoft ecosystem integration depth available with Dynamics 365—including Power BI for production analytics, Power Automate for workflow across supply chain and finance, Azure Synapse for data warehousing, and Teams for operational communication—represents a materially different analytics surface than what Encompass Production Cloud's built-in dashboards offer. Producers managing production data across multiple tools (Excel for financial reporting, third-party BI for sales) consolidate into a unified Microsoft data plane when they move to Dynamics 365, reducing the reconciliation work that disconnected tooling imposes on finance and operations teams.
- Mid-size and enterprise producers with complex distributor EDI requirements report that Encompass Production Cloud lacks mature EDI frameworks and that custom integration work requires professional services engagements that recur with every update. Microsoft Dynamics 365 offers pre-built EDI connectors through AppSource partners, Azure Logic Apps integration templates, and a mature partner ecosystem that handles distributor onboarding as a repeatable service rather than a custom project. Producers outgrowing ad-hoc integration tooling move to Dynamics 365 specifically to reduce the per-distributor integration cost that Encompass imposes at scale.

Questions, answered

## Encompass Production Cloud to Business Central migration questions

How long does an Encompass Production Cloud to Microsoft Dynamics 365 migration take?

Most migrations land between five and seven weeks for producers with under 2,000 batch records, 500 BOMs, a single production segment, and lot tracking already configured in the destination environment. Migrations with multi-segment production lines (beer and spirits simultaneously), full lot genealogy reconstruction across six or more ingredient tiers, historical transaction carry-forward (prior and current fiscal year), and TTB traceability documentation requirements move to ten to sixteen weeks because of the additional extraction, reconstruction, and validation work required before each data phase can proceed.

Does Encompass Production Cloud have a public API that FlitStack AI uses for extraction?

No. Encompass Production Cloud does not publish a public REST API reference or bulk-export endpoint. All data extraction relies on in-app report generation by the customer with appropriate role permissions. We assess the completeness of every in-app export during discovery and reconstruct relational data (lot genealogy, BOM version references) as a separate migration step. If critical data is absent from standard reports, we flag the gap before committing to scope and discuss manual extraction or professional services options with the customer.

Do production workflows, scheduling automations, and QC configurations migrate to Dynamics 365?

No. Encompass Production Cloud production scheduling workflows, QC checkpoint automations, and production routing rules are configuration-specific and do not have documented equivalents in Dynamics 365 Finance and Operations or Business Central. We do not migrate them as configured items. We deliver a written inventory of every active production scheduling workflow, QC order type, and routing configuration in Encompass with a description of the current behaviour and a recommended Dynamics 365 equivalent (Power Automate flows, Quality Order types, or Work Centre configurations). The customer's Dynamics 365 admin or a Microsoft partner rebuilds these as a post-migration configuration task.

Can FlitStack AI preserve TTB compliance traceability through the migration?

We migrate the data that supports TTB compliance: batch records with production dates, ingredient lot numbers with supplier information, finished-goods lot numbers, production variance records, and QC inspection results. We reconstruct lot genealogy chains from Batch Backtrace to provide the raw material traceability chain that TTB audits require. However, TTB compliance is a process and documentation requirement that extends beyond data migration. We do not produce TTB-format compliance documentation as part of the migration scope; we deliver the underlying data and genealogy chains in Dynamics 365 and document the lot traceability structure so that the customer's compliance team can generate TTB-required reports from the migrated data.

What happens to BOM versioning and seasonal reformulations during migration?

Encompass BOMs frequently have multiple active versions for seasonal reformulations, regulatory changes, or TTB-mandated updates. Dynamics 365 BOM tables support version and effective date ranges natively, so each Encompass BOM version can become a separate Dynamics BOM Version record. During scoping we present both options: migrate only the current active BOM version (simplest, lowest volume) or migrate all historical versions for complete reformulation traceability (higher volume, more audit value). The customer decides the strategy, and we apply it uniformly across all BOM records before import. Unresolved version conflicts can cause formulation mismatches in the first production order created in Dynamics 365.

Do open sales orders and purchase orders carry forward with their current statuses?

Yes, open Sales Orders and Purchase Orders migrate with their current status, line items, quantities, and pricing. Partially fulfilled orders carry their partial fulfilment status in Dynamics 365 with remaining quantities updated. We map Encompass distributor-specific fields (route codes, delivery windows) to Dynamics 365 extended fields or flag them as requiring post-migration manual entry because the field equivalents depend on the customer's Dynamics 365 configuration. Purchase Orders migrate after Vendors are confirmed complete to satisfy the vendor lookup. We do not migrate Encompass-specific EDI trading partner configuration; this requires a separate EDI onboarding engagement with the customer's distributor network.

What data does FlitStack AI NOT migrate from Encompass Production Cloud?

We do not migrate: production scheduling automations and workflow rules (delivered as a written inventory for rebuild in Power Automate), QC order configurations and inspection templates (written inventory for Dynamics 365 Quality Order setup), EDI trading partner configurations and distributor integration settings (separate EDI engagement required), custom reports and dashboards built in Encompass (replaced by Dynamics 365 Power BI or built-in report designer), or Encompass user accounts and role assignments (provisioned fresh in Dynamics 365 by the customer's admin). We also do not provide post-migration admin support, TTB compliance documentation generation, or production workflow rebuild as standard scope; these are separate engagements.

## Related migrations

[![](https://flitstack.ai/platforms-trim/microsoft-dynamics-365-business-central.webp) Migrate to **Business Central** Every source we move into Business Central, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central) [**Odoo ERP to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/odoo-erp/to/microsoft-dynamics-365-business-central) [**Sage Intacct to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/sage-intacct/to/microsoft-dynamics-365-business-central) [**NetSuite to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/microsoft-dynamics-365-business-central) [**ERPNext to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/erpnext/to/microsoft-dynamics-365-business-central)

## Sources: official documentation

1. [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)
2. [Update currency exchange rates — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-update-currencies)
3. [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)
4. [Object Specifications and Limitations — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-object-specifications-limitations)
5. [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)
6. [Complete cloud migration — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migration-finish)
7. [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)

Get a quote

## Moving from Encompass Production Cloud to Business Central?

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

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