Migrate from Tyler Enterprise ERP for Schools to Odoo ERP

Tyler stores account codes as structured fund-org-object strings (e.g., 10-0000-0000-0000) with fund-type classifications (governmental, proprietary, fiduciary) per GASB standards. Odoo uses a flat chart of accounts with optional Analytic Account plan for cost-center tracking. We split Tyler's structured code into Odoo Account (for the GL posting) and Analytic Account (for fund-type classification), preserving the original fund-org-object segments in the account code and name fields. GASB fund-type codes map to a dedicated Analytic Account plan that Odoo finance staff use to generate fund-type reports. Balanced-entry validation from Tyler transfers directly to Odoo's debit/credit enforcement.

Tyler Vendors (name, address, 1099 classification, W-9 status, payment terms, vendor ID) map to Odoo Contacts with the Vendor checkbox enabled. Tyler vendor ID is preserved in an external ID field for reconciliation. We detect duplicate vendors by EIN or name similarity and merge before import, writing a vendor deduplication report that the district finance team approves before load. 1099 classification and W-9 status migrate to Odoo's fiscal information fields on the Contact record.

Tyler AP Invoices (vendor ID, invoice number, invoice date, payment terms, GL distribution lines, approval status) map to Odoo Vendor Bills. Each GL distribution line on the Tyler invoice becomes a separate invoice line in Odoo with the corresponding Odoo account code and analytic account resolved via the chart-of-accounts crosswalk. We flag any invoice with a mismatched or deleted account code and emit a Vendor Bill Reconciliation Report before committing the load.

Tyler AR Invoices (customer ID, invoice number, amount, GL distribution) map to Odoo Customer Invoices. Tyler customer IDs are resolved against the district's employee or parent contact records via a lookup table built during discovery. GL distribution lines map to Odoo account codes and analytic accounts using the chart-of-accounts crosswalk.

Tyler Journal Entries (date, description, debit/credit line amounts, multi-fund split distributions) map directly to Odoo Journal Entries. Tyler enforces balanced-entry validation and Odoo enforces the same, so validation carries over cleanly. Multi-fund split distributions from Tyler become multiple journal lines in Odoo, each tagged with the appropriate analytic account for fund-type reporting. Reversing and adjusting entries migrate with their reversal dates preserved.

Tyler Budget records span fiscal years with appropriation amounts, amendments, and encumbrance carryforwards, stored as separate versioned records with draft/approved status flags. We map Tyler's budget amounts to Odoo's Budget lines (available in Odoo Accounting with the Budget app installed) tied to the corresponding Odoo account and analytic account. Because Tyler's Budget module does not auto-propagate to Payroll, we treat Budget as a standalone import phase sequenced before Employee records and generate a Budget Pre-load Validation Report that flags any account code in the budget without a corresponding Odoo account or analytic account definition.

Tyler Employee records (personal data, job title, FTE, compensation, benefits enrollment, union affiliation, hire/termination dates) map to Odoo Employees. Effective-dated compensation history migrates as a series of Salary Structure BBB (payslip details) records linked to the Employee. Union affiliation and benefits enrollment migrate to Odoo's HR Contracts and Appraisals modules as applicable. FTE from Tyler Position Control maps to the Employee contract's planned_hours field.

Tyler Payroll Batches link to employee records, pay period dates, deduction codes, and GL distribution. Odoo Payroll uses Payslip records organized under a Payslip Batch for a given pay period. We export Tyler payroll batches as Odoo payslip batches with individual payslips linked to the corresponding Employee. Deduction codes from Tyler (federal tax, state tax, retirement contributions, benefit deductions) map to Odoo's salary rule structure, which must be configured during the Odoo HR module setup before migration. We generate a Payroll Pre-load Validation Report that cross-references every employee in the payroll export against their time entry records and flags any missing links.

Tyler Time and Attendance entries (employee ID, date, hours worked, pay type, approval status) map to Odoo Timesheets. Tyler's Advanced Scheduling shift assignments migrate as separate timesheet lines with the project/task context set to the scheduling reference. Approved time entries migrate with their approval status preserved; pending entries are flagged for the district to approve in Odoo before the next payroll run.

Tyler Position Control records define FTE allocations, position budget amounts, and the link between a funded position and its incumbent employee. We map Position Control to Odoo Job Positions linked to the corresponding Employee via the Employee's contract. Position budget amounts migrate as reference data in the Odoo contract's wage field and as analytic account entries tied to the position's cost-center budget line.

Tyler Purchase Orders (vendor ID, line items with quantities and unit costs, GL distribution per line, approval workflow status, encumbrance flags) map to Odoo Purchase Orders. Encumbrance balances from Tyler migrate as Odoo purchase order amounts in draft state, with the GL distribution per line resolved via the chart-of-accounts crosswalk. Open POs with partial receipts migrate with their received quantity preserved and a backorder flagged for the district to resolve in Odoo.

Tyler Student Activity Fund management is a separate subsystem with its own fund codes and approval workflows that does not share the same numbering convention as the district's main General Ledger. We export all Student Activity Fund balances as standalone journal entries in Odoo, tagged with a dedicated analytic account for activity fund reporting. We build a crosswalk between Tyler activity fund codes and the district's primary chart of accounts during discovery, so that activity fund transactions can be rolled up into district-wide fund-type reports in Odoo without duplicating account codes. This is one of the highest-risk mappings in a K-12-to-Odoo migration and requires explicit sign-off from the district's finance team on the crosswalk design before any data loads.