Migrate from Integra ERP to Infor CloudSuite Corporate

Integra ERP's Chart of Accounts stores account codes, names, and types in a flat or hierarchical structure. We map each account code to the destination General Ledger account using a customer-provided account-mapping spreadsheet validated by the finance team. Account-type mapping (Asset, Liability, Equity, Revenue, Expense) preserves the trial balance at migration cutover. If Integra ERP uses a segmented account code structure (e.g., Cost Centre.Company.Type), we flatten or restructure the segments per the Infor CloudSuite Financials chart design.

Integra ERP Customer records (name, billing address, GST/VAT registration, credit terms, contact details, open AR balance) map directly to Infor CloudSuite Business Partner records. We set the BP type to Customer and preserve the GST registration number in the tax registration field. Open AR balances as of cutover date migrate as opening balance journal entries rather than individual invoices unless the destination requires open item management.

Integra ERP Vendor records (name, payment terms, GST/VAT registration, address, vendor-specific item pricing) map to Infor CloudSuite Business Partner with BP type set to Supplier. Vendor-specific item pricing is preserved as a pricing schedule on the Business Partner. Open AP balances as of cutover migrate as opening balance entries rather than individual vouchers in most destination configurations.

Integra ERP Items may carry branch-specific stock values, classification codes, and BOM structures. We flatten BOM hierarchies into individual item records during transform: each component of a BOM becomes a standalone item with its own unit of measure and cost. Integra-specific classification codes that do not map to standard Infor item categories are added as custom attributes via Infor OS extensions. Branch-level stock aggregates are mapped to destination warehouse or location codes.

Manufacturing customers with BOMs in Integra ERP must decide whether to flatten them during migration or recreate them in Infor CloudSuite Industrial. We extract BOMs as separate structured records, note the parent-item and component relationships, and deliver a BOM mapping spreadsheet alongside the standard item migration. The customer and their Infor implementation partner decide whether to load BOMs via Infor's data migration utility or rebuild them in the CloudSuite Manufacturing configuration.

Outstanding payable and receivable balances must be migrated as opening balance journal entries in Infor CloudSuite Financials rather than individual invoices, because most destination configurations do not replicate Integra ERP's open-item invoice tracking. We extract the net outstanding amount per vendor and per customer as of the cutover date, create corresponding GL entries, and flag the entries for the finance team to verify against source reports before finalizing.

Integra ERP stores stock quantities per branch or warehouse location. We aggregate by Item across all source branches and map to destination warehouse or location codes. Serial and batch tracking fields are preserved as custom attributes where present in the source. Stock valuation amounts (if stored separately) are mapped to the inventory valuation method configured in Infor CloudSuite.

Open and closed sales orders export with header fields (order number, date, customer reference, order status, terms) and line items (item number, quantity, unit price, discounts). We map Integra ERP order-status values to Infor CloudSuite Sales Order status workflow states. Orders referencing voided or inactive customers are flagged in a reconciliation report for the customer to resolve before import.

Full transaction history—sales orders, purchase receipts, and journal entries—requires extraction of header-and-line linked tables from Integra ERP. We load historical data in dependency order (journals first to establish account balances, then transactions) and deliver a reconciliation report comparing source totals to destination sums by account and period. Loading historical data is optional for reporting-only scenarios; the customer specifies the lookback window during scoping.

Integra ERP's employee management module provides employee records including department assignment and basic compensation fields. We transfer them as Employee Master records in Infor CloudSuite HCM where available. Note that Infor CloudSuite editions without an HCM module require this data to be loaded into a separate HR system or held for manual entry.

Attachments, scanned documents, and PDFs stored inside Integra ERP are not exposed via a documented export mechanism. We extract any linked file paths from the source database but cannot guarantee file integrity or completeness. The customer should archive these files separately using the on-premise file system before decommissioning Integra ERP.