Migrate your ManEx data

Customer records include contact details, account assignments, and address data. Schema is flat and stable; we extract via direct DB query or the platform's native export and map to the destination's account or customer object.

Vendor master data is a distinct entity in ManEx and includes PO history and RMA associations. We preserve the vendor-supplier relationship separately during migration to avoid merging suppliers with customer accounts.

GL accounts are structured with standard types (asset, liability, equity, revenue, expense). We map each account code and type to the destination ERP's chart of accounts, flagging any inactive or suspended accounts for review.

PO records include line items tied to BOMs, vendor assignments, and receiving status. We preserve the full PO lifecycle including partially received orders, handling their status flags explicitly at migration time.

SO records include pricing, customer linkage, and fulfillment status. Multi-price-list pricing on SOs requires value-mapping in the destination, as price list IDs are not portable across ERP systems.

BOMs include multi-level component structures and routing data. Complex multi-level BOMs with phantom assemblies require decomposition during migration; we flatten or preserve hierarchy based on destination system capabilities.

Real-time shop floor data tracks labor time, machine cycles, and material consumption per work order. This transactional data is timestamped and contextual; we map it to destination work order or production records and flag any orphaned transactions not linked to a valid work order.

Inventory quantities, locations, and lot/serial data are extracted from ManEx's materials management module. We handle multiple warehouse locations and on-hand quantities, preserving lot traceability where present.

Open payables and receivables are migrated with their current status, aging buckets, and payment terms. Historical transactions require special handling because ManEx may store them in archived or compressed format depending on the customer's data retention settings.

Time entries from the optional module are tied to employees and work orders. If the destination system has a separate HR module, we map time entries to the corresponding employee records and flag any unlinked entries.

RMAs represent return or repair states tied to original SOs or POs. Their status codes (open, in-progress, closed) require explicit value-mapping because the state machine can differ between source and destination ERPs.

Document attachments stored within ManEx's document management module are not accessible via a public API and may use proprietary formats. We do not migrate attachments directly; instead we flag their existence and advise customers to export them manually or use a separate file-transfer step.