Migrate from Tyler Enterprise ERP to Dolibarr ERP

Tyler funds (GASB fund types: General, Special Revenue, Capital Projects, Debt Service, Enterprise, Fiduciary) map to a combination of Dolibarr Account records at the header level and custom fields on those accounts storing the original fund code and fund type. We preserve fund balances (actual vs budgeted) in Dolibarr as custom numeric fields (fund_balance__c, fund_type__c, appropriation_total__c) so that government clients retain GASB-balance visibility without the native fund hierarchy. This mapping must be validated against the organization's audit requirements before cutover because fund type classification affects year-end reporting.

Tyler's GL transactions (journal entries, account balances, audit timestamps, user attribution) map to Dolibarr Account records with transaction detail stored as Dolibarr's VAT/receipt entries or direct database accounting entries depending on the Dolibarr accounting configuration. We extract historical journal detail with full audit trail timestamps and user attribution, preserving these as custom fields or as a migration-supplemental CSV audit log for compliance documentation.

Tyler's AP module (vendor invoices, payment runs, 1099 vendor classification, W-9 status, payment terms) maps to Dolibarr's Third-Party Supplier records with associated Invoice objects. We extract open payables and payment history with vendor linkage intact. 1099 classification migrates as a custom field on the Supplier record since Dolibarr's standard supplier model does not include a dedicated 1099 field.

Tyler's AR transactions, customer billing records, and receipt history map to Dolibarr's Third-Party (Customer type) records with associated Invoice objects. Customer-to-invoice relationships and payment applied detail migrate as Dolibarr payment entries linked to the invoice records. Receipt references and payment method codes translate to Dolibarr's payment conditions.

Tyler budget entries structured around appropriation periods and funding sources map to a combination of Dolibarr Account records (for the expense accounts being budgeted) and custom budget fields storing appropriation amounts, amendment versions, and fund-source linkage. For complex multi-fund budget structures, we use Dolibarr Project records to group budget allocations by fund or department. Budget amendment history migrates as sequential custom field entries or as a supplemental audit log rather than as native Dolibarr budget versions (which are not a standard feature).

Tyler's purchase orders, requisitions, and approval workflow status export with vendor and line-item detail. We map purchase orders to Dolibarr Supplier Order records and requisitions to Dolibarr Proposal records (draft status). Approval workflow status migrates as a custom field on the record because Dolibarr does not have a native multi-step approval workflow engine built into its purchasing module.

Tyler's Position Control (position-level budget authorization independent of employee occupancy) requires deliberate remapping because Dolibarr tracks employees, not budget-authorized positions. We extract position definitions, funded amounts, and position-to-department linkage. In Dolibarr, we create Employee records for each position (marked as 'Position Only' with a custom field is_position__c = true) and store budget authorization amounts in custom fields against the employee or against a Department record, depending on the organization's budget reporting needs. This mapping requires a scoping decision on how the district or municipality wants to report budget-vs-hire against positions.

Tyler HR data includes employee records, job classifications, organizational hierarchy, and government-specific job titles. These map to Dolibarr Employee records with job title and department linkage. Government-specific job titles and classification codes migrate as custom fields. Employee Self-Service portal data (W-2 references, pay stubs) requires separate extraction from Tyler's HR module and does not map directly to any standard Dolibarr object; we extract as a supplemental file for the customer's admin to re-enter or integrate via Dolibarr's document management module.

Tyler's vendor master records with 1099 classification, W-9 status, payment terms, and 1099 year-end data map to Dolibarr Third-Party records (type = Supplier). We preserve all active and historical vendor relationships, payment terms, and banking information in custom fields since Dolibarr's standard supplier model includes basic contact and payment information but not all government-specific vendor tax classification fields.

Tyler permits user-defined custom fields across modules. Dolibarr supports ExtraFields on most objects (ThirdParty, Product, Project, etc.) as key-value pairs. We inventory all Tyler's custom field definitions during scoping and create equivalent Dolibarr ExtraFields before migration. Field type mapping (date fields, numeric fields, picklist equivalents) requires manual type assignment because Dolibarr ExtraFields store data as text strings by default.

Tyler's document management (scanned invoices, contracts, supporting files) exports as file references and binary attachments where accessible via Tyler's file storage. Dolibarr's document management attaches files directly to records via its document directory structure. We extract document binaries and attach them to the corresponding Dolibarr records. Legacy documents stored in Tyler's proprietary document vault may not be fully accessible; we flag these as potential data gaps during discovery.

Tyler maintains comprehensive transaction audit logs across modules required by government oversight bodies. Dolibarr does not have a native audit trail feature beyond document versioning. We extract Tyler's audit trail records and deliver them as a structured supplemental audit log file (CSV or JSON) alongside the migrated data. The organization's auditors must confirm whether this format satisfies their audit requirements or whether audit trail data needs to be maintained in a separate compliance system.