Migrate from Tyler Enterprise ERP to Microsoft Dynamics 365 Business Central

Tyler Fund records (fund codes, fund types, fund balances following GASB 87/94) map to a combination of Dynamics 365 main accounts and Financial Dimensions. We create a Fund Dimension that captures the original Tyler's fund-type classification, preserve the fund balance as an opening balance entry in Dynamics 365, and store the original Tyler's fund_code in a custom field for audit traceability. The destination main account structure flattens Tyler's fund hierarchy into a standard commercial chart while the Fund Dimension preserves the GASB reporting dimension required for government audits.

Tyler GL journal entries export via Tyler's standard reports with full audit trail timestamps and user attribution. We extract historical journal detail, account distributions, and posting dates, then map Tyler fund-account-department combinations to Dynamics 365 main accounts plus Financial Dimensions. Journal numbers map to LedgerJournalNum; voucher numbers map to Voucher. All posting dates and audit timestamps migrate as-is. Government-specific journal types (appropriations, encumbrances, expenditures) map to Dynamics 365 financial dimension values with a custom journal type field to preserve the original Tyler classification.

Tyler AP vendor invoices, payment runs, and 1099 vendor records migrate to Dynamics 365 VendTable with vendor name, address, W-9 status, 1099 classification, and payment terms preserved. Open payables become pending vendor invoices in Dynamics 365; payment history migrates as posted vendor ledger entries. The 1099 flag maps to a Dynamics 365 1099 vendor setting. Vendor invoice numbers map to InvoiceId; invoice dates and due dates migrate to InvoiceDate and DueDate.

Tyler AR transactions, customer billing records, and receipt history export from Tyler's AR module with customer-to-invoice relationships and payment applied detail intact. We migrate open customer invoices as pending invoices in Dynamics 365 and historical paid invoices as posted customer ledger entries. Customer names and addresses map to CustTable; invoice numbers and amounts map to CustInvoiceJour and CustInvoiceTrans. Receipts migrate as customer payment journals linked to the original invoice via the invoice number reference.

Tyler budget entries structured around appropriation periods and funding sources require a multi-step mapping into Dynamics 365 Budget Planning. We extract budget versions and amendment history, mapping each Tyler's fund-budget-department combination to a corresponding budget planning model in Dynamics 365 with fund as a dimension and appropriation period as a scenario. Amendment versions migrate as budget revision scenarios. The destination budget register configuration must be decided during scoping: Budget Register (ledger-based) or Budget Planning (analytical-based) depending on the government's reporting requirements.

Tyler purchase orders, requisitions, and approval workflows export from Tyler's purchasing module with vendor linkage, line-item detail, and PO history. We migrate PO header data (vendor reference, PO number, order date, terms) to PurchTable and PO lines (item number, quantity, unit price, amount) to PurchLine. Requisitions migrate to PurchReqTable. Approval statuses map to WorkflowState. Historical closed POs migrate as posted purchase order history; open POs remain in active state pending reconciliation with AP.

Tyler Position Control tracks budget-authorized positions at the position level independent of whether an employee occupies the position. This is a critical distinction for school districts managing hiring against approved position budgets. We extract position definitions, funding sources, and budget-to-position linkages. In Dynamics 365, positions exist as HR Position records attached to workers. We map Tyler's funded positions to HcmPosition records, preserve the position budget amount in a custom field, and flag positions with no incumbent as vacant. The customer's HR team decides during scoping whether to maintain position budgets as position records or translate to department-level compensation budget allocations in the destination system.

Tyler HR data includes employee records, job classifications, and organizational structure for government deployments. We map Tyler's employee records to Dynamics 365 HcmWorker, preserving job title, department, employment status, hire date, and compensation rate. Government-specific job titles and classifications migrate as custom fields. Active employees map to HcmWorker with current employment; terminated employees migrate with historical employment records. The HR module configuration (Dynamics 365 Human Resources or full Finance and Operations HR) must be determined during scoping as it affects the worker data model.

Tyler vendor master records export with 1099 classification, W-9 status, payment terms, and remittance addresses. We migrate active and historical vendor relationships to VendTable. 1099 classification maps to a Dynamics 365 1099 type field; payment terms map to PaymentTermId. Vendor numbers from Tyler map to VendorAccountNumber. Historical vendor records inactive in Tyler but with open payables migrate as inactive with a custom flag to ensure they remain accessible for AP reconciliation.

Tyler permits user-defined custom fields across modules that capture government-specific data not in standard fields. We inventory every Tyler's custom field definition during discovery, classify each by data type (text, number, date, picklist), and recreate them as custom fields in Dynamics 365. Dynamics 365 supports custom fields via the Custom Fields workspace in Finance and Operations. The original Tyler's custom field label and database name migrate as a custom field label in Dynamics 365 with the original Tyler's database name stored in a reference field for audit traceability.

Tyler's document management captures scanned invoices, contracts, and supporting files. We extract document references and binary attachments where accessible via Tyler's file storage. Dynamics 365 Finance and Operations uses SharePoint or Azure Blob Storage for document attachment via its Document Handling feature. We map Tyler's document paths to the corresponding SharePoint or Azure URL structure and create DocumentLocation records linking attachments to the parent transaction (vendor invoice, purchase order, employee record). Some legacy scanned documents with illegible filenames may require manual renaming post-migration.

Tyler maintains comprehensive transaction audit logs across modules required by government oversight bodies. We extract audit trail records with user attribution, transaction timestamps, and modification history. Dynamics 365 preserves an audit log via its SystemAdministration workspace. We import Tyler's historical audit records as a custom AuditHistory table in Dynamics 365 so that government auditors reviewing the migrated system can query the full pre-migration audit trail alongside Dynamics 365's native audit log.