Migrate from Aptean Compiere ERP to Microsoft Dynamics 365 Business Central

Compiere Business Partners with Partner Group = Customer map to Dynamics 365 Business Central Contacts. The Compiere BP name, address, phone, email, and tax ID fields map to Contact name, address, phone, e-mail, and tax registration number. Contact is created with a link to the corresponding Account. We resolve the Compiere multi-org location by mapping the Organization-level address to the Contact address, and we flag any Business Partner with a blank email for manual review before import.

Compiere Business Partners with Partner Group = Vendor map to Dynamics 365 Business Central Vendors. The Compiere BP name, address, phone, email, and tax ID map to Vendor name, address, phone, e-mail, and tax registration number. We map Compiere's payment rule and credit limit fields to Dynamics 365 Vendor payment terms and credit limit, and we link the vendor to the correct Purchasing VAT registration if applicable.

Compiere Products map to Dynamics 365 Items. The product type (Item Type = Stocked, Non-Stocked, or Service) maps to Item type in Dynamics 365. Compiere's Product Category, unit of measure, cost method, and standard cost transfer to Item Category, Unit of Measure Code, Costing Method, and Standard Cost respectively. Compiere's hs_sku equivalent or the product value becomes the Item number.

Compiere multi-level BOMs with parent products and component lines map to Dynamics 365 Business Central Production BOMs. Each Compiere BOM level becomes a BOM Header with routing lines. We preserve the full component hierarchy by resolving Compiere Product IDs to Dynamics 365 Item numbers at migration time, and we flag any circular BOM reference for the customer's engineering team to resolve before import. Manufacturing module is required in Business Central Premium or Finance for production BOMs.

Compiere Warehouses map to Dynamics 365 Locations. Each Compiere Warehouse code becomes a Location Code in Business Central. We map the Compiere Warehouse address to the Location address, and we configure the inventory posting group mapping so that inventory valuation posts to the correct general ledger accounts.

Compiere Locators with up to five user-defined dimensions (aisle, bin, rack, level, bay) map to Dynamics 365 bin content records. We use the Compiere Locator's most granular dimension (typically the bin or bay level) as the primary bin code in Dynamics 365, and we configure the zone and bin location structure accordingly. If Compiere uses fewer than five dimensions, we map the available dimensions to the corresponding Dynamics 365 bin location levels. Warehouse must be created before Locator import.

Compiere Purchase Price Lists map to Dynamics 365 Purchase Prices linked to Items and Vendors. Each active Compiere price line (Product + Vendor + Unit Price + Currency + Effective Date) becomes a Purchase Price record in Business Central with the vendor lookup, item lookup, and unit of measure resolved at migration time. Expired price lines are archived rather than imported.

Compiere Sales Price Lists map to Microsoft Dynamics 365 Sales Prices linked to Items and Customer Price Groups. Each active Compiere price line (Product + Customer Group + Unit Price + Currency + Effective Date) becomes a Sales Price record in Business Central. We map Compiere's customer-specific pricing by creating Customer Price Groups in Business Central and linking them to the corresponding Sales Price records.

Compiere's country-specific AccountingXX.csv import files map to Dynamics 365 G/L Account records. We parse the source CSV, extract account number, name, account type, and posting group, and create G/L Accounts in Business Central using the standard chart of accounts structure. We configure the Account Category and the posting profile so that balance sheet and income statement accounts route correctly. Multiple Accounting Schemas in Compiere map to separate Posting Profiles or dimension sets in Dynamics 365.

Open Compiere AP records (invoices with unpaid status) map to Dynamics 365 Vendor Ledger Entries and open Purchase Invoices. We map Compiere Invoice Number to External Document Number, Invoice Date to Posting Date, due date to Due Date, and the outstanding amount to Amount. Vendor lookup resolves by matching the Business Partner vendor to the Dynamics 365 Vendor. We do not migrate historical closed AP records as part of standard scope.

Open Compiere AR records (invoices with unpaid status) map to Dynamics 365 Customer Ledger Entries and open Sales Invoices. We map Compiere Invoice Number to External Document Number, Invoice Date to Posting Date, due date to Due Date, and the outstanding amount to Amount. Customer lookup resolves by matching the Business Partner customer to the Dynamics 365 Customer. We do not migrate historical closed AR records as part of standard scope.

Compiere Product Categories map to Dynamics 365 Item Categories. The category name, default cost method, and default posting group transfer to the Item Category record. Product Categories must be created before Product import so that the Item Category assignment is satisfied at migration time.

Compiere users map to Dynamics 365 Users by email match. The Compiere three-tier role hierarchy (System, Client, Organization) maps to a combination of Business Central Security Groups and User Permissions. We resolve Compiere Role IDs to Dynamics 365 permission sets, and we flag any Compiere role without a direct Dynamics 365 equivalent for manual mapping by the customer's admin.

Each Compiere Accounting Schema (Chart of Accounts + accounting rules per Organization) maps to a Dynamics 365 Posting Profile and General Journal Template. We configure the posting profile to map each account type to the corresponding debit and credit G/L account, and we set up the journal template so that the correct default journal batch names are available at go-live.