Migrate your Proteus E12ERP data

CRM module maps directly to a Customers object. Export is typically available as a delimited file from the web interface. We preserve contact details, company associations, and lifecycle stage where present in the source.

Purchase Order Management implies a Vendors object. We import vendor records with name, contact, and terms fields into the destination's equivalent supplier or vendor object.

Inventory Management module exposes Items with SKU, description, unit cost, and quantity on hand. We map these to the destination item or product catalog, flagging stock quantities separately from item definitions.

Sales Order Management tracks orders linked to Customers and Inventory Items. Order status and line-item pricing require field-level mapping to align with destination order schemas, which vary by ERP.

Purchase Order records include vendor references, line items, and quantities. We match vendor IDs to the destination vendor object and align PO statuses (open, received, closed) to the target system's lifecycle states.

The multi-location module uses Revenue Centers to represent branches or cost centres. This is a non-standard ERP concept. We map Revenue Centers to either departments, locations, or cost centres in the destination depending on what that system exposes.

Financial Management implies a Chart of Accounts. Proteus E12ERP stores account codes and types. We map account structures to the destination coa, preserving account type and currency denomination.

Open invoice state (unpaid purchase orders and outstanding customer invoices) is not explicitly documented as an exportable object in the CSV. We cannot guarantee completeness of open-AP and open-AR records without a confirmed export endpoint and therefore exclude them from standard migration scopes.