Migrate from Tyler Enterprise ERP to Odoo ERP

Tyler Fund records define the government fund accounting hierarchy: fund type, fund code, and appropriation controls following GASB standards. There is no native Fund object in Odoo Accounting. We extract fund definitions and ending balances from Tyler, then create Odoo accounts with a custom fund_code__c field and a fund_type__c selection field (General, Special Revenue, Capital Projects, Debt Service, Enterprise) to preserve fund-level reporting in Odoo's financial statements. This mapping must be validated against the government's audit requirements before final import because fund-level segregation is a compliance control.

Tyler GL transactions (journal entries, account balances, and audit timestamps) map to Odoo Account records with journal entry lines. Each Tyler journal entry becomes an Odoo account.move record with debit and credit lines. We preserve the full audit trail—entry date, user attribution, and source module—on the Odoo move'snarration field and in a custom audit_user__c field. Fund code references from Tyler become custom fields on the Odoo account.move record so that fund-level GL can be reconstructed from Odoo's standard financial reporting.

Tyler AP vendor invoices, payment runs, and 1099 classification map to Odoo Vendor Bills (account.move of type in_invoice). We preserve vendor invoice number, invoice date, due date, and line-item detail including amounts and descriptions. 1099 vendor status from Tyler's vendor master migrates to Odoo's Accounting Settings property for 1099 tracking on the vendor contact. Open payables import as unpaid vendor bills; historical closed payables import as posted entries with full payment detail.

Tyler AR transactions, customer billing records, and receipt history map to Odoo Customer Invoices (account.move of type out_invoice). We preserve customer-to-invoice relationships by mapping Tyler AR customers to Odoo Contact records with customer flag enabled, then linking invoices to those contacts. Payment history and receipts import as Odoo account.payment records linked to the corresponding invoices, maintaining the full AR aging trail in Odoo's Follow-up Management.

Tyler budget entries are structured around appropriation periods and funding sources specific to government budgeting cycles—often annual or multi-year with amendment tracking. Odoo does not include a native government budget-to-appropriation module. We extract budget versions, amendment history, and fund-budget-department linkages from Tyler, then either configure Odoo's Budget Management module (available in Odoo Enterprise Accounting) with custom fields for fund_code__c and appropriation_period__c, or document the budget structure in a migration handoff spreadsheet for the customer's Odoo administrator to configure based on their fiscal year setup.

Tyler Position Control tracks staffing at the position level—a funded position exists independently of whether an incumbent occupies it. This is a critical distinction for school district hiring oversight with no direct Odoo equivalent because Odoo HR tracks employees, not positions. We extract position definitions (title, FTE, salary range, funding source, fund code) from Tyler and map them to Odoo Employee records with a custom position_status__c field that can hold Approved/Funded/Unfunded values, or to Odoo IndustryBenefit or Department budget allocations depending on the district's chosen Odoo HR configuration. This mapping requires explicit customer decision during scoping.

Tyler HR records for school districts and municipalities include employee profiles, job classifications, organizational hierarchy, and government-specific job titles. We map Tyler employee records to Odoo Employees with standard fields (name, work email, department, job title, manager) and preserve government-specific job titles and classification codes in custom fields. Salary and compensation history migrate to Odoo HR Payroll if that module is in scope; otherwise we import the most recent compensation record as a custom field on the Employee record.

Tyler vendor master records with 1099 classification, W-9 status, and payment terms map directly to Odoo Contacts with the Vendor checkbox enabled. We map 1099 category codes (NEC, MISC, 1099-K, etc.) from Tyler to Odoo's tax_id and l10n_us_1099_type fields. Payment terms migrate to Odoo's payment.term records with the terms text preserved. Vendor address, phone, and email migrate to the standard Odoo Contact fields. Both active and inactive vendors import to preserve historical AP and purchasing context.

Tyler purchase orders, requisitions, and approval workflow history map to Odoo Purchase Orders (purchase.order). PO header fields (PO number, vendor, date, terms) and line items (product, quantity, unit price, description) migrate directly. Tyler PO approval status migrates to Odoo Purchase Order state (Draft, Sent, PO Locked, Cancelled). We flag any PO with a status that does not map cleanly to Odoo's state model for manual admin review post-migration.

Tyler permits user-defined custom fields across all modules. We inventory every custom field definition during scoping—field name, data type, module association, and any validation rules—and create equivalent custom fields on the corresponding Odoo model (res.partner, account.move, hr.employee, etc.) before any data import begins. Data type translation follows Odoo's field type conventions: date fields become date, decimal amounts become float, and text fields become char or text depending on length.

Tyler's document management stores scanned invoices, contracts, and supporting files. We extract document references and binary attachments where accessible via Tyler's file storage export path and attach them to the corresponding Odoo records (vendor bills, customer invoices, purchase orders, employee records) using Odoo's ir.attachment model. Some legacy Tyler attachments stored in non-standard paths may require manual retrieval; we document any inaccessible files in the migration handoff report for the customer's admin to address.

Tyler maintains comprehensive transaction audit logs across all modules required by government oversight bodies. We extract audit trail records from Tyler's standard reports and attach them as internal notes on the corresponding Odoo records using Odoo's chatter (mail.thread), or store them in a custom audit_log__c text field on the account.move and purchase.order models. The specific audit fields migrated depend on what Tyler's report exports expose; we flag any gap between the exported audit trail and the government's audit requirements during the discovery phase.