Migrate from iDempiere to Microsoft Dynamics 365 Business Central

iDempiere's Client > Organization hierarchy is the foundational structure that must be created before any other data. Each iDempiere Client maps to a Microsoft Dynamics 365 legal entity (Business Central Company or Finance legal entity). Child Organizations under a Client map to Business Central Operating Units. We extract the full AD_Client and AD_Org tree from iDempiere's PostgreSQL database, then configure the corresponding Company and Operating Unit structure in Business Central or Finance using the Organizations API before any master or transactional data is imported.

iDempiere Business Partners with IsCustomer=TRUE map to Dynamics 365 Customer records split into separate Customer and Vendor entities. BP locations (address tabs) map to Dynamics 365 Address lines with address-type roles (Invoice-to, Ship-to, Purchase-from). Pricing schemas attached to the BP in iDempiere become Customer Price Groups in Business Central. Credit limits and payment terms migrate to Customer records. We resolve the BP's default GL Bank Account to the corresponding Vendor bank account in Finance.

iDempiere Products map to Dynamics 365 Items (for inventory-tracked products) or direct Product records for non-inventoried items. BOM structures in iDempiere map to Dynamics 365 Bills of Materials on the Item. Product categories map to Item Categories. Costing method (Standard, Average, LIFO, FIFO) migrates to Business Central's Costing Method field. Product attributes and configured variants in iDempiere's Product Attributes window map to Dynamics 365 Item Variant records with the corresponding dimension values.

iDempiere orders (C_Order with C_OrderLine) map to Microsoft Dynamics 365 Sales Order and Purchase Order documents. Header-level fields (document number, date, BP reference, description, payment terms, warehouse) and line-level fields (product, quantity, unit of measure, pricing, tax, warehouse, GL account) all migrate. Document status from iDempiere (Draft, In Progress, Completed, Closed) maps to Business Central's document status (Open, Released, Pending, Closed). We resolve the C_BPartner_Location_ID to the correct Dynamics 365 Ship-to address at line creation time.

iDempiere invoices (C_Invoice with C_InvoiceLine) map to Microsoft Dynamics 365 Sales Invoice and Vendor Invoice records. iDempiere's document number becomes the Dynamics 365 document number. Payment terms from the BP migrate to the Invoice Header. Tax codes in iDempiere map to Dynamics 365 Tax Groups and Tax Business Posting Groups. GL journal references from iDempiere become General Journal entries linked to the posted invoice. Open invoices are imported as Open; historical closed invoices are imported with their posting dates and amounts preserved for GL reconciliation.

iDempiere payment batches (C_Payment) and cash journal entries map to Dynamics 365 Payment Journal lines. Bank statement mappings and allocation details migrate to Bank Account Reconciliation records. Open AP and AR records carry their payment terms and aging bucket assignments into Business Central's Payment Terms and Reminder Terms configuration. Cash and bank accounts with currency assignments map to the corresponding Bank Account records in Finance with Multi-Currency enabled if the iDempiere setup uses multiple currencies.

iDempiere Projects (C_Project) with their phases (C_ProjectPhase) and tasks (C_ProjectLine) map to Dynamics 365 Jobs (Business Central) or Projects (Finance Project Accounting). Project status, start date, end date, customer, and contract amount migrate. Phase-level milestones map to Project Tasks with WBS hierarchy preserved. Time entries (S_TimeExpense or C_ProjectLine with time type) migrate to Project Journal Lines in Finance or Time Sheets in Business Central. Project billing method maps to the Dynamics 365 billing policy on the Job.

iDempiere fixed asset registers (A_Asset with A_Asset_Acct, A_Depreciation tables) map to Dynamics 365 Fixed Asset records with corresponding Depreciation Books. Depreciation methods (straight-line, declining balance, units-of-production) migrate to Fixed Asset Depreciation Book entries. Asset book, insurance mappings, and service history migrate as Asset Comments and Custom Fields. Opening balances for fixed assets map to General Ledger entries in the target accounting schema.

iDempiere's multiple accounting schemas per tenant map to one or more Finance or Business Central Companies, each with its own Chart of Accounts. iDempiere's dimensional GL structure (Legal Entity, Business Partner, Product, Location dimensions) must be recreated in Dynamics 365 as Financial Dimensions (segments on the account string). We extract the AD_Column dimension assignments per accounting schema, then configure corresponding Financial Dimension sets in Finance using the Dimension Sets API. GL journal history migrates as closed periods with a GL Entry import.

iDempiere tax categories, rates (C_Tax), and validity windows migrate to Dynamics 365 Tax Groups and Tax Jurisdictions. Tax jurisdiction assignments per location are preserved so the correct rates apply post-migration. We map C_TaxCategory to Tax Group and C_Tax to Tax Code, then configure Tax Posting Setup linking Tax Group + Product Tax Group combinations to the correct Purchase and Sales Tax accounts. Valid-from dates become Effective Date in Dynamics 365 tax jurisdiction configuration.

iDempiere users (AD_User) and role-based security assignments (AD_Role, AD_User_Roles) map to Dynamics 365 Users and Security Groups or Teams. We extract role-privilege records from AD_Role_Access and map them to Business Central Permission Sets or Finance Security Roles. Multi-org data access scopes in iDempiere (OrgAccess records) map to Business Central's User Setup and Delegation configuration. Any user without a corresponding Microsoft 365 Azure AD account goes to a reconciliation queue for the customer's IT admin to provision before user import proceeds.

iDempiere custom windows registered in the Application Dictionary are backed by custom database tables with AD_Column, AD_Tab, and AD_Field metadata. We export the underlying table data (the custom entity records) and deliver the AD metadata as a written report. The visual form layout and field sequencing must be rebuilt by the customer's Dynamics 365 administrator using Business Central's Page Designer or Finance's customization tools. We do not migrate AD form layouts as code; we provide the schema and data for manual rebuild.

iDempiere attachments stored in the database (LOB) or filesystem are detected at scoping using the Migrate Storage Provider plugin configuration. Files are extracted and mapped to Dynamics 365 Document Attachment records linked to the corresponding entity (Customer, Vendor, Item, Order). For Business Central cloud, attachments are stored via SharePoint Online or OneDrive integration; we configure the document attachment storage provider during migration and attach files to the parent record post-import.