Migrate from Kentro ERP & 3PL to Microsoft Dynamics 365 Business Central

Kentro Products with variants and SKU-level tracking map to Microsoft Dynamics 365 Item records. We map Kentro product variants to Dynamics 365 product variants using the ProductVariants table in Business Central or the EcoResProductVariant table in Finance & Operations. Kentro's hs_sku equivalent maps to Item No. or Global Trade Item Number (GTIN) fields. Pricing tiers from Kentro map to Microsoft Dynamics 365 Sales Prices and Discount groups. The product catalog is migrated first because Sales Orders and Inventory transactions depend on valid Item references.

Kentro real-time inventory positions across locations map to Dynamics 365 Item Ledger Entries for financial inventory and Warehouse Entries for bin-level tracking. We map Kentro warehouse locations to Dynamics 365 Locations, preserving FIFO/FEFO tracking logic as Lot Tracking or Serial Number setup in inventory posting groups. Current stock snapshots migrate as opening quantities; historical movement logs migrate as posted Item Ledger Entry records with Entry exit values preserved for audit trails.

Kentro Orders flow through the full lifecycle from channel receipt to fulfillment. We map open orders to Microsoft Dynamics 365 Sales Orders with Order Status, shipping address, and line items preserved. Historical fulfilled orders migrate as Sales Invoice records with the original order reference. Returns and refunds map to Sales Return Orders or Credit Memos linked to the original invoice. The Kentro order number becomes the External Document No. in Dynamics 365 for cross-system reconciliation.

Kentro B2C customers map to Dynamics 365 Customer records. We map customer name, email, phone, and address fields directly. Kentro's address associations map to Dynamics 365 Address fields with the Ship-to and Bill-to roles preserved. Customer pricing terms from Kentro map to Customer Price Groups in Dynamics 365. B2C customer records are migrated before Sales Orders so that Customer No. references are satisfied at import time.

Kentro B2B company accounts map to Dynamics 365 Customer records with associated Contact records for individual buyers. Company-level pricing terms map to Customer Price Groups or Customer Discount Groups. The B2B account hierarchy in Kentro (parent company with subsidiary locations) maps to Dynamics 365 Customer hierarchies using the Ship-To Address functionality or the Contact Organization feature in Business Central.

Kentro Supplier records with contact details, lead times, and default terms map to Dynamics 365 Vendor records. Vendor address, payment terms, and shipment terms migrate directly. Kentro purchase orders map to Dynamics 365 Purchase Orders with Vendor No. resolved at import time. Vendor catalog items (if any) can be mapped to Item records flagged as purchased rather than sold.

Kentro supplier-facing purchase orders map to Dynamics 365 Purchase Orders. PO status, expected delivery dates, and line items migrate. Any custom approval chains in Kentro are flagged in the handoff document for manual configuration in Dynamics 365 approval workflows. Open POs migrate with their current status; closed POs migrate as posted Purchase Receipts and Invoices.

Kentro multi-client 3PL setups host each client as a separate tenant partition within one database. We isolate each client's inventory pool, order history, and billing records and map them into separate Dynamics 365 Companies (Business Central) or Legal Entities (Finance & Operations). This ensures that one 3PL client's inventory does not blend with another's. The mapping requires a client-to-company lookup table built during discovery.

Kentro inter-warehouse transfer orders map to Dynamics 365 Transfer Orders with From Location and To Location fields populated. Transfer status at migration time determines whether the transfer migrates as an open Transfer Order or as a posted Transfer Receipt. In-transit items during migration window are flagged for a delta migration after cutover.

Kentro fulfillment events and carrier tracking data linked to orders map to Microsoft Dynamics 365 Sales Shipment records. We map shipping method names and tracking numbers to the Shipment Header. Carrier-specific metadata (e.g., FedEx SmartPost details) may require supplementary export from Kentro or re-entry in Dynamics 365's shipping documentation if no middleware connector is in place.

Kentro marketplace connections, Shopify integration, and channel-specific settings map to Dynamics 365 integration configurations or AppExchange connectors. We preserve the channel-to-order linkage so historical orders retain their originating source (Shopify, Amazon, eBay, Walmart) as a custom field. Channel-specific settings (e.g., Shopify-specific inventory rules) are documented for rebuild in the destination's integration layer.

Kentro EDI compliance documents (EDI 850 purchase orders, EDI 856 ASN feeds, EDI 810 invoices) used for B2B wholesale operations are preserved as document attachments linked to the corresponding Sales Order or Purchase Order in Dynamics 365. Because Dynamics 365 Business Central does not have native EDI parsing, we store the original EDI document as a PDF or XML attachment with the document type noted. A separate EDI rebuild plan documents the recommended ISV connector (Cleo, True Commerce) to restore automated EDI processing post-migration.

Kentro IQ reports and underlying datasets migrate as static report snapshots for historical reference. We export available report definitions and the data they query. Power BI report configurations that replicate Kentro IQ analysis (inventory velocity, order fulfillment rates, SKU performance) are documented for rebuild in Power BI Desktop and published to the Dynamics 365 workspace. Native Dynamics 365 reports that cover equivalent metrics are identified during discovery.

Kentro file attachments on orders, products, or customers migrate as Dynamics 365 Document Attachment records linked via the Related Record ID to the parent record. We preserve attachment URLs from Kentro's file storage and re-link them where Dynamics 365 supports incoming file references. Large document archives may require Azure Blob Storage configuration in the destination environment.