Migrate from Tyler Enterprise ERP for Schools to Microsoft Dynamics 365 Business Central

Tyler stores account codes as structured strings (fund-org-object or fund-dept-object) using government fund-accounting conventions with fund-type codes (governmental, proprietary, fiduciary). Dynamics 365 Finance separates this into a Main Account (the account segment) and Financial Dimensions (fund, department, cost center, project). We parse the Tyler account string into its component segments and configure a corresponding Financial Dimension set in Dynamics. GASB-compliant fund-type classification is preserved as a dimension value. Fund codes with reserved-character restrictions in Dynamics are flagged and crosswalked before import.

Vendor records in Tyler include name, address, 1099 classification, W-9 status, and payment terms with a numeric vendor ID. We map vendor IDs and merge duplicates detected by EIN or name similarity, then load into Dynamics 365 Vendor with 1099 configuration enabled where applicable. Vendor addresses migrate as postal addresses with the primary address flag set from Tyler's default-address indicator.

AP invoices in Tyler carry vendor ID, invoice number, invoice date, payment terms, GL distribution lines, and approval status. We flag any invoice with a mismatched account code (a deleted Tyler account with no Dynamics 365 equivalent) before load and generate a GL-distribution reconciliation report. Open invoices load as Vendor Invoice records in Dynamics with invoice-date-relative due dates computed from Tyler's payment terms. Approved status migrates directly; pending-approval invoices migrate with a Hold flag for the district to release post-migration.

General Billing and student account receivable invoices in Tyler include customer ID, invoice number, amount, and GL distribution. We match AR customer IDs to employee or parent contact records using the district's contact crosswalk and load AR invoices into Dynamics 365 as either Free Text Invoices (for simple charges) or Customer Invoices (for full AR workflow). GL distribution lines map account codes through the chart-of-accounts crosswalk before insert.

Journal entries in Tyler carry date, description, debit/credit line amounts, and multi-fund split distributions with balanced-entry validation enforced at source. We export all journal entries including reversing and recurring entries and load them into Dynamics 365 General Journal with line-level debit/credit amounts preserved. Multi-fund split distributions map each line through the fund-dimension crosswalk. Tyler's journal batch and entry-number sequencing is preserved in Dynamics journal batch references.

Budget records in Tyler span fiscal years and include appropriation amounts, amendments, and encumbrance carryforwards. Tyler stores budget versions as separate records with status flags (draft, approved). We export budget entries with their effective dates, fiscal year, and fund-account references, then load into Dynamics 365 Budget Register using the Budget Model configured for the district's fiscal calendar. Amendments and carryforward amounts are loaded as separate budget revision lines. Budget status (draft vs approved) maps to Dynamics budget check behavior.

Employee records in Tyler include personal data, job title, FTE, compensation, benefits enrollment, union affiliation, and hire/termination dates. Effective-dated compensation history is stored across multiple records. We export employees as Worker records in Dynamics 365 HCM, preserving compensation history as effective-dated worker employment records. Union affiliation migrates as a pay-related dimension. Position assignments are loaded after Position Control records exist in Dynamics.

Position Control records in Tyler define FTE allocations, position budget amounts, and the link between a funded position and its incumbent employee. Tyler stores positions as distinct from employee records. We export positions first (before Employee records in load order), create corresponding Dynamics 365 HCM Position records with FTE and position budget amount, then link incumbents via Worker Position Assignment records after Workers are loaded. Position-to-budget linkage is preserved as a financial dimension filter in Dynamics.

Payroll batches in Tyler 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-flight Time-to-Payroll Linkage Report that cross-references every employee in the payroll export against their time entry records and flags any missing links before committing the load. Dynamics 365 Payroll batch references Worker IDs and Pay Agreement lines resolved from the position assignment.

Time entries in Tyler's Time and Attendance module include employee ID, date, hours worked, pay type, and approval status. Advanced Scheduling stores shift assignments separately. We export both as line-item time registration entries with worker ID, date, hours, and pay type, then load into Dynamics 365 Time module linked to the corresponding Worker. Tyler's approval workflow status maps to a Time Entry Status field; entries without approval in Tyler are flagged as unapproved in Dynamics.

Purchase Orders in Tyler carry vendor ID, line items with quantities and unit costs, GL distribution per line, approval workflow status, and encumbrance flags. We export open POs with their encumbrance balance and load into Dynamics 365 Purchase Order with line-item quantities, pricing, and GL distribution mapped through the chart-of-accounts crosswalk. Encumbrance balance is preserved as a pre-encumbered amount in Dynamics pending receipt processing.

Student Activity Fund accounting in Tyler is a separate module from the General Ledger with its own fund codes and approval workflows. We export activity fund balances as standalone GL journal entries and build a crosswalk between Tyler Activity Fund codes and the district's primary chart-of-accounts fund dimension. Activity fund approval workflows are documented as a written handoff for the district's admin to configure in Dynamics as workflow approvals on the journal batch. Activity fund balance amounts load as opening balances in the corresponding Dynamics fund dimension.

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 tax code table including rate, basis, and exemption rules and configure corresponding Sales Tax Groups in Dynamics 365 with the appropriate tax codes, rates, and posting definitions. Local-option and district-specific tax codes require manual configuration in Dynamics as additional sales tax authorities.

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 with a compliance deadline or reporting requirement. Dynamics 365 Finance supports Grant Management as a module; we configure Grant records with award metadata, attach the associated budget allocation by fund-dimension split, and set award period dates as grant validity dates. Active grant balances are reconciled against the GL before closing.

Tyler stores document attachments as binary blobs in a separate document management subsystem behind Tyler's authentication layer. The Open API Toolkit exposes document metadata (filename, date, type, and parent record ID) but not the file payload. We extract all document metadata, note which parent records (Vendor, Employee, Purchase Order, Journal Entry) have attachments, and deliver a written inventory listing the record type, record ID, and attachment filename. Binary extraction requires a separate Tyler Professional Services engagement or direct database access. The destination system flags those records for manual document handling post-migration.