Migrate from Tyler Enterprise ERP to Epicor Prophet 21

Tyler structures all accounting around government fund codes following GASB standards. Epicor has no native fund-accounting structure, so we extract fund type definitions, fund codes, and cost center hierarchies and remap them into Epicor's commercial chart of accounts. We preserve fund-level reporting balances as custom fields on the Account record (e.g., fund_code__c, fund_type__c) or as sub-account segments in Epicor's multi-segment account structure. The mapping must be validated against the organization's GASB audit requirements before cutover.

GL transactions, journal entries, and account balances export from Tyler's standard reports with full audit trail timestamps and user attribution. We extract historical journal detail by fund and fiscal period, mapping each Tyler fund-account line to an Epicor Account segment. Epicor's GLJrnTran records preserve the transaction date, fiscal period, and source module. We maintain the original posting user as a custom field since Epicor's native user tracking ties to Epicor user accounts, not the Tyler's original users.

Vendor invoices, payment runs, and 1099 vendor records export from Tyler's AP module. We extract open payables and full payment history with vendor linkage intact, mapping Tyler vendor records to Epicor Vendor records and Tyler invoice lines to Epicor APTran entries. 1099 classification, W-9 status, and payment terms migrate to Epicor Vendor fields. Open AP balances are verified against Epicor's AP open balance report post-migration.

AR transactions, customer billing records, and receipt history export from Tyler's AR module. We preserve customer-to-invoice relationships and payment applied detail, mapping Tyler AR customers to Epicor Customer records and Tyler invoice headers to Epicor InvcHead with line items on InvcDtl. Receipt history and applied cash migrate as Epicor CashRcpt records linked to the original invoices.

Tyler budget entries are structured around appropriation periods and funding sources specific to government budgeting cycles. We extract budget versions and amendment history, mapping Tyler's fund-budget-department relationships to Epicor's budget structure. Since Epicor has no native appropriation-control model, fund-budget linkages store as custom fields on Epicor Budget records, and the customer's Epicor admin configures budget-check workflow rules in Epicor BAM or BPM if appropriation controls are required to persist.

Purchase orders, requisitions, and approval workflows export from Tyler's purchasing module. We extract PO history with vendor and line-item detail, mapping Tyler vendor references to Epicor Vendor, Tyler item codes to Epicor Part or MfgPart records, and PO line quantities to Epicor POLine. Approval routing does not migrate; we document the Tyler approval workflow structure for the customer's Epicor admin to rebuild in Epicor BPM.

Position Control tracks staffing at the position level rather than employee level, which is a critical distinction for school districts managing hiring against approved position budgets. We extract position definitions, budget authorization amounts, and incumbent status. In Epicor, position-level budget authorizations map to department-level compensation budget allocations in Epicor's HR module, and positions without incumbent employees are flagged for manual position-to-employee reconciliation in Epicor. This is a high-severity mapping gap that requires explicit scoping sign-off.

HR data in Tyler Enterprise ERP for Schools includes employee records, job classifications, and org structure. We extract employee demographics, job titles, department assignments, and compensation. Government-specific job titles and custom fields require field-level mapping against Epicor's HR schema. Epicor Employee records are employee-centric (not position-centric), so position-to-employee mapping requires resolution against the Position Control translation in scope item 7.

Vendor master records with 1099 classification, W-9 status, and payment terms export from Tyler's vendor file. We preserve all active and historical vendor relationships, mapping them to Epicor Vendor records with address book linkage, payment terms, and 1099 configuration intact. Epicor's Vendor table supports multiple addresses and contacts via the VendorPP and VendorAttr tables, which we populate from Tyler's vendor contact records.

Tyler permits user-defined custom fields across modules. We inventory all custom field definitions during scoping and map them to Epicor user-defined (UD) fields on the corresponding Epicor table (e.g., PartLot_c, Vendor_c). Epicor UD fields follow a specific naming convention and require pre-creation in Epicor's customization tools before data load. Type translation is required since Tyler field types do not map one-to-one to Epicor field types.

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. Epicor's native document management attaches files to records via DocStar or Epicor's internal document storage. We map Tyler's document references to Epicor's document links on the equivalent records (AP Invoice, AR Invoice, Purchase Order), though some Tyler legacy formats may require conversion or may be flagged as non-migratable.

Tyler maintains comprehensive transaction audit logs across modules. We extract audit trail records to preserve compliance documentation required by government oversight bodies. Epicor's native audit logging does not cover historical Tyler records, so we deliver the audit trail data as a structured archive (searchable CSV or JSON) attached to the Epicor company as a read-only reference dataset, not as live Epicor records. This satisfies the government's requirement for historical audit access without forcing Tyler audit log entries into Epicor's transactional schema.

Tyler's 1099 tracking is part of the AP module with vendor-level 1099 box assignments and annual 1099 reporting data. We extract the 1099 history by vendor and box type and map it to Epicor's APTran records tagged with 1099 box codes. Epicor's TaxConn module handles 1099 reporting, and we ensure vendor 1099 box assignments migrate as Epicor VendorTaxRi records. Historical 1099 form data for closed fiscal years is archived separately as PDF output from Tyler's 1099 report.

Tyler Enterprise ERP does not include a dedicated manufacturing inventory module, but some government deployments use Tyler's inventory or asset tracking for consumables and capital assets. If Tyler inventory records exist, we map them to Epicor Part (for stock items) and PartBin (for bin-level inventory) records. Epicor's Part table supports lot/serial tracking, multi-warehouse, and UOM conversions that Tyler's government-specific inventory may not. We flag any inventory records with non-standard UOMs for manual review before Epicor import.