Migrate your Tryton data

Parties are the central master data record in Tryton. We migrate all party types with full address, contact-info, and fiscal-data preservation. Party-specific fields like party categories and accounting receivable/payable accounts are mapped individually.

Sale Quotations and Sale Lines are separate records in Tryton. We preserve state (quotation, confirmed, done, cancelled) and all line-level pricing, taxes, and descriptions. Party link is preserved via party_id foreign key.

Purchase orders follow the same structure as sales orders. We map supplier party references, expected dates, and line-level quantities and prices. States are migrated including confirmed and cancelled orders.

Stock moves track goods from receipt to delivery. We preserve shipment states, warehouse assignments, and quantities. Lot and shipment data is mapped separately with explicit handling for inventory valuation methods.

The account_chart model includes type, parent hierarchy, and tax applicability. We preserve the full account code and name structure and map account_type settings (expense, revenue, receivable, payable, etc.). OHADA-specific account contexts are flagged for manual review.

Analytic accounts in Tryton are stored as a separate axis against moves and invoices. We migrate analytic lines but require explicit mapping of which analytic account model the destination uses, as schema variation between installations is common.

Invoices carry a complex state machine (draft, validated, posted, paid, cancelled) and tax computation caches. We migrate posted and paid invoices fully; draft invoices require additional state validation in the destination.

Project and Work entries in Tryton support hierarchy, status tracking, and time recording. We migrate project work records with their task structure, assigned parties, and durations. Active vs. closed status is preserved at migration time.

Binary attachments are stored as file_id references. We extract attachments from Tryton's ir_attachment table and re-attach them in the destination using bulk file-id mapping. Large attachments are chunked to avoid memory spikes.

Users and employees are separate models with role-based access control. We migrate active users and their employee records but remap group memberships to destination equivalents since access-control schemas differ between ERP platforms.

Financial accounts for payments and cash are migrated with their journal assignments and reconciliation settings. Open AP/AR balances are preserved as move lines linked to the correct party account.

Tryton supports dynamic field extension via ir.model.field and properties. Custom fields added by modules or administrators are migrated as key-value pairs when the destination schema supports custom fields, otherwise we map them to available standard fields.