Migrate from Tryton to Infor CloudSuite Corporate

Tryton Party records map to Infor CloudSuite Business Partner with full address, contact information, and fiscal data preserved. Party categories in Tryton map to Business Partner groups in Infor. The customer party code becomes the Business Partner ID; the party name becomes the Description field. Multi-address records (Tryton supports multiple delivery and invoice addresses per party) map to Infor's Address Book with address priority flags preserved.

Tryton Sale Quotations map to Infor CloudSuite Quotation with state preservation (quotation, confirmed, done, cancelled) and all line-level pricing, taxes, and descriptions intact. The party reference resolves to the Business Partner ID created from the Party mapping. Lines migrate with product code, quantity, unit, and price, and quoted dates transfer as header-level validity dates.

Tryton Sale Orders map to Infor CloudSuite Industrial Sales Order. Sale Order state (processing, shipped, done, cancelled) migrates with shipment state and line-level fulfilled quantities tracked against the original order lines. If Tryton uses drop-shipment or drop-shipment-invoice patterns, those flags migrate as Infor drop-shipment order types.

Tryton Purchase Orders map to Infor CloudSuite Purchase Order. Supplier party references resolve to Business Partner IDs, and expected dates, line-level quantities, and prices transfer with the purchase state preserved (draft, confirmed, in-receipt, done, cancelled). Tax applicability flags on lines map to Infor's tax jurisdiction assignment.

Tryton Stock Moves track goods from receipt to delivery. We preserve shipment states, warehouse assignments, and quantities. Lot numbers, shipment tracking numbers, and inventory valuation data migrate as separate fields. Warehouse codes in Tryton map to Infor site codes using a pre-built lookup table generated during scoping.

The Tryton account_chart model with account type (expense, revenue, receivable, payable), parent hierarchy, and tax applicability maps directly to Infor CloudSuite's chart of accounts. Account code and name structure is preserved. We flag any accounts that originated from OHADA configuration separately, because OHADA in Tryton uses a different classification scheme that may require manual verification against Infor's account type settings before posting is enabled.

Analytic accounts in Tryton are stored as a separate axis against moves and invoices, supporting multi-dimensional analysis. Infor CloudSuite Industrial represents cost analysis differently depending on the industry template in use. We migrate analytic lines but require explicit mapping during scoping of which Infor cost element or analysis dimension each Tryton analytic account axis maps to, because the axis-to-dimension assignment is customer-specific.

Tryton Invoices carry a complex state machine (draft, validated, posted, paid, cancelled) and tax computation caches that can be stale in older Tryton versions. We migrate posted and paid invoices fully. Draft invoices require additional state validation before import. Post-migration, we trigger Infor CloudSuite's invoice recompute pass and flag any invoices where tax totals deviate from computed amounts by more than a rounding threshold.

Tryton Project and Work entries support hierarchy, status tracking, and time recording. We migrate project work records with their task structure, assigned parties, and durations. Active versus closed project status migrates as Infor project status. If Tryton recorded billable time against project work, those hours transfer to Infor's project work cost logging.

Tryton stores file attachments as Binary fields with a file_id reference, not as inline blobs. We run a pre-export pass that queries ir_attachment, extracts file content by file_id, and bundles attachments as a parallel export set. In Infor CloudSuite, we re-attach by matching the original file_id to the newly created record ID using Infor IDM (Infor Document Management) and Infor OS Content Lifecycle Management.

Financial accounts for payments and cash migrate with their journal assignments and reconciliation settings. Open AP/AR balances are preserved as move lines linked to the correct party account. Bank account numbers and payment method codes map to Infor payment terms and bank account configurations using a lookup table.

Tryton supports dynamic field extension via ir.model.field and properties. Custom fields added by community modules or administrators migrate as key-value pairs where the destination Infor CloudSuite schema supports extended attributes or custom fields. We pre-create the Infor custom field definitions before importing records that carry those values, so that data lands in typed fields rather than notes blocks.