Migrate from Datacor ERP to Microsoft Dynamics 365 Business Central

Datacor Items carry formula data, BOM versions, unit-of-measure conversions, and shelf-life metadata that require decomposition into Dynamics 365 product structure. We extract Items with all associated BOM levels, then map the formula data to Dynamics BOM lines, unit-of-measure classes to Unit of Measure Groups, and shelf-life metadata to Tracking dimension groups or product extensions. Co-products and by-products from Datacor's production model map to BOM line types in Dynamics.

Datacor's cradle-to-grave lot tracking is a core strength. We preserve full lot genealogy including parent lots, co-products, by-products, and downstream consumption records. Lot numbers, dates, statuses, and locations transfer to Dynamics inventory dimensions. We resolve lot genealogy chains (parent-to-child lot relationships) and map consumption records to inventory transactions in Dynamics. Co-product and by-product splits preserve the production yield percentages for cost allocation.

Datacor Customer records include customer-specific pricing, credit limits, discount schedules, and multi-address support. We map these to Dynamics 365 Customer and Address entities. Customer-specific pricing tiers from Datacor's CUPS matrix migrate to Dynamics Trade Agreements or custom price list tables attached to the Customer record. Multi-address support (billing, shipping, multiple plant deliveries) maps to Dynamics address purposes.

Datacor Vendor records carry CUPS (Complex Unit Price Schedules), rebate logic, and multi-source purchasing flags. These are preserved as Vendor custom properties in Dynamics 365, with rebate schedules mapped to Trade Agreements and multi-source flags translated to vendor-level purchasing settings. Vendor-specific lead times and delivery schedules become purchase agreement lines.

Open POs must be mapped by line item and delivery schedule. We extract PO headers, lines, and delivery schedules, then flag partially-received POs and hold them open or close them manually post-migration depending on the customer's preference. Datacor's multi-source purchasing logic (splitting PO quantities across vendors) does not have a direct Dynamics equivalent; we document the source logic for the customer's purchasing team to configure in Dynamics vendor agreements.

Datacor Sales Order headers and lines carry customer-product pricing, freight terms, and shipping method logic tied to Datacor's truck routing module. We extract open orders by status, map pricing to Dynamics Trade Agreements, and flag orders with partial shipment history. Truck routing and freight logic does not migrate; we document the routing rules as a reference for the customer's admin to configure in Dynamics Transportation Management or as a Power Automate flow.

Datacor Batch production orders include formula versions, scheduled start/end times, and consumption/yield records. We flag in-process batches that cannot be safely cut over and advise running those to completion or formal closure before migration day. Completed production orders migrate as production history with full consumption and yield data. We extract BOM versions, production schedules, and the cost calculations tied to each batch for cost rollup in Dynamics.

QC inspection records link to lots and items in Datacor. We extract the inspection history, disposition decisions (Accept, Reject, Rework), and certificate-of-analysis data, mapping them to Dynamics 365 Quality Management modules or custom tables if the destination tenant does not include the Quality Management module. Inspection templates migrate as quality associations linked to product and warehouse dimensions.

Datacor's GL structure with accounts, departments, cost centers, and journal entry history migrates directly to Dynamics 365 Finance & Operations or Business Central main account hierarchies. We map the account hierarchy, preserve posting dates and amounts for historical financial records, and translate Datacor's department and cost center dimensions to Dynamics Financial Dimensions. Journal entry headers and lines migrate as open or historical journal batches depending on account status.

Open AR and AP records with payment terms and discount schedules migrate as open invoices in Dynamics 365. We flag records with outstanding credits, holds, or partial payments and handle them as exceptions. Datacor's aging bucket definitions map to Dynamics terms and conditions. Post-dated checks and security deposits migrate as financial dimension data or ledger account configurations.

Datacor equipment records with maintenance schedules, work orders, and asset specifications migrate as Fixed Assets or Assets in Dynamics 365 depending on the target tenant's asset management configuration. Preventive maintenance schedules map to Work Orders or Asset Service Plans. Meter readings and maintenance history transfer to asset lifecycle records. Depreciation methods and book values migrate to Fixed Asset registers.

SDS records are regulatory artifacts managed by Datacor's regulatory module and linked to Items. We do not migrate SDS documents; we extract the item-to-SDS associations as a reference table and flag the SDS linkage so it can be re-generated or re-linked in the destination compliance system post-migration. The customer must budget for re-attaching SDS documents to items in Dynamics 365 compliance or a third-party regulatory management system.