Migrate from Intact iQ to Microsoft Dynamics 365 Business Central

Intact iQ Customer records hold addresses, price lists, credit limits, and account statuses. We map Customer to Dynamics 365 Account. The primary business address in Intact iQ becomes the primary Address in Dynamics 365; additional addresses (delivery, trade counter, invoice) require consolidation to one address per purpose since Dynamics 365 Finance & Operations permits only one address marked as primary per address purpose. We flag multi-address customers during scoping and resolve the consolidation with the customer's finance team before production migration.

Intact iQ Supplier records include contact details, payment terms, rebate agreements, and procurement history. We map Supplier to Dynamics 365 Vendor. Vendor addresses follow the same primary-address limitation as Customer accounts. Payment terms and rebate agreement codes are stored as custom fields or mapped to vendor groups in Dynamics 365 Finance & Operations.

Contact records in Intact iQ are linked to Customers and Suppliers and hold roles, phone numbers, and email addresses. We preserve the association back to the parent Customer or Supplier via the AccountId or VendorId lookup. Roles (e.g., Accounts Payable, Purchasing, Trade Counter) are stored as custom fields in Dynamics 365. We validate email format and phone number formatting during the transform phase.

Stock Items carry complex relationships: BOM structures, variant codes, reorder levels, and ABC stock categories. Intact iQ's predictive stock management and replenishment rules require us to map not just the stock item but its variant codes and BOM components into Dynamics 365 Supply Chain Management or Business Central product variants and bill of materials. Multi-unit-of-measure setups (eaches, cases, pallets) are preserved in Dynamics 365 unit of measure groups. We flag any stock items that use non-standard ABC categories for manual category mapping in the destination.

Open and historical sales orders are extractable via REST API definition where available, or from the Orders table in direct database extraction. We preserve order line items, pricing, discount structures, and the original order date. Closed orders migrate as historical records; open orders migrate as active orders with the original status preserved and the appropriate order-number prefix assigned during import.

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 in Dynamics 365. Packing slip and product receipt sequences are validated to ensure inventory posting dates align with the original transaction dates in Intact iQ.

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 of accounts before mapping. We flag any mismatched account types or cost-centre hierarchies during the discovery phase and work with the customer's finance team to reconcile the account structure before production migration. GL dimension structures require custom field mapping for cost-centre, department, and project dimensions.

Outstanding invoices and credit notes require careful sequencing. We extract current open items from Intact iQ's aged debtor and creditor reports, map them to Dynamics 365 Finance & Operations or Business Central Customer and Vendor Ledger Entries, and flag any partial payments or credit limits. The open-item migration must complete before the sales and purchase order migration so that account balances are reconciled at cutover. This is the highest-risk financial object in the migration.

Bank accounts, cash accounts, and reconciliation data are accessible via the REST API as defined services or via the Cashbook tables in database extraction. We extract current balances and recent transactions for re-creation at the destination. Bank account codes and currencies are validated against the Dynamics 365 cash and bank management module before import.

User records include roles, branch assignments, and permissions hierarchies. The destination uses a different role model (Dynamics 365 security roles and duty/privilege structure vs. Intact iQ's branch-based access), so we map permissions to the closest equivalent Dynamics 365 security role and flag any permissions that cannot be directly mapped for admin review before migration.

Custom fields added to any standard object in Intact iQ 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 or extension field model. In Dynamics 365 Finance & Ops, custom fields are added via the customization layer or extension fields in Visual Studio; in Business Central, they are created via the field designer in the client. We deliver the full custom field inventory during the discovery phase.

Documents and files attached to Orders, Contacts, or Stock Items are stored in Intact iQ's internal attachment layer and are not exposed via the REST API definition layer. We do not migrate attached documents programmatically. 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 post-migration via SharePoint integration in Dynamics 365.

Workflow rules configured in Intact iQ live in the application layer and are not included in REST API definitions. We document the existing rule set during discovery including triggers, conditions, and actions, and deliver a written rule-rebuild specification for Power Automate or Dynamics 365 workflow configurations. The rebuild itself is a manual task for the customer's admin or a Dynamics 365 partner.

Branch and warehouse assignments on inventory, stock takes, and users require pre-migration validation of the branch structure at both source and destination. Intact iQ's multi-branch model does not map directly to Dynamics 365's legal-entity and operating-unit hierarchy. We resolve mismatched branch hierarchies by building the destination site/warehouse structure before stock data migration and mapping users to the appropriate operating unit or security role.