TYLER TECHNOLOGIES ETL CONNECTOR

    Tyler Technologies ETL Connector — Pre-Built, Fund-Accounting-Aware, CJIS-Compliant

    The pre-built Tyler Technologies ETL connector covering every Tyler product: Munis, Eden, Tyler Enterprise ERP, iNovah, Energov / Tyler Civic Pro, Brazos, Odyssey, Enterprise Justice, Eagle, MicroPact, MyCivic, Socrata. Fund-accounting decoder, CJIS-compliant Courts partition, FBDI / HDL Oracle Fusion targets, OIC state-reporting replacement — first extract in week one.

    3,400+
    Munis tables understood
    Week 1
    First extract in days, not months
    CJIS 5.9
    Built in, not bolted on
    Quarterly
    Release cadence with Tyler + Fusion

    Why a purpose-built Tyler Technologies ETL connector beats a generic ETL tool every time

    Generic ETL tools give you SQL Server connectivity. The Tyler Technologies ETL connector gives you fund accounting, position control, CJIS compliance, GASB reporting, Courts case-financial-obligations and the FBDI / HDL Oracle Fusion target out of the box.

    Tyler Technologies is the dominant US state/local government software vendor with 35%+ market share across counties and municipalities, ~14,000 jurisdictions on Munis alone, and the largest US court system running on Odyssey. The Tyler product surface is enormous: Munis ERP (Financials, HR, Payroll, Tax Billing, Utility Billing, Permits, Inspections), Eden Financials, Tyler Enterprise ERP, iNovah Cashiering, Energov / Tyler Civic Pro suite, Brazos public safety RMS, Courts Odyssey and Enterprise Justice, Eagle recorder, MicroPact entellitrak case management, MyCivic citizen portal, Socrata open-data portal, NIC state digital government and payment processing, Tyler Notify civic engagement.

    Generic ETL tools (Informatica, Talend, MuleSoft, Boomi) connect to Tyler's SQL Server schemas and Azure REST APIs — and then you build everything else yourself: fund-accounting decoders, position-control mappers, Courts case-financial-obligation extractors, CJIS-compliant partitions, GRRS retention taggers, FBDI / HDL payload generators, OIC state-reporting replacements, CAFR/ACFR statement rebuilds. The build-it-yourself path consumes 6–12 months and an army of consultants — and the resulting code is yours to maintain forever.

    The Tyler Technologies ETL connector inverts that economics. The connector ships every Tyler-specific capability as configuration — not as code your team writes from scratch. First extract lands in week one of any Tyler-to-Fusion programme, the migration assessment lands in week four, the data mapping deliverable lands in week six, and the cutover lands in 16–24 weeks instead of the 12–18 months a consultant-led programme typically consumes. Quarterly release cadence keeps the connector current with Tyler product releases and Oracle Fusion quarterly updates. Customer-facing release notes document every change with the configuration impact.

    What the Tyler Technologies ETL connector ships

    1
    Pre-built source extractors
    Munis (3,400+ tables), Energov (900+ endpoints), iNovah (400+ tables), Odyssey (1,800+ tables), Tyler admin extracts. SQL Server, Azure SQL, IBM i / DB2, REST APIs.
    2
    Fund-accounting decoder
    ORG/OBJ/PROJ to Fusion six-segment COA. GASB 34/68/87/96 compliance. CAFR/ACFR statement templates for Fusion BI Publisher to GFOA Award standards.
    3
    CJIS-compliant Courts partition
    AES-256 encryption, MFA, role separation, immutable access log, quarterly access certification, FedRAMP-aligned. Sealed/juvenile partitions with expungement-aware access.
    4
    FBDI / HDL Fusion targets
    Oracle Fusion Public Sector Financials, HCM, CX, Grants Management. OIC state-reporting integration replacement for PERS, TCEQ, TWC, EDD, NYSLRS, federal SEFA.

    Six characteristics that distinguish the Tyler Technologies ETL connector from a generic ETL tool

    The capabilities counties and cities discover they need in week one of a Tyler-to-Fusion migration — and that the Tyler Technologies ETL connector ships out of the box.

    🏛️

    Fund-accounting decoder

    Walks every Munis ORG/OBJ/PROJ combination, decodes embedded fund logic, produces Fusion six-segment COA crosswalk with explicit Fund segment. GASB 34 fund-level + government-wide reconciliation.

    👥

    Position-control mapper

    Every active and frozen Munis position, step/grade, union code, civil service class, FLSA status, retirement plan mapped to Fusion HCM Position Management with funding-string preserved.

    ⚖️

    Courts + CJIS partition

    CJIS-compliant partition design with AES-256, MFA, role separation, immutable access log, quarterly access certification. Sealed/juvenile partitions with expungement-aware access rules.

    📊

    CAFR/ACFR templates

    Fusion BI Publisher CAFR/ACFR statement templates rebuilt to GFOA Award standards. Statement of Net Position, Statement of Activities, Fund-level statements, notes, RSI, MD&A.

    🌐

    OIC state-reporting

    Replaces every Tyler-native state-system interface (PERS, TCEQ, TWC, EDD, NYSLRS, state tax-warrant filings, federal SEFA) with a Fusion-native OIC equivalent.

    📦

    FBDI / HDL Fusion targets

    Every loaded object FBDI / HDL template-compliant for the in-scope Fusion release. GL, AP, AR, Cash, Fixed Assets, Purchasing, Budgeting, Worker, Position, Grade, Step, Union Assignment.

    The Tyler Technologies ETL connector deployment lifecycle

    From read-only credentials provisioning to first extract to production cutover — a structured, repeatable deployment lifecycle that lands the Tyler Technologies ETL connector in production inside 16–24 weeks for a typical mid-sized county.

    1

    Read-only credentials provisioned — Week 1

    Read-only SQL Server logins (Munis, Eden, iNovah, Energov), Azure API keys (Energov, Tyler Civic Pro), Odyssey case-data access, Tyler admin extracts. Scoped permissions, no schema changes. Throttled to off-peak query windows.

    2

    First extract + catalogue — Week 1 end

    Tyler Technologies ETL connector self-discovers active Munis ORG/OBJ/PROJ combinations, active positions, active Energov record-types, active Odyssey case-types, active iNovah POS configurations, active Crystal Reports / Tyler Reporter reports. Catalogue delivered.

    3

    Migration assessment — Weeks 2–6

    Pre-built Tyler discovery feeds migration assessment: fund-accounting crosswalk strawman, GASB compliance map, CJIS partitioning plan, position-control mapping, sized roadmap with risk register. Signed by CFO, Clerk, CIO, external auditor.

    4

    Data mapping deliverable — Weeks 4–10

    Row-level crosswalk: every ORG/OBJ/PROJ to Fusion six-segment COA, every position to HCM Position Management, every Odyssey case-type to Fusion AR with CJIS partition, every state-reporting integration to OIC. Seven sign-offs before extract.

    5

    Extract + validation + reconciliation — Weeks 8–20

    Tyler Technologies ETL connector executes full extract, validation, reconciliation across all seven reconciliation domains. CJIS partition activated. State-reporting OIC integrations tested. Citizen Self-Service portal cutover prepared.

    6

    Cutover + parallel-run + steady-state — Weeks 16–24+

    Choreographed cutover. CJIS partition active. State-reporting OIC integrations live. Citizen Self-Service DNS redirects active. Parallel-run for 2–3 months. Tyler Technologies ETL connector operates as steady-state Oracle Fusion integration.

    What ships with the Tyler Technologies ETL connector platform

    A productised, version-pinned, quarterly-released ETL platform with every Tyler-specific capability counties and cities need for a Tyler-to-Fusion migration and the subsequent steady-state operating model.

    🔌

    Pre-built source extractors

    Munis (3,400+ tables) MSSQL, Energov (900+ endpoints) Azure REST, iNovah (400+ tables), Odyssey (1,800+ tables), Eagle, Brazos, MicroPact, MyCivic, Socrata, NIC, Tyler admin extracts.

    📋

    Configuration-driven mappings

    Fund-accounting decoder, position-control mapper, Courts CJIS partition, GRRS retention tagger — all configuration, no custom code. Customer owns the configuration.

    📦

    FBDI / HDL target loaders

    Oracle Fusion Public Sector Financials (FBDI), HCM (HDL), CX (REST), Grants Management. Every loaded object FBDI / HDL template-compliant for the in-scope Fusion release.

    🌐

    OIC integration designs

    State-reporting integrations (PERS, TCEQ, TWC, EDD, NYSLRS, federal SEFA), Courts Odyssey-to-Fusion AR, iNovah-to-Fusion AR, Energov-to-Fusion AR, Citizen Self-Service-to-Fusion AR.

    🛡️

    CJIS-compliant archive

    AES-256, MFA, role separation, immutable access log, quarterly access certification, FedRAMP-aligned. Sealed/juvenile partitions with expungement-aware access.

    📚

    Quarterly release notes

    Customer-facing release notes per quarter documenting every Tyler-side and Fusion-side change with connector configuration impact and recommended migration timing. Version-pinned for existing migrations.

    Frequently asked questions

    What is the Tyler Technologies ETL connector and what does it cover out of the box?+

    The Tyler Technologies ETL connector is the pre-built, configuration-driven, fund-accounting-aware extraction and loading platform that handles every Tyler product county and city customers commonly run: Munis ERP (Financials, HR, Payroll, Tax Billing, Utility Billing, Permits, Inspections), Eden Financials, Tyler Enterprise ERP, iNovah Cashiering, Energov / Tyler Civic Pro suite (permits, licensing, code enforcement), Brazos public safety RMS, Courts Odyssey and Enterprise Justice, Eagle recorder / land records, MicroPact entellitrak case management, MyCivic citizen portal and Socrata open-data portal. The Tyler Technologies ETL connector ships with row-level Munis MSSQL schemas (3,400+ tables), Energov Azure REST APIs (900+ endpoints), iNovah extracts (400+ tables), Odyssey case-data schemas (1,800+ tables) and Tyler admin extracts for Crystal Reports, Tyler Reporter, workflow definitions and role/permission catalogs.

    How does the Tyler Technologies ETL connector differ from a generic ERP ETL tool?+

    Generic ERP ETL tools (Informatica, Talend, MuleSoft, Boomi) treat Tyler as a SQL Server tenant with a schema browser — you get connectivity but you build everything else yourself: the fund-accounting decoder for Munis ORG/OBJ/PROJ chartfields, the position-control mapper for Munis Position Management, the Courts case-financial-obligation extractor for Odyssey, the Energov record-type catalog crawler, the iNovah daily deposit-ticket reconciler, the CJIS-compliant partition for sealed/juvenile case data, the GRRS retention tagger, the FBDI / HDL payload generator for Oracle Fusion Public Sector Financials and HCM, the state-reporting integration replacement for PERS / TCEQ / TWC / EDD / NYSLRS. The Tyler Technologies ETL connector ships every one of those capabilities as configuration — not as code your team writes from scratch.

    What Tyler source systems does the Tyler Technologies ETL connector read from?+

    The Tyler Technologies ETL connector reads from every common Tyler source-system technology: SQL Server (Munis, Eden, iNovah, Energov on-prem and Tyler-hosted), Azure SQL Database (Energov on Tyler Cloud), Azure Blob Storage (Energov attached binaries, Citizen Self-Service documents), IBM i / DB2 (legacy Munis tenants on the iSeries lineage, older Eden tenants), Odyssey case-data warehouse extracts, Tyler-hosted REST APIs (where Tyler exposes them — Energov, Tyler Civic Pro, MyCivic, Socrata, NIC payment-processing), Tyler admin CSV exports (Crystal Reports inventory, Tyler Reporter inventory, workflow configuration, role/permission catalog), and Tyler Disaster Recovery Service backup extracts for tenants where direct-database access is not available. Every source-system read is throttled to respect Tyler's recommended off-peak query windows.

    What target systems does the Tyler Technologies ETL connector load to?+

    The Tyler Technologies ETL connector loads to Oracle Fusion Public Sector Financials (FBDI for GL, AP, AR, Cash Management, Fixed Assets, Purchasing, Budgeting), Oracle Fusion HCM (HDL for Worker, Position, Grade, Step, Union Assignment, FLSA Status, Retirement Plan Eligibility), Oracle Fusion CX (REST-based for case management where applicable), Oracle Grants Management (for federal grant project-cost tie-out), Oracle BI Publisher (CAFR/ACFR statement templates rebuilt to GFOA Award standards), Oracle OIC (integration design replacing every Tyler-native state-system interface), CJIS-compliant Parquet archive partitions on county-controlled object storage (for compliance archive, legacy data access, decommissioning evidence), and Citizen Self-Service portal payment-gateway integration (MuniciPay, Square Government, Stripe Government, NIC payment-processing). Every target-system load is FBDI / HDL template-compliant for the in-scope Fusion release.

    How does the Tyler Technologies ETL connector handle fund accounting and GASB compliance?+

    Fund accounting and GASB compliance are the defining features of the Tyler Technologies ETL connector versus any generic ETL tool. The connector ships with a fund-accounting decoder that walks every active ORG/OBJ/PROJ chartfield combination in Munis (or every Eden fund/department/account string), decodes the embedded fund logic against the state Uniform Chart of Accounts and the local fund-numbering convention, and produces a Fusion Public Sector Financials six-segment COA crosswalk with explicit Fund segment. GASB 34 fund-level + government-wide reconciliation, GASB 68 pension reporting, GASB 87 lease accounting, GASB 96 SBITA accounting, GASB 100 accounting changes and GASB 101 compensated absences each get configuration support. CAFR/ACFR statement rebuild templates ship for Fusion BI Publisher to GFOA Award standards.

    Does the Tyler Technologies ETL connector handle CJIS-scoped Courts data?+

    Yes — and CJIS compliance is built into the Tyler Technologies ETL connector, not bolted on as an after-thought. The connector ships with a CJIS-compliant partition design for Courts Odyssey case data, sealed and juvenile record partitions with expungement-aware access rules, AES-256 encryption-at-rest with FIPS 140-2 validated modules, MFA + smart-card or equivalent advanced authentication, role-based access control with documented separation of duties, immutable access logging with quarterly access certification commitments, FedRAMP-aligned data residency on US cloud regions, documented incident-response plan, and physical security controls on the underlying object storage region. The annual FBI CJIS audit and any state-level CJIS audit pulls the evidence pack directly from the Tyler Technologies ETL connector configuration.

    How quickly can the Tyler Technologies ETL connector get to first extract?+

    First extract on the Tyler Technologies ETL connector lands in week one of any Tyler-to-Fusion programme — typically within 5 business days of read-only SQL Server credentials being provisioned. The connector self-discovers active Munis ORG/OBJ/PROJ combinations, active positions in Munis HR/Payroll, active Energov record-types, active Odyssey case-types, active iNovah POS configurations and active Crystal Reports / Tyler Reporter reports. The first extract delivers a complete catalogue of every Tyler object in scope, every fund-level rollup, every position by union, every case-type by court division and every state-reporting integration. The catalogue feeds the migration assessment, the data mapping deliverable, the cutover strategy and the steady-state operating model. Most Tyler-to-Fusion programmes consume a quarter on inventory before the Tyler Technologies ETL connector lands the catalogue in week one.

    Who maintains the Tyler Technologies ETL connector — the connector itself, not the customer project?+

    Syntra ETL maintains the Tyler Technologies ETL connector as a productised platform with quarterly release cadence aligned to Tyler product release notes and Oracle Fusion quarterly updates. Every new Munis release (typically 11.x semi-annual update cadence), every new Energov release, every Tyler-side schema change, every Oracle Fusion FBDI / HDL template change is incorporated into the connector with quarterly customer-facing release notes. The Tyler Technologies ETL connector ships with version-pinning so existing customer migrations are not disrupted by upstream changes. The customer-facing release notes document every Tyler-side and Fusion-side change with the connector configuration impact and the recommended migration timing. The Tyler Technologies ETL connector is the customer's platform for Tyler-to-Fusion migration; Syntra ETL's job is to keep it current.

    Ready to evaluate the Tyler Technologies ETL connector?

    Book a 30-minute discovery call. We'll walk through your Tyler product footprint (Munis, Eden, iNovah, Energov, Brazos, Odyssey), your Oracle Fusion scope (Financials, HCM, CX, Grants Management), your CJIS requirements, your state-reporting portfolio and your migration timeline — and demonstrate a Tyler Technologies ETL connector first extract against your environment inside a week.