Migrate your Iptor ERP data

Iptor uses Business Partner as the unified entity for both customers and vendors. We map this to separate Customer and Vendor objects on the destination, splitting by BP type. Custom fields on the BP record require explicit field-level mapping.

Items in Iptor include configurable attributes, Item Classifications, and multiple unit-of-measure settings. We preserve the item classification hierarchy and map it to the destination's category or attribute system. Pricing tiers on items need separate mapping rules.

Sales Orders are well-structured records in Iptor with line items, pricing, and status. We migrate order headers and lines in a single pass, preserving order numbers and dates. Open vs. fulfilled status is captured so the destination reflects the correct pipeline state.

Purchase Orders export cleanly from Iptor. We handle vendor assignment, line quantities, and expected delivery dates. Partially received POs are migrated with received quantities flagged so the destination can manage remaining receipts.

Iptor generates both AR and AP invoices with associated tax codes and payment terms. We map these to the destination's invoice objects, preserving invoice numbers, dates, amounts, and tax jurisdiction codes. Historical invoices may have attachments that require separate file handling.

Delivery Notes map directly to shipment or fulfillment records. We migrate header and line details including quantities shipped vs. ordered, with a linkage back to the originating Sales Order for audit trail purposes.

We extract open payables and receivables as explicit records at migration time so the destination begins with accurate aged trial balance data. Closed items are migrated as historical records for reporting continuity.

Iptor's account structure uses a configurable segment layout. We map the source segments to the destination's chart, flagging any accounts with non-standard segment assignments for manual review before finalization.

Stock levels, warehouse locations, and lot/serial numbers are migrated as current-state snapshots at go-live. Iptor's multi-warehouse setup requires us to map warehouse codes to destination location records. Perishable or shelf-life data must be explicitly preserved where applicable.

Historical journal entries are migrated for reporting continuity. Iptor supports complex journal types including recurring entries. We preserve the journal date, description, and all debit/credit lines; reversal entries are handled as separate records.

Only present where the Publishing module is active. Royalties and Rights records have complex multi-dimensional structures. We map these to equivalent royalty or rights objects where supported by the destination, otherwise converting them to flat custom records with key fields preserved.

Iptor supports extensive custom field and custom object creation. These are customer-specific and not governed by a stable schema. We document custom field definitions during discovery and propose target-side custom field creation, but we do not migrate the data until the destination schema is confirmed.

User accounts, passwords, and role assignments do not migrate directly due to identity and security constraints. We provide a user mapping table so the customer can reassociate records to new user IDs post-migration. Role definitions are documented for reconstruction.

Documents stored in Iptor's document management system can be exported as file packages. We extract them alongside the related transactional record, package them with folder structure preserved, and deliver them for bulk re-attachment in the destination system.