Migrate your Intact iQ data

Customer records in Intact iQ hold addresses, price lists, credit limits, and account statuses. The REST API exposes Customer as a defined service with read/write access, allowing us to extract and load customer data with standard field mapping to most destination CRMs.

Supplier records include contact details, payment terms, rebate agreements, and procurement history. We map Supplier records directly into the destination's equivalent vendor or supplier object using the API's defined service layer.

Contact records are linked to Customers and Suppliers and hold roles, phone numbers, and email addresses. The API permits read/write access to contact data, and we preserve the association back to the parent account during migration.

Stock Items carry complex relationships: BOM structures, variant codes, reorder levels, and ABC categories. Intact iQ's predictive stock management and replenishment rules require us to map not just the item record but also the replenishment configuration, which varies by customer setup.

Open and historical sales orders are extractable via the REST API as a defined service. We preserve order line items, pricing, and discount structures. Closed orders can be migrated as historical records depending on the destination schema.

Purchase order records include supplier references, expected delivery dates, and line-level item assignments. We extract the full PO lifecycle from draft through to receipt and close the records appropriately at the destination.

Chart of Accounts records carry account codes, types, and cost-centre assignments. The account code structure varies between Intact iQ configurations, so we validate the destination's chart before mapping and flag any mismatches in account type or currency assignment.

Outstanding invoices and credit notes require careful sequencing — we extract current open items, map them to the destination's receivable or payable ledgers, and flag any partial payments or credit allocations that may not transfer cleanly.

User records include roles, branch assignments, and permissions hierarchies. The destination may use a different role model, so we map permissions to the closest equivalent and flag any permissions that cannot be replicated.

Document storage in Intact iQ uses an internal attachment layer that is not exposed via the standard REST API definition. We do not migrate attached documents. We recommend exporting them separately and re-attaching post-migration.

Intact iQ workflow rules are defined in the application layer and are not portable via the REST API. We document the existing rule set during discovery and provide a rule-rebuild guide for the destination system.

Custom fields added to any standard object are stored in the database but require manual field mapping during migration scoping. We identify all custom field names and data types pre-extraction and map them to the destination's custom field schema.

Branch and warehouse assignments on inventory, stock takes, and users require pre-migration validation of the branch structure at both source and destination. Mismatched branch hierarchies are resolved during the mapping phase.

Bank accounts, cash accounts, and reconciliation data are accessible via the REST API as defined services. We extract current balances and recent transactions for re-creation at the destination.