Migrate from Tryton to Microsoft Dynamics 365 Business Central

Tryton's Party model is a unified record that can represent a customer, supplier, employee, or any combination. Dynamics 365 splits this into Account (representing the company or organization) and Contact (representing individuals). We split Tryton Parties into Account records (for companies with a VAT/company number) and Contact records (for individuals without a company association), preserving the Party's category roles as Account roles and Contact roles. Address and contact information migrates separately with address purpose flags for invoice vs. delivery in Dynamics 365.

Tryton Sale Quotations map to Microsoft Dynamics 365 Sales Quotes or Sales Orders depending on whether the Tryton quotation was converted to an order. We preserve the quotation state (draft, confirmed, cancelled) and map sale_line records to salesorderline entities with quantity, unit price, tax code, and discount amounts. Party references resolve to Account records created in the first mapping pass.

Tryton Sale Orders map to Microsoft Dynamics 365 Sales Orders with the order state preserved (processing, done, cancelled). Line-level pricing, taxes, and descriptions migrate to salesorderline. If the Tryton order references a product that does not exist in Dynamics 365, we hold the product reference in a staging table for the customer's admin to provision before completing the order import.

Tryton Purchase Orders map to Dynamics 365 Purchase Orders with supplier Party references resolved to Vendor accounts. Expected dates, quantities, and prices migrate with the line structure preserved. States (draft, confirmed, done, cancelled) map to corresponding Purchase Order status values.

Tryton posted invoices map to Microsoft Dynamics 365 Sales Invoice records with invoice number, party, date, and line items preserved. Tax computation caches in Tryton pre-7.0 may be stale; we flag these and trigger a recompute pass post-import. Draft invoices require additional state validation before migration. Invoice payments and reconciliation states map to corresponding Dynamics 365 payment terms and partially paid flags.

Tryton's chart_of_accounts model maps to the Dynamics 365 Chart of Accounts with account type (expense, revenue, receivable, payable, asset) preserved as account categories. For OHADA-configured Tryton instances, we map to the OHADA localization in Dynamics 365 Finance and Operations. The account code and name structure migrates; parent account hierarchy maps to main account structures in Dynamics 365. We recommend configuring the COA in the destination before migration begins.

Tryton stores analytic accounts as a separate axis against moves and invoices. Dynamics 365 Finance and Operations uses financial dimensions (Department, Cost Center, Project, Business Unit) that can be assigned to main accounts or transactions. We merge Tryton's analytic account model into Dynamics 365 financial dimensions, mapping the analytic account type to the appropriate dimension set. Business Central uses Dimension values and Dimension combinations instead.

Tryton products map to Dynamics 365 items with product type (stock, service, non-stock). Stock moves migrate as warehouse journal lines or inventory movements. Lot and shipment data maps separately with explicit handling for inventory valuation. Warehouse assignments from Tryton ship from/ship to locations map to Dynamics 365 warehouse codes.

Tryton Project and Work entries map to Dynamics 365 Projects with task hierarchy, status, and duration preserved. For Finance and Operations, we map to the Project Management and Accounting module; for Business Central, we map to Jobs. Time recording entries migrate as project journal lines with worker references resolved to Dynamics 365 Workers.

Tryton Employee records map to Dynamics 365 Human Resources Workers with employment status, job title, and department preserved. Employee-party links are resolved to the Contact mapping where the employee is also a party contact. HR-specific fields (employment type, start date, compensation) map to the appropriate Human Resources entities.

Financial accounts for payments and cash migrate with their journal assignments. Open AP/AR balances from Tryton move as open ledger entries with move lines linked to the correct party Account and the appropriate receivable or payable G/L account. Bank account details map to Bank Account records with BIC/IBAN preserved.

Tryton stores attachments as Binary fields with file_id references. We extract file content by file_id from ir_attachment and bundle them as a parallel export. In Dynamics 365, we re-attach by matching the original file_id to the newly created record ID via SharePoint integration (Business Central) or the native document handling (Finance and Operations). Large attachments are chunked for upload via the Dynamics 365 file API.

Tryton dynamic fields added via ir.model.field migrate as key-value pairs mapped to Dynamics 365 custom fields. We pre-create the destination custom fields in the target environment before migration, using Dynamics 365 extension fields (AL extension fields for Business Central, custom fields for Finance and Operations). Custom field mapping requires explicit source field identification during scoping.