Pre-built Tyler data conversion for Munis, Eden, Energov, iNovah and Courts. MSSQL extractors, ORG/OBJ/PROJ to six-segment COA crosswalks, position-control preservation, encumbrance carryover, FBDI/HDL emitters, row-level reconciliation. Audit-ready evidence at every load.
The hard part isn't pulling rows from SQL Server. It's translating Munis fund accounting, position control and encumbrance balances into Fusion Public Sector Financials without breaking the GASB chain or the ACFR comparative-year continuity.
Tyler Munis, the dominant US local-government ERP, presents a data model built around the ORG/OBJ/PROJ chartfield (with embedded fund logic), position-control tables tied to budget appropriations, encumbrance balances tracked at PO-line granularity, and a long tail of agency-specific configurations covering tax billing, utility billing, building permits and code enforcement. Oracle Fusion Public Sector Financials uses a different shape — an explicit six-segment COA with Fund as a named segment, Fusion HCM Position Management for position tracking, and Fusion Procurement encumbrance accounting tied to the budgetary ledger.
Every tyler technologies data migration to Oracle Fusion has to bridge those gaps without breaking the GASB-compliant audit chain that links a fund-level ACFR statement back to its supporting GL journal, vendor voucher and contract document. Custom MSSQL clients and one-off PL/SQL conversion routines can do it — but every domain becomes a multi-week negotiation between finance, HR, budget office and the external auditor. Syntra ETL replaces that with pre-built crosswalks refined across dozens of Tyler conversions.
The same engine handles three deployment scenarios: full Tyler replacement (Munis + Energov + iNovah → Fusion Public Sector), Munis-only migration with Energov and iNovah kept for domain-specific operations (with daily AR/GL feeds to Fusion), and the consolidation pattern where multiple Tyler tenants across departments roll up into a single Fusion ledger with cross-department fund accounting.
The transformations Syntra ETL ships pre-built. No custom MSSQL scaffolding, no multi-month bespoke conversion development.
Every active Munis chartfield combination walked, fund/department/program/activity meaning extracted from actual journal patterns, and routed to a clean Fusion six-segment COA with Fund as explicit segment. Finance and external auditor sign-off built into the workflow.
Open encumbrances captured at cutover snapshot, validated against source appropriations and contract documents, re-established in Fusion Procurement at PO-line and funding-string level. Budget capacity preserved without double-counting.
Every Munis position, step/grade, union code, civil-service class and retirement-plan eligibility migrated to Fusion HCM Position Management with position-to-funding-string intact for encumbrance accounting continuity.
Vendor 1099 history (NEC, MISC, INT, DIV) carried forward with year-by-year totals reconciled to Fusion's 1099 reporting. First post-migration 1099 cycle runs without manual reconciliation.
Permit issuance, plan-review fees, inspection fees and business-license renewals routed from Energov to Fusion AR with revenue recognition aligned to GASB modified-accrual basis.
Odyssey case financial obligations (fines, fees, restitution) translated to Fusion AR with case-cross-reference preserved for ongoing collections through court-clerk back-office.
A repeatable load order that respects Fusion Public Sector Financials' data dependencies. Skip a step and your GL load fails on missing funds or your position-control fails on missing union codes.
Fusion enterprise structures, ledgers, BUs, six-segment COA with Fund as named segment, fiscal calendar matching agency fiscal year, budgetary controls enabled, encumbrance accounting enabled. Loaded via FSM tasks — not user-facing data, but everything downstream depends on it.
Funds, departments, programs, grants, vendors, suppliers, customer master, civil-service job codes, union codes, step/grade tables, retirement plan eligibility codes. Loaded in dependency order via FBDI/HDL — funds before journals, jobs before positions, positions before workers.
HDL Worker.dat loads first, HDL Position.dat second with position-to-funding-string intact, HDL Payroll Element Entries for historical earnings (configurable depth: typical agencies load current FY + prior FY full detail, older as summary).
GL trial balance by fund loaded as opening balances. Historical journals loaded for current FY + prior FY (configurable depth). Reconciled at fund-level to the cent against Munis source. External auditor walkthrough.
Open AP vouchers, open AR invoices, fixed-asset register with depreciation schedule, open encumbrances and active POs, current FY budget appropriations — loaded as open items ready for transaction continuation.
Final delta replay, parallel monthly close (Munis + Fusion), reconciliation pack issued (trial balance by fund, 1099 totals, position FTE, encumbrance balance — Munis vs Fusion to the cent). Finance, budget office and external auditor sign-off. Production cut to Fusion.
Every Tyler data migration to Oracle Fusion concludes with a signed evidence pack designed for the first post-migration ACFR audit cycle.
Munis trial balance by fund vs Fusion trial balance by fund, to the cent, for every fiscal year migrated. Variance investigation report attached for any non-zero variance.
Vendor year-totals by 1099 box (NEC, MISC, INT, DIV) — Munis vendor master vs Fusion supplier master — with mapping crosswalk and IRS-ready substantiation.
Authorized headcount and budgeted FTE by department/fund — Munis Position Control vs Fusion HCM Position Management — proving union-negotiated headcount preserved.
Open encumbrance balance by appropriation — Munis encumbrance ledger vs Fusion PO commitment ledger — proving no budget capacity lost or duplicated.
Current FY budget appropriations and YTD actuals — Munis vs Fusion — proving budget-to-actual reporting continuity for Council/Board reporting.
GASB 34 government-wide + fund-level continuity, GASB 87 lease schedule preservation, GASB 96 SBITA preservation — signed by Syntra ETL and countersigned by the external auditor.
Tyler Technologies data migration is the process of moving general ledger journals, AP vouchers and 1099 history, AR invoices and aging, cash receipts, fixed-asset registers, budget appropriations, encumbrance balances, workers and positions, payroll history, permit and inspection records, cashiering and payment data, and court-case financial obligations from your Tyler Munis, Eden, Energov, iNovah and Courts Odyssey tenants into Oracle Fusion Public Sector Financials and HCM. The technical heart is structured extraction through Tyler's MSSQL databases (or the iSeries-resident Munis tenants), governed crosswalks for ORG/OBJ/PROJ to Fusion six-segment COA, position-control and step/grade preservation, and Oracle-validated FBDI/HDL payloads. Syntra ETL handles every step with pre-built Tyler extractors and fund-accounting-aware transformations.
The terms get used interchangeably, but the distinction is useful: migration is the end-to-end project (extract + transform + load + reconcile + cutover), while conversion is the transformation layer specifically. Syntra ETL's Tyler data conversion engine ships pre-built rules for ORG/OBJ/PROJ to Fusion COA segment routing, fund-code classification (General Fund, Special Revenue, Capital Projects, Enterprise, Internal Service), step/grade-to-Fusion-grade-rate mapping, union-code preservation, encumbrance carryover, permit-to-cash recognition and court-case-AR translation. These are rules that on a consultant-led project would otherwise eat 4–6 months of bespoke SQL and PL/SQL development. Syntra ETL ships them refined across dozens of Tyler conversions across counties, cities, school districts and special districts.
Munis uses a hierarchical ORG/OBJ/PROJ chartfield design with embedded fund logic — a single ORG code can carry fund + department + program + activity meaning depending on the agency's setup conventions. Fusion Public Sector Financials uses an explicit six-segment COA with Fund as a named segment. Syntra ETL's Tyler converter walks every active ORG/OBJ/PROJ combination in the source Munis instance, identifies the embedded fund/department/program/activity meaning by analyzing actual journal entries and ledger balances, and proposes a clean six-segment Fusion COA: Fund, Department, Program/Activity, Grant, Object, Future. Finance leadership and the external auditor sign off on the crosswalk before any load runs. The migration preserves every historical balance and ties them to the new COA so the comparative-year ACFR continues to balance.
Yes — and it's table-stakes for any government finance go-live. Open encumbrances (open POs against current-year appropriations) are mid-year sacred: they consume budget capacity and need to land in Fusion exactly as they sat in Munis. Syntra ETL captures every open encumbrance at cutover snapshot, validates each against the source appropriation and contract document, and re-establishes them in Fusion Procurement at the PO line and funding-string level. Budget appropriations for the current fiscal year (original, amendments, transfers) migrate to Fusion Public Sector Budgeting with full Council/Board approval trail preserved. Year-end carry-forward processing (typical for capital projects and grant-funded programs) runs through Fusion's encumbrance accounting from day one.
Syntra ETL emits Fusion-native load formats for every Tyler data domain: FBDI GL Journal Entry Import for historical journals and trial balance load; FBDI AP Invoice Import for vendor history and 1099 substantiation; FBDI AR Invoice Import for receivable history; FBDI Fixed Asset Mass Additions for the asset register with depreciation history; FBDI Budget Import for appropriations; FBDI PO Import for open encumbrances; HDL Worker.dat and HDL Position.dat for HCM payloads; HDL Payroll Element Entries for historical earnings; and REST API payloads for incremental delta loads during parallel-run. Every payload is validated against the current Oracle Fusion 26x release schema before submission, so validation errors surface locally — not in a 4-hour Fusion ESS job that fails on row 47,000 with a fund-code violation.
Every record extracted from Tyler is hashed at the source (header hash + line hashes + funding-string hashes). Every record loaded into Fusion is re-hashed post-load. The reconciliation engine compares counts (journals, vouchers, invoices, assets, positions), sum totals (debit/credit by fund, appropriation balance by department, vendor 1099-year totals, position FTE by union) and hash signatures per fiscal year per fund. Any record that fails Fusion validation is captured with the exact field-level reason ready for bulk fix. Output is a signed timestamped reconciliation pack: Munis trial balance by fund vs Fusion trial balance by fund to the cent, vendor 1099 totals vs Fusion 1099 reporting, position-FTE vs Fusion HCM position headcount, encumbrance balance by appropriation vs Fusion PO commitment. External auditor signs off on the pack directly for the first post-migration ACFR cycle.
Yes. After the initial bulk load, Syntra ETL captures Tyler deltas via MSSQL change-data-capture (or modified-since watermarks on each domain) and replays them into Fusion through REST APIs. This supports the standard parallel-run pattern for government finance: Tyler Munis continues taking transactions for 1–2 monthly close cycles while Fusion is validated to the cent by fund. Payroll runs in parallel for 2 bi-weekly cycles. Permits continue issuing in Energov, with summarized AR streamed daily to Fusion. Once finance, budget office, HR and external audit sign off, new transactions cut to Fusion and the Munis tenant moves to read-only archive mode.
GASB compliance is non-negotiable for public sector finance and the single most common reason migrations get audit-questioned. GASB 34 requires both government-wide and fund-level reporting — Syntra ETL's Tyler conversion preserves both views by mapping Munis fund rollups to Fusion fund-segment values and configuring the Fusion ledger structure for dual-reporting. GASB 87 lease liabilities tracked in Munis Lease module migrate to Fusion Lease Accounting with right-of-use asset and liability schedules intact. GASB 96 SBITA (subscription-based IT arrangements) obligations migrate with payment schedules, term-end disclosure data and discount rates preserved. The first post-migration ACFR includes a sign-off note confirming GASB continuity, which the external auditor uses for the migration-year opinion.
Book a 30-minute conversion strategy call. We'll review your Munis ORG/OBJ/PROJ structure, fund rollups, position-control profile, open encumbrance volume and external auditor expectations — and walk you through the exact reconciliation pack your migration will produce.