Migrate from Ridder iQ to Microsoft Dynamics 365 Business Central

Ridder iQ CRM records for customers and prospects map to Business Central Customer and Contact entities, or to the Account and Contact entities if the Microsoft Dynamics 365 Sales CRM module is activated. Ridder iQ's Outlook integration for email and calendar is replaced by the native Microsoft 365 integration in Dynamics 365. We preserve customer credit limits, payment terms, and any CRM-specific fields (industry classification, customer since date) in mapped Business Central Customer fields or custom fields if no standard equivalent exists.

Supplier master records from Ridder iQ map directly to Business Central Vendor. We preserve payment terms, lead times, and any associated purchase history as line-item records in the destination. Supplier-specific contact fields map to Vendor Contact information in Business Central. If the customer uses 3-way matching for purchase invoices, we flag the Vendor posting group assignment for the customer's finance team to configure.

Ridder iQ items covering raw materials, components, and finished goods map to Business Central Item records with the Item Type field set to Inventory, Non-Inventory, or Service based on usage context. Unit of measure, cost, and supplier-link data transfer to the respective Business Central Item Card fields. We flag any items with multiple active unit-of-measure conversions for Business Central's UoM handling review and any items flagged as both manufactured and purchased for BOM variant analysis.

This is the highest-complexity mapping in the migration. Ridder iQ allows each BOM component to be produced or purchased interchangeably, creating multiple valid production paths for the same finished item. Business Central separates production BOMs (manufactured items) from assembly BOMs (kits). We represent each distinct make-or-buy production path as a separate master item with its own Production BOM in Business Central. Items with more than one active BOM variant are flagged for the customer's engineering team to review and confirm the intended production path before the BOM hierarchy is committed. Phantom assemblies in Ridder iQ map to Business Central phantom BOM lines.

Ridder iQ production routings map to Business Central Work Centers and Machine Centers, which combine into Routing records attached to production BOM versions. Each routing step in Ridder iQ becomes a Work Center Operation in Business Central with the same sequence, setup time, and run time values. We validate that the work center capacity unit in Business Central matches the time-tracking unit in Ridder iQ (hours, minutes, or fractions thereof) before committing the routing.

Ridder iQ production orders reference a BOM and routing with scheduled start and end dates, work center assignments, and component allocations. We map production order status (Released, Finished, Cancelled) directly to Business Central Production Order Status. BOM linkage and scheduled quantities transfer to the Production Order Components and Operations lines respectively. Open production orders migrate as Firm Planned or Released in Business Central; closed orders migrate as Finished. Component allocation records in Ridder iQ generate from the BOM at migration time rather than preserving the pre-allocated quantities, which Business Central recalculates on release.

Ridder iQ sales orders spanning the quote-to-invoice lifecycle map to Business Central Sales Order and Sales Line. Customer reference, order dates, and pricing transfer directly. Pre- and post-calculation margin data per line has no standard Business Central equivalent at the line level; we preserve margin values in a custom decimal field on the Sales Line and discuss with the customer whether margin analysis is handled via the Jobs module, Power BI, or a custom extension post-migration. Open orders migrate as open; closed orders migrate as invoiced or as read-only records at the customer's choice.

Ridder iQ purchase orders linking Suppliers and Items map to Business Central Purchase Order. Order quantities, due dates, and supplier references transfer to Purchase Header and Lines. Open POs migrate as open in Business Central and can continue to receive against in the new system. Closed POs migrate as historical records with received quantities preserved if the customer elects to carry historical purchase data. We flag any POs with line items referencing BOM components that have not yet been migrated to prevent orphan references.

Ridder iQ Projects coordinating multi-department ETO workflows (R&D, engineering, purchasing, production phases) with budget, milestone, and cost-tracking data require a scoping decision before mapping. If the customer uses Business Central Jobs, we map project phases to Job Task lines with WIP tracking, milestone dates to Job Planning Lines, and budget data to Job Budget Lines. If the customer's ETO workflow includes resource planning, billing, and advanced project accounting, we recommend evaluating Dynamics 365 Project Operations and document the mapping accordingly rather than forcing ETO complexity into the base Jobs module. Budget and milestone data are preserved in custom Job Task fields or as a documented import specification for the customer's implementation team.

Ridder iQ invoices linked to Sales Orders with payment status tracking map to Business Central Sales Invoice and the corresponding Customer Ledger Entries in the General Ledger. Invoice headers, line items, amounts, and payment reconciliation data transfer to posted invoices or to open entries as appropriate. Historical closed invoices are mapped as read-only posted records in Business Central. We do not re-open or re-post closed invoices; they retain their original posting dates and GL impact as closed periods.

Ridder iQ documents attached to Orders, Projects, Items, and other entities with version history map to Business Central Document Attachments (the standard record-level file attachment feature) or to SharePoint Document Libraries if the customer already uses Microsoft 365 SharePoint. We export file attachments and metadata from Ridder iQ during the file-based export phase. We do not migrate version-diff data or previous revision history; the current revision attaches as the active document. If the customer uses IXON Cloud or IXON Apps for machine data integration, we flag this as an external system that requires a separate integration plan post-migration.

We do not migrate workflows, production scheduling rules, reporting definitions, or document management automations as code. These are platform-specific configuration objects that do not survive direct export between different ERP architectures. We deliver a written inventory of every active Ridder iQ workflow, automation rule, and custom report with its trigger, conditions, actions, and a recommended Business Central equivalent (Job Queue, Workflow, or Report redesign). The customer's admin or a Microsoft partner rebuilds them post-migration as part of the Business Central configuration phase.