Migrate your Tranquil ERP data

Account structures are maintained in Tranquil's financial module. We extract the full account hierarchy and map it to the destination's COA, flagging any inactive or duplicate account codes that accumulated in the source system.

Customer records include contact details, transaction history, and payment terms. We migrate customer records 1:1 and preserve open AR balances by linking them to the corresponding invoice records.

Vendor master data carries contact information, bank details, and purchasing history. We map vendor records and reconstruct the accounts payable ledger by linking vendor IDs to open purchase orders and bills.

Items support serial/batch numbers, expiry dates, and multi-unit-of-measure configurations. We map these attributes to the destination's item schema and flag multi-UoM conversions that require unit-ratio logic.

PO records include line items, quantities, supplier links, and status flags. Open POs are migrated with their current status; closed POs are preserved as historical records with a closed flag to prevent reopening.

Sales orders carry customer references, line items, pricing, and fulfillment status. We migrate open orders in full and archive completed orders with their final fulfillment state intact.

Inventory quantities are tracked across warehouses using serial/batch and expiry data. We extract current stock levels, warehouse assignments, and reorder thresholds; the destination's warehouse mapping must be confirmed before writing.

Employee records include personal data, roles, and compensation history maintained in the HR module. We extract the current employee roster and effective-dated compensation fields, mapping them to the destination HR schema.

Custom fields are supported on most business objects. We detect custom field definitions during discovery, map them to destination equivalents, and apply a field-level transformation pass during the load phase.