Migrate from Intact iQ to Acumatica

Intact iQ customer records map to Acumatica Business Accounts with the Customer class designation. The primary contact, billing address, and delivery address fields transfer directly to their corresponding Acumatica address and contact entities. Customer codes are validated against Acumatica's character constraints — alphanumeric length and allowed special characters — before insert to prevent rejection during migration.

Intact iQ supplier records map to Acumatica Business Accounts with the Vendor class designation. Tax registration numbers transfer directly to the Tax Registration ID field on the vendor record. Multi-address suppliers: the primary address becomes the main vendor address in Acumatica; additional locations are stored as separate Location records linked to the same Business Account.

Stock items in Intact iQ split into Acumatica Stock Items (tracked inventory) and Non-Stock Items (catalog-only) based on the stock-control flag. Unit of measure conversions apply from Intact iQ's UDF to Acumatica's UOM table. Product categories map to Acumatica Item Classes.

Open and completed sales orders migrate with all line items, quantities, unit prices, and discounts fully preserved through the migration process. Order statuses in Intact iQ — Quoted, Processing, Completed, Cancelled — map directly to corresponding Acumatica SO status values. Historical orders retain their original order dates as the transaction date; create dates are stored in custom fields to preserve audit history beyond Acumatica's standard timestamp fields.

Open and completed purchase orders migrate with vendor details, line items, ordered quantities, and expected delivery dates transferred completely. Acumatica PO status values — Pending Approval, Open, Completed, Cancelled — receive their values from Intact iQ status codes via a value mapping table created during the discovery phase. Header-level notes and internal references are preserved in the Description field.

Intact iQ invoices map to Acumatica AR Invoices with the original invoice numbers preserved in the Reference Nbr. field for straightforward reconciliation. Tax codes on Intact iQ invoices map to corresponding Acumatica Tax Category IDs through value mapping. Payment applications migrate separately as AR Payment records linked by customer ID and invoice reference number to maintain the payment-to-invoice relationship.

Intact iQ supplier invoices map to Acumatica AP Bills. The vendor reference number from the supplier invoice is stored in the External Ref. field on the AP Bill for reconciliation purposes. Prepayments and credit notes from Intact iQ migrate as separate AP Bill documents of type Credit Note rather than standard invoices, preserving their financial impact against vendor accounts.

Customer credit notes from Intact iQ migrate as Acumatica AR Credit Memos and are linked to the original invoice via the Applied-to Document field where reference linkage exists in the source system. The credit amount and reason codes from Intact iQ are preserved in custom fields on the Acumatica credit memo for audit and dispute resolution purposes.

Customer payments migrate as AR Payments applied to the corresponding open invoices by matching the invoice reference number. Unapplied cash amounts from partially applied payments are retained as unapplied balances in Acumatica. Payment methods in Intact iQ — BACS, cheque, card, cash — map to Acumatica payment methods via value mapping created during the discovery phase.

Intact iQ product categories map directly to Acumatica Item Classes, which serve as the primary grouping mechanism for inventory items. The class hierarchy in Acumatica determines the default tax category, posting accounts, and default warehouse assignments for items within each class. Subcategories from Intact iQ nest under parent item classes in Acumatica's hierarchical structure.

Intact iQ branch records map to Acumatica Branches, with each branch receiving its own unique BranchID for inventory and financial posting segregation across entities. Inter-branch transactions that were handled natively in Intact iQ's Multi-Branch module require Acumatica inter-company transaction configuration as a separate setup step after initial branch creation.

Intact iQ price lists become Acumatica Sales Price Lists linked to customer classes or specific customer accounts for targeted pricing. Effective dates and expiry dates migrate with the price list headers. Volume-based pricing tiers — break quantities and corresponding prices — require custom fields in Acumatica since native price breaking is configured per price list rather than as multi-tier records.

Intact iQ warehouse records map to Acumatica Warehouses with their respective addresses and default issue/receipt settings transferred to the warehouse configuration. Quantities on hand from Intact iQ transfer as opening balances in the Inventory Valuation summary, applied after item and warehouse setup is complete to ensure correct stock positioning.

Contacts linked to customers and suppliers migrate as Acumatica Contacts with their full name, email address, phone number, and job title preserved. The contact's associated Business Account is linked via the AccountID field on the contact record. Primary contact designation from Intact iQ is preserved to maintain the default contact for communications.

Every Intact iQ user-defined field requires a corresponding Acumatica custom field defined in a customization project and published via the Customization Project Editor before data migration runs. Field type translation is required during the mapping phase: Intact iQ date fields map to Acumatica Date fields; numeric fields map to Decimal or Integer fields based on the source precision; text fields map to varchar fields with appropriate length constraints.