Migrate from Tyler Enterprise ERP for Schools to Infor CloudSuite Corporate

Tyler stores account codes as structured fund-org-object-project strings following government fund-accounting conventions with fund-type codes (governmental, proprietary, fiduciary). Infor CloudSuite Financials uses a configurable multi-segment GL where each segment maps to a dimension. We extract the full Tyler account code table, map each fund-org-object-project segment to the corresponding Infor GL segment structure, and preserve GASB-compliant fund-type classifications as Infor fund-dimension values. Account code validation rules and fiscal-year status flags migrate as Infor account business rules. The mapping output is a segment crosswalk table that the district's Infor administrator uses to configure the GL during implementation.

Tyler vendor records (name, address, 1099 classification, W-9 status, payment terms, and numeric vendor ID) map to Infor Vendor Master. We preserve Tyler's numeric vendor ID as an alternate vendor key in Infor to prevent duplicate vendor creation during the initial load. Any duplicate vendors detected by EIN or name similarity are merged before insertion into Infor. Active vendor status migrates; vendors flagged as inactive in Tyler post-cutoff date are held in a reconciliation report for the district to confirm before loading.

Tyler AP invoices carry vendor ID, invoice number, invoice date, payment terms, GL distribution lines, and approval status. We map vendor ID via the vendor crosswalk, preserve GL distribution lines by resolving account codes against the Infor segment structure, and flag any invoice with a mismatched account code (an account code that was deleted or deactivated in Tyler prior to export). Invoices in Approved status migrate as open Infor AP records; invoices in Pending or Void status migrate with their status preserved in a custom field for the district's AP team to review.

General Billing and student account receivable invoices in Tyler include customer ID, invoice number, amount, and GL distribution. We match AR customer IDs to Infor contact or employee records (depending on payer type) via the contact crosswalk, preserve GL distribution lines, and migrate invoice status. Any AR invoice referencing a GL account that has been deactivated in Tyler is flagged in a pre-load reconciliation report before the Infor load begins.

Journal entries carry date, description, debit/credit line amounts, and multi-fund split distributions. Tyler enforces balanced-entry validation at the database level. We export all journal entries including reversing and recurring entries, preserving entry type flags (regular, reversing, recurring) as Infor journal batch attributes. Each line's account code is resolved to the Infor multi-segment structure using the chart-of-accounts crosswalk developed during schema design. Entries are loaded in ascending date order into Infor journal batches matching the original Tyler batch grouping.

Budget records span fiscal years and include appropriation amounts, amendments, and encumbrance carryforwards. Tyler stores budget versions as separate records with status flags (draft, approved). We map Tyler's fiscal year structure to Infor budget periods, preserving amendment history as separate Infor budget version records. Encumbrance carryforwards are mapped to Infor encumbrance records linked to the corresponding GL accounts. Budget entries are loaded before employee records in the migration sequence because Infor Payroll validates pay codes against budget account codes at the position level. We generate a Budget-to-Position Validation Report that flags every Infor position with a pay code whose GL account code is absent from the budget load, enabling the district to resolve gaps before the payroll batch arrives.

Tyler employee records include personal data, job title, FTE, compensation, benefits enrollment, union affiliation, and hire/termination dates. Effective-dated compensation history is stored across multiple records per employee. We map each employee to an Infor HCM Employee record, preserving Tyler's numeric employee ID as an alternate ID, and link the Infor Employee to the corresponding Infor Position Control record using the position crosswalk. State-specific benefit plan codes (used by Tyler for union-negotiated benefit tiers) require Infor lookup table population before employee benefit enrollment can load. We flag any benefit code that lacks an Infor equivalent in the pre-load benefit code gap report.

Tyler payroll batches link to employee records, pay period dates, deduction codes, and GL distribution. Tyler separates time entry from payroll into distinct modules with a workflow between them. We run a Pre-load Time-to-Payroll Linkage Report that cross-references every employee in the payroll export against their time entry records in Tyler and flags any missing links before committing the Infor load — without this check, a payroll batch can silently post with $0 hours if the upstream time entry was absent. We also run the Budget-to-Position Validation Report before payroll migration begins to confirm every pay code has a resolved GL account from the budget load. Deduction codes are mapped to Infor deduction setup; any deduction code referencing a GL account not present in the migrated chart of accounts is flagged for resolution.

Time entries in Tyler's Time and Attendance module include employee ID, date, hours worked, pay type, and approval status. Tyler's Advanced Scheduling stores shift assignments separately from basic time entries. We export both as line items and map to Infor Time and Attendance time entry records, preserving approval status and linking to the corresponding Infor Employee record. Shift differential codes (Tyler stores these as pay types) are mapped to Infor overtime and premium pay codes using a pay type crosswalk table. Hours in approved status in Tyler are loaded as approved in Infor; hours pending approval are loaded pending and inherit the Infor approval workflow.

Position Control records define FTE allocations, position budget amounts, and the link between a funded position and its incumbent employee. Tyler stores position records as distinct from employee records, which is why position mapping must precede employee mapping in the migration load order. We map Tyler's position ID to an Infor Position ID, preserve FTE allocation and budget amount per position, and link the incumbent employee via the employee crosswalk (Tyler employee ID to Infor employee alternate ID). Positions with a status of Frozen or Eliminated in Tyler are migrated with status preserved in a custom field for the district to confirm before activating in Infor.

Purchase Orders carry vendor ID, line items with quantities and unit costs, GL distribution per line, approval workflow status, and encumbrance flags. We export all open POs with their encumbrance balance (the unspent commitment amount) and map to Infor Purchase Orders. Encumbrance flags are preserved as Infor encumbrance records. GL distribution per line is resolved against the Infor chart-of-accounts crosswalk. PO approval workflow status is mapped to Infor workflow status, with any Tyler approval step referencing a deactivated user mapped to a reconciliation queue for the district's Infor admin to assign.

Student Activity Fund accounting in Tyler is a separate subsystem from the core General Ledger with its own fund codes and approval workflows. The activity fund numbering convention does not share Tyler Munis's fund-org-object structure. We export Student Activity Fund records as standalone GL journal entries and build a crosswalk between Tyler activity fund codes and the district's primary Infor chart of accounts before loading. This is a critical mapping step — loading activity fund records against the wrong Infor GL account range would misstate fund balances in the district's primary financial statements. We deliver the crosswalk as a named spreadsheet alongside the journal export so the district's Infor administrator can validate before committing.

Tax codes in Tyler's Revenue Management module handle Real Estate Tax, Personal Property Tax, and Motor Vehicle Excise Tax with rate tables and exemption schedules. We export the full Tyler tax code table including rate schedules and exemption codes, and map to Infor Tax Management tax codes. Property tax codes from Tyler carry jurisdiction-specific rate schedules that are migrated as Infor tax rate records with the same jurisdiction code. Any tax code in Tyler that references a GL account not present in the migrated chart of accounts is flagged before loading.

Grant records in Tyler include grantor name, award number, award period, funding amount, and budget allocation by GL account. We export grant awards with their associated budget lines and flag any grant in closeout status (balance remaining below a configurable threshold) for the district to reconcile before loading. Award period dates map to Infor grant start and end dates; GL account allocations are resolved against the Infor chart-of-accounts crosswalk. Grantor name and award number are preserved in Infor grant custom fields for audit trail.

Tyler stores document attachments (scanned invoices, contracts, employee documents) as binary blobs in a separate document management subsystem. The document store is not accessible via the Open API Toolkit — only metadata (filename, date, type, and parent record ID) is available for extraction. We extract all document metadata and note which parent records (vendor, AP invoice, employee, PO) have attachments, enabling Infor to flag those records for manual document handling or a separate Tyler Professional Services extraction engagement. We do not migrate binary document payloads as part of standard scope; this is disclosed upfront during scoping so the district can plan a separate extraction project or accept manual re-upload.