Migrate from Ridder iQ to Acumatica

Ridder iQ customer records map to Acumatica Customer DACs. Acumatica supports business account and individual person types — if Ridder iQ stores both, the CustomerClassCD field assigns the correct type. Primary contact details migrate to the Contact sub-tab; additional contacts become related Contact records under the same CustomerID.

Ridder iQ vendor records map to Acumatica Vendor DACs. Acumatica's VendorClassCD assigns a payment terms group that must be configured in Acumatica before vendor records land. Ridder iQ supplier-specific fields (lead time, minimum order quantity) migrate as user-defined fields unless Acumatica's standard Vendor terms fields cover the same data.

Ridder iQ inventory items map to Acumatica Inventory IDs with ItemClassID assignments. Acumatica requires a default warehouse to be set on each Inventory ID — if Ridder iQ stores multiple locations per item, we create one Inventory ID per warehouse in Acumatica and link them via the Warehouse management structure, or consolidate to the primary location and preserve the rest in a custom field.

Ridder iQ BOM structures with material components and routing steps map to Acumatica BOMs with BOM Lines for materials and Operation IDs for routing steps. Acumatica BOMs are versioned — if Ridder iQ stores active and archived BOM versions, we create multiple BOM versions under the same Inventory ID. Phantom BOMs and sub-assemblies require separate BOM records linked as line components.

Ridder iQ production orders map to Acumatica Production Orders with the Production Nbr, status, and warehouse. Open production orders at cutover require a delta window (24–48 hours) to capture any completions or material issues logged during the migration run. Acumatica production order status (Pending, In Process, Completed, Cancelled) maps directly from Ridder iQ status values.

Ridder iQ sales orders map to Acumatica Sales Orders by order number, customer, line items, quantities, and promised dates. Open sales orders transfer with their current statuses; historical closed orders migrate as completed records if reporting continuity is required. Acumatica's order types (CM, RM, DS) need pre-migration configuration to match Ridder iQ's order category assignments.

Ridder iQ purchase orders map to Acumatica Purchase Orders by PO number, vendor, and line items. Open POs transfer with current receipt status. Acumatica's receipt application process (Receipt → AP Bill) means partially received Ridder iQ POs become partially received Acumatica POs with the receipt quantity preserved on the POLines.

Ridder iQ AR invoices map to Acumatica AR Invoices with invoice number, customer, date, description, line items, and amount. Applied payments and credit memos migrate as separate AR Adjustment records linked to the original invoice via the ReferenceNbr. Unapplied credit memos become open AR documents with type CreditMemo in Acumatica.

Ridder iQ AP bills map to Acumatica AP Invoices by vendor, invoice number, date, and line items. Discount terms from Ridder iQ transfer as Acumatica cash discount codes on the AP Invoice. Prepayments and credit memos from vendors migrate as separate AP documents; Ridder iQ payment applications link to Acumatica payment records via the same vendor and invoice reference.

Ridder iQ GL account codes map to Acumatica Account records by account code and description. Active/inactive status carries over. If Ridder iQ uses a segment-based account code structure (e.g., Division-Subaccount), Acumatica's branch and subaccount segments must be configured to receive those values — we map each segment to the corresponding Acumatica dimension.

Ridder iQ contact records map to Acumatica Contacts by name, email, phone, and company association. If a Ridder iQ contact links to a Customer, the ContactRecord's BusinessAccount field references the CustomerID in Acumatica. Multiple contacts per customer are supported in Acumatica; we map each contact individually and preserve the contact's primary-flag from Ridder iQ.

Ridder iQ custom properties on any object map to Acumatica user-defined fields (USR-prefixed fields) created on the corresponding DAC before migration. Each custom property requires a DAC extension in Acumatica — we document the field name, data type, pick-list values, and the DAC it attaches to so your Acumatica admin creates the schema extension before the migration run.

Ridder iQ fixed asset records (asset tag, description, acquisition cost, acquisition date, depreciation method) map to Acumatica Fixed Asset records. Acumatica's asset classes assign default depreciation methods — we map Ridder iQ depreciation codes to the closest Acumatica depreciation method and preserve the asset's net book value and accumulated depreciation as separate fields.

Ridder iQ notes and activity logs on customers, vendors, or orders map to Acumatica Activities with the entity reference preserved. Timestamps and owners carry over. If Ridder iQ stores email threads or call logs linked to contacts, those become Acumatica Activity records with Type='Email' or Type='Phone Call' and the original body preserved in the Details field.