Migrate from Base ERP to Microsoft Dynamics 365 Business Central

Base ERP Warehouses map to D365 Sites (the organizational unit for inventory control) and Location records within each Site. We preserve the warehouse name, address, and active status. Multi-warehouse accounts in Base ERP become multiple Site-Location pairs in D365. If the customer uses warehouse-specific stock rules or transfer orders, we map those to D365 Warehouse Management (WMS) configurations under the site.

Base ERP Offers (SKU, name, description, images, weight, dimensions) map to D365 Items of type Product or Service. The Base ERP product_type distinguishes stocked vs non-stocked vs service items. We set the Item Type and Item Model Group accordingly so that inventory tracking behavior matches the source. Base ERP images migrate as attachments or blob references; D365 Item image storage is separate from the item record and requires a different ingestion path.

Base ERP stores real-time stock as integer quantities per warehouse per product at a point in time. D365 models inventory using dimension combinations (Site, Location, Warehouse, Batch, Serial, Variant). We capture the full stock snapshot at migration start time, then map each Base ERP warehouse-stock row to a D365 on-hand entry with the corresponding Site and Location. Inventory posting groups and dimension defaults require pre-configuration before stock loads.

Base ERP Orders (customer details, line items, shipping address, payment method, status, fulfillment tracking) map to D365 Sales Order with Sales Order Lines. We preserve the order number, order date, customer account, ship-to address, payment terms, and status. D365 requires a Customer record as a prerequisite for every Sales Order, so we map Base ERP order customer data to D365 Customer (contact name, email, phone, address) before loading order headers.

Base ERP pricing rules defined per marketplace channel or per quantity tier export as flat key-value pairs. D365 uses Price Lists scoped to Customer or Customer Price Group with line-specific pricing. We expand the flat pricing export into multiple D365 Price List entries and create a Customer Price Group record per Base ERP marketplace channel. Quantity-based tiers become D365 Sales Price records with minimum quantity thresholds.

BaseLinker connector profiles (channel type, listing IDs, sync rules) are mapped and documented as a written reference document. Base ERP channel credentials (API keys, tokens) cannot be extracted via standard export and require manual re-entry at the destination. We deliver a channel-by-channel reconnect checklist so the customer's admin re-establishes marketplace listings without re-entering all configuration from scratch.

Base ERP custom fields per product (e.g., certifications, seasonal flags, custom dimensions) export as extra columns in the product CSV. We create corresponding custom fields on the D365 Item table (Item table extensions via Power Objects or custom fields), rename them to match source labels, and type-cast values (decimal, integer, text) to match D365 field definitions. Custom fields on non-item objects (e.g., order extensions) require separate extension object configuration.

Base ERP user accounts with roles (Admin, Operator, Warehouse Manager) map to D365 User records. We resolve users by email match. Role assignments from Base ERP (Admin, Operator, Warehouse Manager) map to D365 Security Groups or permission sets. Users without a matching D365 tenant account go to a reconciliation queue for the admin to provision before migration proceeds.

Base ERP's warehouse-to-marketplace channel assignments (which warehouse feeds which channel) have no direct D365 equivalent. We document each warehouse-channel relationship and recommend a D365 Inventory Posting Profile setup per site-channel pair so that inventory posting accounts match the original financial flow. This is configuration-only work delivered as a written spec.

Base ERP's Inventory Control module is explicitly marked beta in official documentation. We extract any records in this module under a versioned schema snapshot to prevent breakage if the source schema changes during the migration window. We flag the record count and schema for customer review and do not assume these records map to standard D365 inventory objects without explicit customer confirmation.

Base ERP does not generate invoices internally; invoicing is handled via external accounting tools integrated through BaseLinker. We do not migrate invoice records. Customers should export invoices from their connected accounting system directly. We do not have access to invoice data from the Base ERP export layer.

Base ERP order fulfillment tracking fields (tracking number, carrier, shipment status) map to D365 Warehouse Shipment tracking or to a custom field on the Sales Order. We preserve the tracking URL pattern if present. D365's shipment management requires WMS to be enabled for full tracking automation; we configure this based on the customer's Business Central edition and warehouse management requirements.