---
title: "Business Central to Epicor Prophet 21 Migration"
description: "Migrate Business Central to Epicor Prophet 21 with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central/to/epicor-prophet-21"
---

# Business Central to Epicor Prophet 21 migration

We migrate Customers, Vendors, Items, open Sales and Purchase Orders, Inventory Ledger entries, Jobs, Employees, Bank Accounts, and Fixed Assets from Microsoft Dynamics 365 Business Central into Epicor ERP with schema alignment, BOM and routing map documentation, custom extension transfer, and a defined migration cutoff for historical transactions before any data moves.

Short answer

FlitStack AI migrates customers, vendors, parts, gl accounts and salesorders from Business Central to Epicor Prophet 21, 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: 8-12 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/microsoft-dynamics-365-business-central/to/epicor-prophet-21#what-moves)

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

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

Destination Epicor Prophet 21 ![](https://flitstack.ai/platforms-trim/epicor-prophet-21.webp)

Customer Vendor Part GL Account SalesOrder

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

## What moves from Business Central to Epicor Prophet 21?

Moving from Microsoft Dynamics 365 Business Central to Epicor ERP is a cross-vendor ERP migration that requires schema reconciliation between two structurally different platforms.

Read the full summary

Business Central organizes data around de-normalized data entities exposed via REST API v2.0 with named-user licensing; Epicor ERP uses a normalized table structure with native manufacturing depth (BOMs, routings, work centers, MES) available across more tiers. We extract master records, open documents, and scoped historical data from Business Central, transform the records to Epicor's schema and naming conventions, and load via Epicor's REST or IDO-based API with parent-record dependency resolution. We do not migrate Business Central workflows, approval rules, RapidStart packages, or AL extensions as code; we deliver a written inventory of these for the customer's Epicor administrator to rebuild. The migration cutoff for historical posted entries (G/L Entry, Item Ledger Entry, Value Entry) is negotiated during scoping to keep the cutover window manageable while preserving the audit trail the customer actually needs.

1:1

### Customer → Customer

Business Central Customer records map directly to Epicor Customer.

How it maps

We resolve t ShipToAddress and PayToContact structures into Epicor's Customer and CustShipTo tables, preserving payment terms, customer posting groups, and credit limits. Customer is imported before any Sales Order or AR invoice records so that parent references are satisfied at insert time. We flag any Customer records with inactive status in Business Central for the customer's Epicor admin to confirm before migration.

1:1

### Vendor → Vendor

Business Central Vendor master records map to Epicor Vendor.

How it maps

Vendor posting groups from Business Central translate to Epicor's Vendor purchasing group or terms code. Pay-to addresses and contact records map to Vendor and VendorContact. We resolve AP invoice and open PO records against the Vendor after master import completes, preserving any pre-cutoff open balances as carry-forward entries.

1:N split

### Item → Part

Business Central Items use three separate types (Inventory Item, Service, Non-Inventory Item) stored as distinct records in a single table with a Type field.

How it maps

Epicor Kinetic uses a single Part table with a PartType field (Stock, Non-Stock, Service, Expense). We transform the Business Central Item Type into Epicor PartType and map the related inventory posting group to Epicor's Commodity Code or Class. Stocking UOM, costing method, and lot/serial tracking flags carry forward as Part Plant and PartLot configuration rows. Items without inventory tracking (Service, Non-Inventory) map to PartType = Non-Stock or Service without plant-level stocking records.

mapping

### General Ledger Account → GL Account

Business Central Chart of Accounts records (with account categories, account type, and direct-posting flag) map to Epicor GL Account with the account number and name preserved.

How it maps

We resolve Business Central account categories to Epicor GL Account Categories or Segments depending on the customer's Epicor chart configuration. Pre-migration, we confirm whether the destination Epicor chart uses a flat or segmented account structure, as Business Central account numbering schemes often use prefixes that map differently to segmented charts.

1:1

### Sales Order → SalesOrder

Open Sales Orders from Business Central (document status not equal to Invoiced, Cancelled, or Shipped) migrate to Epicor SalesOrderHed and SalesOrderDtl.

How it maps

We preserve OrderDate, RequestDate, the customer and contact references, and all line quantities, unit prices, and discount amounts. Line-level Item numbers are resolved to Epicor PartNum after the Part master import completes. Backorder quantities and partial-shipment flags carry forward. Lines referencing Items that do not yet exist in Epicor are held in a reconciliation queue.

1:1

### Purchase Order → POHeader / PODetail

Open Purchase Orders from Business Central migrate to Epicor POHeader and PODetail.

How it maps

Expected receipt dates, quantities, and vendor references carry forward. Business Central prepayment percentages on PO lines map to Epicor prepayment fields if the destination is configured for prepayment tracking; otherwise they are documented as notes for the customer's AP team. Open PO lines referencing unmapped Vendors are held until Vendor master reconciliation completes.

******What moves 13 objects

Business Central Epicor Prophet 21

- Customer Customer 1:1
- Vendor Vendor 1:1
- Item Part split
- General Ledger Account GL Account transformed
- Sales Order SalesOrder 1:1
- Purchase Order POHeader 1:1

\+ 7 more in the mapping below

## How Business Central and Epicor Prophet 21 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                         | Business Central                                                                      | Epicor Prophet 21                                                                                                      |
| --------------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Deployment model                  | Cloud-only SaaS; no on-premises option                                                | Cloud (Epicor Kinetic), on-premise, and hybrid deployment available                                                    |
| Manufacturing depth               | Production Orders, routings, and work centers on Premium tier only ($100/user/mo)     | BOM, routing, work center, and MES capabilities available across multiple tiers without a pricing cliff                |
| License model                     | Named-user per month, no concurrent model; $70 Essentials / $100 Premium per user     | Named-user and concurrent options; per-user pricing from $125/mo on Kinetic; larger deployments negotiate volume tiers |
| Manufacturing implementation cost | Reviews cite $100K-$240K implementation costs for small-to-mid manufacturers          | Implementation costs competitive for manufacturers; top10erp.org shows $4K-$500K range with per-user at $125/mo        |
| Manufacturing retention           | 91% customer retention per top10erp.org comparison data                               | 97% customer retention per top10erp.org comparison data for Epicor Kinetic                                             |
| API architecture                  | REST API v2.0 with data entity abstraction layer; undocumented per-tenant rate limits | REST API and IDO (Iterative Data Object) interface with published rate limits per Epicor Kinetic API documentation     |
| Data residency                    | SaaS-only; Azure-hosted with limited data residency configurability                   | On-premise option provides full data residency control for regulated industries                                        |

## What to watch for in a Business Central to Epicor Prophet 21 migration

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

high

### Business Central data entity schema does not map directly to Epicor's normalized table structure

Business Central exposes de-normalized data entities (CustomerEntity, VendorEntity, ItemEntity) via its REST API that abstract away the underlying normalized SQL tables.

How we handle it

Epicor Kinetic uses a normalized table structure with separate header, detail, extension, and link tables. A field present in a Business Central data entity may reference a different table in Epicor (e.g., Business Central's Ship-to Address is embedded in CustomerEntity while Epicor stores it in a separate CustShipTo table with a foreign key). We build a table-level field map during discovery that resolves each Business Central entity field to its Epicor table and column before any ETL work begins. Migrations that skip this schema reconciliation step produce orphaned records, broken foreign keys, and data that appears correct at import but fails referential integrity checks during Epicor's validation routines.

high

### Manufacturing BOM and routing data requires manual mapping and separate Epicor import

Business Central Premium stores production bill of materials and routing data in separate tables (ProductionBOM, ProductionOrderRoutingLine) that do not have a direct equivalent in Epicor's Part, BOM, and PartOpr tables with a one-to-one field correspondence.

How we handle it

Epicor Kinetic's BOM structure uses ParentPartNum, Revision, and MtlPartNum links, while routings use PartOpr with WorkCenterSeq references. We document the BOM and routing transformation rules during scoping and provide a written map with the migration package. The customer or an Epicor manufacturing consultant executes the BOM and routing import using Epicor's data load tools after the master data migration validates. Business Central Production Orders with status (Released, Finished, Firmed) migrate as Epicor JobHead and JobMtl records with their current production stage preserved.

medium

### Custom AL extension fields do not automatically transfer to Epicor User Defined fields

Business Central allows custom fields via AL language extensions stored in separate extension tables (e.g., table extension ID prefixed to the base table).

How we handle it

Epicor Kinetic does not have a direct equivalent to AL extensions; custom data requirements are handled through User Defined (UD) fields on standard tables or through custom UD tables. We identify all active AL extension fields during the discovery phase, map each to its target Epicor UD field with correct data type (character, integer, decimal, date), and import custom field data in a second pass after the base entity migration validates. Any custom field that overlaps with a standard Business Central field is flagged to prevent duplicate or conflicting data on import. The customer's Epicor administrator validates UD field labels and validation rules post-migration.

medium

### Historical posted transaction volumes can stall the cutover window

Business Central's G/L Entry, Item Ledger Entry, and Value Entry tables grow indefinitely and can contain millions of rows in active manufacturing or distribution environments.

How we handle it

Epicor Kinetic's migration import tools process records sequentially with referential integrity checks that slow under large batch sizes. We negotiate a migration cutoff with the customer during scoping, typically 12-24 months of posted history, and carry forward account and inventory balances as Epicor opening balance entries for pre-cutoff periods. Historical detail beyond the cutoff is archived outside Epicor for compliance and audit access. Migrations that attempt full historical replay without a cutoff definition routinely extend the cutover window by 2-4 weeks and increase the risk of API timeout errors during the extraction phase.

low

### Business Central workflows and approval rules are not portable between tenants or vendors

Business Central approval workflows are environment-specific, tied to user accounts, delegate settings, and response limits configured within the tenant.

How we handle it

Epicor Kinetic uses a different workflow engine (Epicor Functions, BPM, and Method Directives) with different trigger models and action types. We do not migrate workflows as code. We deliver a written inventory of every active Business Central approval workflow and Power Automate flow with its trigger conditions, approver chain, and action sequence. The customer's Epicor administrator or an Epicor consultant uses this inventory to rebuild equivalent workflow logic in Epicor Kinetic post-migration. RapidStart configuration packages (used for master data template setup in Business Central) similarly do not migrate; they are documented for reference only.

## How the migration runs

1. ### Discovery and migration scope definition

   We audit the source Business Central tenant across version, licensed tier (Essentials/Premium), active user count, company structure (single or multi-entity), custom AL extensions, active workflows, and integration points.

   What this step covers

   We extract record counts across all master and transactional tables to size the migration. We confirm the Epicor Kinetic deployment (cloud or on-premise), active modules (manufacturing, distribution, project), and chart of accounts structure. The discovery output is a written migration scope document covering object priority, migration cutoff for historical transactions, custom field inventory, BOM and routing presence, and a timeline estimate.

2. ### Schema design and table-level field map

   We build a detailed field map between Business Central data entities and Epicor Kinetic tables.

   What this step covers

   This includes resolving the de-normalized entity fields to their normalized Epicor table counterparts (e.g., CustomerEntity ship-to fields to CustShipTo), mapping Business Central account categories to Epicor GL Account segments, and designing the BOM and routing transformation rules. We coordinate with the customer's Epicor administrator to confirm the chart of accounts structure, part number format, and warehouse/location codes before any data extraction begins. The field map is reviewed and signed off before extraction.

3. ### Data extraction from Business Central

   We extract data from Business Central using the REST API v2.0 with OAuth 2.0 authentication.

   What this step covers

   We implement request throttling with exponential backoff and batch chunking to stay within observed rate limits (Microsoft does not publish fixed limits). We pull master records (Customers, Vendors, Items, Employees, Bank Accounts, GL Accounts, Fixed Assets) in full, then transactional records (open Sales Orders, open Purchase Orders, scoped Item Ledger Entries, scoped G/L Entries) up to the agreed cutoff date. We extract custom extension field values in a separate pass after base entity extraction validates. All extractions emit row-count and checksum reports for reconciliation against Epicor import results.

4. ### Data transformation and Epicor Kinetic staging

   We transform the extracted Business Central records to match Epicor Kinetic's schema, data types, and validation requirements.

   What this step covers

   This includes splitting Business Central Item types into Epicor PartType values, resolving Business Central posting groups to Epicor account segments, formatting part numbers and customer numbers to the customer's Epicor conventions, and applying date and currency formatting per the Epicor locale configuration. We run a transformation dry-run against a subset of records and validate against Epicor's validation rules before full load. Any record that fails Epicor validation is logged to a reconciliation queue with the specific field and rule violation for the customer to resolve or suppress.

5. ### Epicor Kinetic production load and reconciliation

   We load master data into Epicor Kinetic first (GL Accounts, Customers, Vendors, Parts, Employees, Bank Accounts, Fixed Assets), then transactional records in dependency order (open Sales Orders, open Purchase Orders, scoped Item Ledger Entries, Job/Project records, scoped G/L opening balances).

   What this step covers

   Each phase emits a row-count reconciliation report comparing Business Central source record count against Epicor inserted record count. We flag any discrepancy above 0.5% for investigation before proceeding to the next phase. BOM and routing data is delivered as a documented import package rather than loaded directly, as these require Epicor manufacturing consultant review for accuracy. Custom extension fields are loaded in a second pass after base entity validation.

6. ### Cutover, validation, and handoff documentation

   We freeze writes to Business Central during the cutover window, run a final delta migration of any records modified during the window, then hand off Epicor Kinetic as the system of record.

   What this step covers

   We deliver the workflow inventory document, the BOM and routing transformation map, and the post-migration data archive location for pre-cutoff historical records. We support a one-week hypercare window for reconciliation issues. We do not rebuild Business Central workflows, Power Automate flows, or RapidStart packages in Epicor Kinetic; those are delivered as written inventories for the customer's Epicor administrator or manufacturing consultant to rebuild as separate engagement scope.

![](https://flitstack.ai/platforms/microsoft-dynamics-365-business-central.svg) Business Central ![](https://flitstack.ai/platforms/epicor-prophet-21.svg) Epicor Prophet 21

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 · Epicor Prophet 21 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

**8-12 weeks** Typical, smaller accounts

**12-18 weeks** Large or heavily customised accounts

A quote scales with record volumes, BOM and routing complexity, custom extension scope, and historical transaction cutoff depth. Epicor subscription cost (typically negotiated per deployment and user count) sits outside the migration fee and is the customer's recurring cost. Business Central licensing savings post-migration can offset a portion of Epicor's subscription for manufacturers that were on the Premium tier. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Business Central to Epicor Prophet 21 →](https://flitstack.ai/contact)

## Why teams move from Business Central to Epicor Prophet 21

- Small and mid-size manufacturers report Business Central implementation costs of $100K-$240K, pricing out businesses that need manufacturing capabilities. Reddit users on r/manufacturing cite $240K implementation quotes for Business Central Premium as the reason they short-listed Epicor, Acumatica, and Katana instead. Epicor Kinetic targets the same SMB-to-mid-market manufacturing segment with a more accessible implementation cost structure and per-user pricing that does not impose a Premium-tier pricing cliff for Production Orders, routings, and work centers.
- Business Central's manufacturing module (Production Orders, routings, work centers) is gated behind the Premium tier at $100 per user per month. Manufacturers with 20 or more users on Essentials who need production capabilities must upgrade every seat to Premium. Epicor Kinetic includes BOM, routing, work center, and MES capabilities across its manufacturing tiers without a pricing cliff that forces blanket Premium licensing, reducing total cost for manufacturing-focused organizations that need these features at scale.
- Epicor Kinetic shows a 97% customer retention rate versus Business Central's 91% on head-to-head comparison data from top10erp.org. COSMO CONSULT explicitly names Epicor ERP as a direct competitor and alternative to Business Central on their public comparison page, indicating that Epicor targets the same mid-market segment with a different manufacturing-first positioning. Higher retention rates suggest stronger long-term fit for the manufacturing and distribution workflows that outgrow Business Central's Essentials tier.
- Microsoft raised Business Central pricing for the first time since 2019 starting October 2024, with a second adjustment in October 2025. Organizations already concerned about total cost of ownership following reviews citing steep learning curves, difficult customization, and partner-dependency for AL extensions now face a recurring cost increase with no new features attached. Epicor offers a negotiated subscription model where larger deployments can lock in multi-year pricing and avoid the annual-percentage increases applied to Business Central renewals.
- Business Central is SaaS-only, with no on-premises or private-cloud option. Organizations in regulated industries (defense, pharmaceutical, food and beverage) with strict data residency requirements, offline production floor requirements, or legacy network architectures cannot accommodate a pure-cloud ERP without significant network investment. Epicor offers cloud, on-premise, and hybrid deployments, making it viable for organizations that cannot or will not move fully to Microsoft's Azure-hosted SaaS model.

Questions, answered

## Business Central to Epicor Prophet 21 migration questions

How long does a Business Central to Epicor ERP migration take?

Most Business Central to Epicor migrations land between 8 and 12 weeks for straightforward scopes (under 5,000 Customers, 2,000 Vendors, 10,000 Items, open orders only, no BOM or routing data). Migrations that include BOM and routing data, multi-site inventory across multiple warehouse and location tables, large historical ledger entries (over 500,000 rows), or active AL custom extensions move to 12-18 weeks because of the BOM transformation work, multi-site warehouse mapping, and the two-pass custom field migration. Epicor Kinetic cloud deployments add 1-2 weeks for environment provisioning and network configuration before data load begins.

Do Business Central workflows, Power Automate flows, and RapidStart packages migrate to Epicor ERP?

No. Business Central approval workflows and Power Automate flows are environment-specific and built on Microsoft's workflow engine; Epicor Kinetic uses a different workflow engine (Epicor Functions, BPM, and Method Directives) with different trigger models, action types, and conditions. We do not migrate them as code. We deliver a written inventory of every active Business Central workflow and Power Automate flow with its trigger conditions, approver chain, action sequence, and recommended Epicor Kinetic equivalent. The customer's Epicor administrator or an Epicor manufacturing consultant rebuilds them post-migration. RapidStart configuration packages similarly do not migrate; they are documented for reference only.

Can we keep Business Central for some entities while moving others to Epicor ERP?

Yes, a phased migration is a common pattern for multi-entity Business Central tenants moving to Epicor Kinetic. We can migrate individual Business Central companies or business units to separate Epicor partitions or companies while leaving the remaining Business Central entities live. The customer defines the phasing order during scoping, and we execute migration in sequence per the agreed cutover schedule. We recommend migrating the entity with the most complex data first (typically manufacturing or distribution) to surface any schema or mapping issues before the remaining entities move. Cross-entity reporting requirements between the two systems during the migration window are addressed through temporary data export tools or a read-only Business Central access layer.

Do we lose historical posted transactions (G/L Entries, Item Ledger Entries, Value Entries)?

We do not lose the data; we archive it strategically. Full historical replay of Business Central posted transaction tables can mean millions of G/L Entry and Item Ledger Entry rows, which extend the cutover window significantly and add little operational value compared to the cost of migrating them. We negotiate a migration cutoff with the customer during scoping (typically 12-24 months of posted history), carry forward account and inventory balances as Epicor opening balance entries for pre-cutoff periods, and archive the detailed pre-cutoff G/L Entry and Item Ledger Entry history in an external data store accessible for compliance and audit access. Customers that require immediate access to historical detail in Epicor can opt for a fuller historical migration at additional cost.

How are Business Central custom AL extension fields handled in Epicor ERP?

Business Central AL extension fields are stored in separate extension tables and do not have a direct Epicor schema counterpart. We identify all active AL extension fields during the discovery phase, map each to an equivalent Epicor User Defined (UD) field on the corresponding standard table (or to a custom UD table), and import the custom field data in a second pass after the base entity migration validates. Any custom field that overlaps with a standard Business Central field is flagged before migration to prevent duplicate or conflicting data. The customer's Epicor administrator validates UD field labels, validation rules, and any associated business logic after migration. This two-pass approach keeps the base entity migration clean and defers custom field conflicts to a separate, controllable pass.

What happens to our Business Central BOM and routing data in Epicor ERP?

Business Central Premium BOM and routing data (Production BOM, Production Order Routing, work centers, machine centers) requires manual transformation and separate import into Epicor Kinetic rather than a direct data migration. We deliver a written BOM and routing transformation map that documents the translation from Business Central BOM structure (Parent Item, BOM Version, Production BOM Lines) to Epicor's Part, BOMHead, BOMDetail, PartOpr, and WorkCenter tables. The transformation map is reviewed and executed by the customer's Epicor administrator or manufacturing consultant using Epicor's data load tools after the master data migration validates. Active Production Orders from Business Central migrate as Epicor JobHead and JobMtl records with current production stage, quantity, and scheduled dates preserved.

Does FlitStack AI also migrate from Epicor ERP back to Business Central?

Yes. We handle bidirectional migrations between Business Central and Epicor ERP. The reverse migration (Epicor to Business Central) involves extracting from Epicor's normalized table structure and transforming to Business Central's de-normalized data entity format, which is a different mapping than the Business Central-to-Epicor direction. Epicor's IDO interface and REST API serve as the extraction layer, and we apply the same migration methodology: discovery scoping, table-level field mapping, phased master and transactional load, BOM and routing documentation, and workflow inventory handoff.

## Related migrations

[![](https://flitstack.ai/platforms-trim/epicor-prophet-21.webp) Migrate to **Epicor Prophet 21** Every source we move into Epicor Prophet 21, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/erp/epicor-prophet-21) [**NetSuite to Epicor Prophet 21** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/epicor-prophet-21) [**Odoo ERP to Epicor Prophet 21** Mapping · history · rollback](https://flitstack.ai/migrations/erp/odoo-erp/to/epicor-prophet-21) [**Edicom EDI to Epicor Prophet 21** Mapping · history · rollback](https://flitstack.ai/migrations/erp/edicom-edi/to/epicor-prophet-21)

## Sources: official documentation

1. [Data Migration Tools (DMT) — Epicor](https://www.epicor.com/en-us/products/enterprise-resource-planning-erp/kinetic/global-business-management/ptw-data-migration-tool/)
2. [Export and import a Multi-Level BOM — Epicor User Help Forum](https://www.epiusers.help/t/how-can-i-export-and-import-a-multi-level-bom-bill-of-material/76708)
3. [Importing History from Old ERP System — Epicor User Help Forum](https://www.epiusers.help/t/importing-history-from-old-erp-system/97587)
4. [Importing History from Old ERP System (page 2) — Epicor User Help Forum](https://www.epiusers.help/t/importing-history-from-old-erp-system/97587?page=2)
5. [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)
6. [Update currency exchange rates — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-update-currencies)
7. [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)

Get a quote

## Moving from Business Central to Epicor Prophet 21?

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

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