Migrate from iDempiere to Infor CloudSuite Corporate

iDempiere's top-level Client entity maps to Infor CloudSuite's Company (or Division depending on the CloudSuite edition). Multiple iDempiere Clients under one installation map to separate Infor Companies. We create the Company record first before any child data imports so that the referential integrity is satisfied on subsequent Business Partner and GL imports. Company-specific settings (fiscal year, base currency, segment structure) are configured in Infor before master data begins.

iDempiere Organization records under a Client map to Infor's organizational units (Division, Plant, or Warehouse depending on the CloudSuite edition and industry). Multi-org hierarchies must be recreated in the correct parent-child order in Infor before user-role assignments and Business Partner assignments are imported. Any Organization that is referenced on transactional records must exist in Infor before those records are imported.

iDempiere Business Partner covers customers, vendors, and leads under a single table with a BPType field. We split on BPType during migration: Customer and Vendor BP types map to Infor Customer and Supplier records respectively. Location and contact sub-tabs from iDempiere map to Infor's Address Book and Contact Person records. Credit data, pricing schemas, and payment terms migrate to Customer or Supplier configuration records. Lead-type BPs in iDempiere map to Infor Prospect records if the destination edition supports prospect management.

iDempiere Products with full BOM structures (Bill of Materials) map to Infor Item Master records with associated BOM definitions. Product categories from iDempiere map to Infor Product Groups. Stocking settings, warehouse assignments, and costing methods migrate to Infor Item Plant and Cost Element records. Configured products and product variants are preserved as Infor configured items. We resolve the product-organization assignment so that items are available in the correct Infor plant post-migration.

iDempiere BOM records (M_Product_BOM table) with component lines, quantities, and BOM type (Make-to-Order, Standard) map to Infor Bill of Materials or Formula depending on the CloudSuite edition (manufacturing vs process). The parent product must be imported as an Item Master before BOM lines can reference it. Phantom BOMs and BOM versioning are preserved with version numbers carried forward.

iDempiere C_Order header records with their C_OrderLine children map to Infor Sales Order or Purchase Order records. Document status, pricing, tax treatment, and warehouse assignments migrate directly. Header-level charges and discounts from iDempiere map to Infor Order Charges. Lines reference the imported Item Master and Customer or Supplier. We flag any Orders with Product IDs that failed the Item Master import for resolution before closing the migration window.

iDempiere C_Invoice records (Sales Invoice, Purchase Invoice, AR Credit Memo, AP Credit Memo) map to Infor Accounts Receivable or Accounts Payable Invoice records. Tax codes and rates migrate to Infor Tax Authority and Tax Code assignments per line. Payment terms and aging buckets carry forward. GL journal references on iDempiere invoices map to Infor Distribution Sets or manual account distributions depending on the CloudSuite accounting configuration.

iDempiere GL Journal entries (Fact_Acct table) with account combinations, debit/credit amounts, and dimensional values map to Infor General Ledger Journal Entries. The dimensional structure in iDempiere (up to 8 analytical dimensions) maps to Infor's configurable GL segment structure. We preserve the original iDempiere account combination string in a reference field and create the Infor journal in the corresponding posting date period. Opening balances for balance sheet accounts are imported as year-opening journal entries before transactional history begins.

iDempiere's C_ElementValue table (accounting element) maps to Infor's Account Master. The account structure dimensions (Account, Subsidiary, Business Partner, Product, Location, Project, Campaign, Activity) from iDempiere's accounting schema map to Infor's GL segment configuration. We build a mapping table during scoping that assigns each iDempiere dimension to the corresponding Infor segment, then generate the Infor segment structure in the target company before any GL data imports. Account type (Active, Passive, Memo, Budget) and posting control settings migrate to account-level configuration.

iDempiere C_Project records with phases, tasks, milestones, and time entries map to Infor Project Management records. Project status, contract type, and billable flags carry forward. Task assignments with user and role references are resolved against the imported User mapping. Project budgets from iDempiere map to Infor budget versions on the Project. Custom project types defined in the Application Dictionary migrate as standard project types with a note in the handoff documentation.

iDempiere A_Asset records with depreciation schedules, asset books, and insurance mappings map to Infor Fixed Asset records. Depreciation methods (straight-line, declining balance, units of production) migrate to Infor depreciation method configuration. Asset book assignments and current book values carry forward. The corresponding GL account from the chart of accounts mapping is assigned as the Accumulated Depreciation and Depreciation Expense account on the Infor Fixed Asset record.

iDempiere C_Payment records with allocation details, bank account references, and payment batch assignments map to Infor Payment records and Cash Journal Entries. Open AP/AR payment allocations migrate with their matching invoice references. Bank account mappings from iDempiere C_BankAccount map to Infor Bank Account records with GL account assignments for cash and bank charges.