Migrate from Epicor Prophet 21 to Microsoft Dynamics 365 Business Central

P21 Customer records map to D365 Account (CustomerType = Organization) or Contact (CustomerType = Person) depending on whether the account is B2B or B2C. We extract ship-to addresses, contact details, credit limits, and pricing tiers from P21 Customer and SalesTerritory tables. The AccountNumber from P21 becomes the AccountNumber in D365, and the CustPriceGrp from P21 maps to a PriceGroup or CustomerGroup in D365 depending on whether the destination is Business Central or Finance and Operations.

P21 Vendor master records map to D365 Vendor. We preserve address, payment terms, buyer assignment, and the vendor-to-item linkage that drives replenishment. P21's VendorGln maps to D365's GlobalLocationNumber for EDI readiness. Payment terms from P21's Terms table map to D365's PaymentTerm or CashDiscount entities.

P21 Item master maps to D365 Released Product (Finance and Operations) or Item (Business Central). Complex item structures require careful handling: sales kits map to D365 product bundles, job assemblies with BOMs require BOM and routing creation in D365, and kitted items map to BOM structures. Lot/serial controls from P21's ItemLotGrp and ItemSerialGrp tables map to D365 tracking dimension groups. We preserve the replenishment method (Min-Max, Order Point, Manually) from P21's Replenishment class to D365 coverage group settings.

Open and historical sales orders export from P21 OrderHead and OrderDtl tables. Line item pricing, discounts, warehouse fulfillment, and customer address linkages migrate to D365 SalesOrder and SalesOrderLine. We preserve the order-to-customer relationship via AccountNumber lookup. Completed orders migrate as historical records; open orders require additional status mapping from P21's OrderRel table for partial shipments. Order holds and credit blocks from P21 require manual recreation in D365's order-hold functionality.

PO records from P21 POHeader and POLine tables map to D365 PurchTable and PurchLine. Vendor pricing, lead times, and receipt schedules are included. Partially received POs require the receipt register and invoicing status preserved as D365 receipt and invoice records. PO approval workflows from P21 Business Process Modules require redesign in D365's workflow engine.

Quote headers and lines from P21 QuoteHed and QuoteDtl map to D365 SalesQuotation and SalesQuotationLine. Expiration dates, pricing, and customer linkage are preserved. Quotes with expired statuses are flagged for exclusion from migration to prevent stale data cluttering the new system. Active quotes with expired dates are reviewed with the customer before inclusion.

P21 GLAccount records map to D365 main accounts. Account segment structure varies by P21 company configuration, so we preserve the full account code string (including any cost center or department segments) and map it to D365's financial dimension structure. Multi-entity P21 setups with intercompany accounts require additional mapping to D365 legal entity configuration. Account types (Asset, Liability, Expense, Revenue) map from P21's AcctType field.

Open payables and receivables require careful sequencing. We extract invoice headers and line distributions from P21's InvoiceHead, InvoiceDtl, PayGrp, and RecGrp tables. Partially paid invoices are flagged with remaining balance preserved. In D365 Finance and Operations, open AP migrates as pending vendor invoices in the invoice journal; open AR migrates as pending customer invoices. D365 Business Central uses open customer ledger entries and vendor ledger entries. Historical paid invoices are optionally migrated for audit continuity, though many customers archive pre-migration history.

P21 warehouse records include bin locations, picking priorities, and cross-dock configurations from the Warehouse and Bin tables. Multi-warehouse setups extract cleanly via SQL. We map each P21 warehouse and its bin structure to D365's warehouse management configuration, including zone definitions and picking route sequences.

Lot and serial number tracking links to item and transaction history in P21. We preserve the lot number, expiration date, and cost layer (FIFO or lot-specific) during migration. Full traceability chains for received lots migrate to D365 inventory dimension tracking. P21's lot cost history requires mapping to D365's inventory value model.

P21 job assemblies with BOM and routing data map to D365 BOM and production routes. Sales kit components require BOM creation in D365 without production order linkage. Complex job assemblies with multiple operations and work centers map to D365 work centers and operations resources. We flag kit structures that require BOM redesign versus those that migrate as-is.

P21 user accounts and employee records with role-based permissions extract from the UserAcces and SalesRep tables. Territory coverage and buyer assignment link to order and quote ownership. User email addresses map to D365 User accounts via Azure Active Directory synchronization. Role assignments from P21 are inventoried as a written document for the customer to recreate in D365 security roles.

P21 customer-specific pricing tiers and volume discounts from the CustPriceGrp and PriceLst tables map to D365 price groups. We extract all active price list lines, effective dates, and quantity break tiers. The mapping preserves the tier structure for volume pricing but requires D365 trade agreements configuration to activate post-migration.