Migrate from Intact iQ to Epicor Prophet 21

Intact iQ Customer records carry addresses, price lists, credit limits, and account statuses. We extract via the REST API definition (or database if definitions are absent) and map to Epicor Customer with ShipTo and BillTo address records. Credit limit and account status map to the CustomerCredit table in Epicor. Multi-address customers in Intact iQ with multiple Properties create multiple ShipTo records in Epicor under a single Customer. Branch assignments in Intact iQ map to Epicor's Company or Site structure if the destination is multi-company.

Intact iQ Supplier records include contact details, payment terms, rebate agreements, and procurement history. We map Supplier to Epicor Vendor with the address, payment terms, and rebate structure preserved. Epicor Vendors require a采购Ledger account assignment which we resolve against the GL account mapping during schema design. Supplier-held stock arrangements in Intact iQ (consignment stock) are flagged for manual setup in Epicor rather than automated migration.

Intact iQ Contact records are linked to Customers and Suppliers and hold roles, phone numbers, and email addresses. The API exposes Contact with its parent Customer link. We map to Epicor Person records attached to the corresponding Customer. The Intact iQ contact role (Buyer, Account Contact, Site Manager) maps to the Person Type field in Epicor.

Intact iQ Stock Items carry complex relationships: BOM structures, variant codes, reorder levels, ABC categories, and predictive stock management rules. We map Stock Item to Epicor Part with BOM (Bill of Materials) structures mapped to Epicor's BOM table. Variant codes in Intact iQ (size, colour, pack configurations) map to Part Number modifiers or Epicor's PartRev configuration. Reorder levels and ABC categories require mapping to Epicor's planning and ABC code fields. The Intact iQ predictive stock management rules are documented for rebuild in Epicor's MRP or Demand Workbench.

Open and historical sales orders are extractable via the Intact iQ REST API as a defined service. We preserve order line items, pricing, discount structures, and order status. Closed orders migrate as historical records with their original dates and amounts. The Intact iQ sales order number becomes a custom field in Epicor SalesOrder for audit trail. Invoiced orders in Intact iQ map to Epicor Invoice records with AR aging preserved.

Intact iQ Purchase Order records include supplier references, expected delivery dates, and line-level item assignments. We extract the full PO lifecycle from draft through receipt and close. Epicor POHeader maps from the supplier and order header; POLine maps from the line item, quantity, unit cost, and expected receipt date. Received POs in Intact iQ require Epicor Receipt processing records to be generated for the receiving log.

Intact iQ Chart of Accounts records carry account codes, types, and cost-centre assignments. Account code structures vary between Intact iQ configurations, so we validate the destination Epicor chart before mapping. The account code format in Intact iQ (numeric, alphanumeric, segment-separated) must be reconciled against Epicor's account segment structure. Cost centre assignments in Intact iQ map to Epicor GL Account segments or Department codes depending on the destination configuration.

Outstanding Intact iQ invoices and credit notes require careful sequencing. We extract current open items, map them to Epicor's APInvoice and ARInvoice tables, and flag any partial payments or credit allocations. The outstanding balance and due date migrate with the record. Aged AP/AR reports from Intact iQ are used to validate the Epicor aging report post-migration. This is a high-risk migration phase requiring explicit sign-off on the open item count before cutover.

Intact iQ User records include roles, branch assignments, and permissions hierarchies. We map permissions to Epicor UserCode with the corresponding Plant and Company assignments. Intact iQ branch-based user restrictions map to Epicor's Site access controls. Any Intact iQ permission that has no Epicor equivalent goes to a reconciliation list for the customer's admin to review.

Intact iQ Bank and Cash Accounts are accessible via the REST API as defined services. We extract current balances and recent transactions for re-creation at Epicor as BankAcct records with opening balances posted to the GL. Bank reconciliation data from Intact iQ is used to set the Epicor Bank Reconciliation starting point.

Intact iQ custom fields on any standard object are stored in the database and require manual identification during scoping. We identify all custom field names and data types pre-extraction and map them to Epicor UD Column definitions. UD columns in Epicor require BPM methods to populate them during transaction processing, which means the migration team designs the BPM logic alongside the data mapping. This is a configuration-intensive step not present in all ERP migrations.

Documents and files attached to Orders, Contacts, or Stock Items in Intact iQ are stored in the internal attachment layer not exposed via REST API. We flag this during scoping and advise customers to use Intact iQ's native export or manual download for documents before cutover, then re-attach in Epicor post-migration. No document migration path exists without manual intervention.