Migrate your Proteus ERP data

Customer records store contact data, buying habits, and referral source information. We extract all customer fields from the database export and map them to the destination system's equivalent contact or account object, preserving any custom fields on the Proteus side.

Vendor master records are included in the standard export. We handle vendor code mapping to avoid collisions when the destination system already has vendor records.

The accounting module uses a structured COA with GST-compliant coding. Account codes may use different segment lengths or naming conventions than the destination; we build a mapping table before writing the import.

Item records include SKU, description, stock levels, pricing tiers, and linked revenue center assignments. We export all item data and handle multi-revenue-center flagging at import time.

Open and historical sales orders carry header-level and line-level data. Line item mapping requires aligning the destination system's product IDs with Proteus item codes.

Purchase orders are tracked with vendor associations and line items. We preserve the PO-to-receive linkage where the destination supports it.

Invoice records include GST/HST data and payment status. Historical invoices may need date-range scoping given export file sizes.

Employee records are part of the employee management module. We export employee data and map it to the destination HR or user object.

E-commerce orders are integrated into the back-end system with inventory sync. We pull order data and line items, then map to the destination order or transaction object.

POS transactions are captured within the same inventory and accounting system. We extract transaction-level data and map it to the destination's sales or receipt records.