Migrate your Ridder iQ data

CRM records for customer and prospect data, fully supported. Ridder iQ's CRM integrates with Outlook for email and calendar. We map Contacts to the destination CRM's equivalent entity, preserving email addresses, phone numbers, and any custom address fields.

Supplier master records including contact info, payment terms, and lead times. We preserve the supplier record and any associated purchase history as line-item records in the destination system.

Items cover raw materials, components, and finished goods. Items carry unit-of-measure, cost, and supplier-link data that varies in schema between ERP systems. We flag any multi-UOM items that require conversion at import time.

Ridder iQ stores multi-level BOMs with routing steps. BOMs can be produced or purchased at the component level, which creates branching structures. We map the full BOM tree and flag phantom assemblies that reference other BOMs rather than stockable items.

Production orders reference a BOM and a routing, carrying scheduled start/end dates, work center assignments, and component allocations. We preserve the BOM linkage and scheduled quantities; work center mapping depends on whether the destination ERP uses the same scheduling model.

Sales orders span the quote-to-invoice lifecycle and carry pre- and post-calculation margin data per line. Not all destination ERPs expose margin fields at the order level, so we discuss margin handling with the customer during scoping and land margin data in a custom field where the target schema allows.

Purchase orders link to Suppliers and Items, with order quantities driven by BOM-level demand calculations. We map PO headers and lines, preserving supplier references and due dates. Open POs can be re-imported as active records in the destination system.

Projects in Ridder iQ coordinate multi-department ETO workflows including R&D, engineering, purchasing, and production phases. Projects carry budget, milestone, and cost-tracking data. We map the project structure and phase assignments; downstream phase details are preserved as hierarchical task or phase records where the destination supports them.

Invoices link to Sales Orders and track payment status. We preserve invoice headers, line items, and payment reconciliation records. Historical closed invoices are mapped as read-only records in the destination ERP to maintain audit continuity.

Documents attach to multiple objects (Orders, Projects, Items) and include version history. File attachments and document metadata are exported; we do not migrate version-diff data or previous revision file blobs. Embedded document links are rewritten to point to the destination system's storage path.