Migrate from Bilr to Twenty CRM

Twenty's Pro tier limits custom objects to 10, which may be insufficient for complex Bilr matter configurations

Bilr matters with multiple UTBMS task categories and custom billing properties require several custom objects (Matter, TimeEntry, Invoice, plus any domain-specific entities like Expenses or Disbursements). Twenty Pro caps custom objects at 10, and reaching this limit during migration planning is a common surprise. FlitStack AI audits the custom object count during discovery and flags whether Organization-tier workspace setup is required. If Organization-tier is not feasible, we consolidate related data into fewer objects using compound custom fields or pick-list segmentation. This gotcha is specific to the Bilr-to-Twenty migration because Bilr's billing model is more object-rich than typical CRM data.

Import ordering constraint in Twenty causes relation failures if Companies are not migrated first

Twenty's CSV import system enforces a specific dependency order: Companies must be imported before People (because People records carry a companyId foreign key), and all objects with relations must follow their parent objects. Bilr's data model has no such constraint — clients, matters, and time entries can be exported in any order. FlitStack AI sequences the migration export to match Twenty's required import order: Companies first (mapped from Bilr client companies or created as placeholder accounts for individual clients), then People linked via companyId, then custom objects for Matters, then TimeEntries linked to Matters, then Invoices linked to Matters. Skipping this sequence results in import errors where People records cannot resolve their companyId and TimeEntry records cannot resolve their matterId, triggering Twenty's uniqueness-check failures.

UTBMS task code taxonomy has no native equivalent in Twenty — pick-list mapping requires manual curation

Bilr's UTBMS-coded task categories (e.g., A100 for Case Evaluation, B101 for Fact Investigation) are a legal-industry standard that Twenty has no native concept of. We create a custom pick-list field (UTBMS_Task_Code__c) on the TimeEntry custom object, but Bilr instances often include non-standard codes or firm-specific variations that don't match the official UTBMS taxonomy. These custom codes must be mapped individually during the migration plan — a code-by-code review that adds scope for firms with complex billing arrangements. We surface all unique UTBMS values found in the Bilr export and ask the client's billing admin to confirm the mapping before the migration runs.

Bilr billing workflows and invoice templates have no Twenty equivalent and require manual rebuild

Bilr's billing engine generates invoices from time entries and applies firm-specific rules (e.g., invoice numbering conventions, expense markups, payment terms, billing group assignments). Twenty has no native billing or invoicing engine — its Opportunities object tracks deal values but does not generate documents. FlitStack AI migrates the underlying data (time entries, invoice records, billing rates) as custom objects and fields, but invoice templates, billing rules, payment reminders, and automated billing workflows cannot migrate and must be rebuilt. We export Bilr's workflow definitions as a reference document for the client's admin to use when configuring Twenty's workflow builder or integrating a separate billing tool.

Twenty's 20,000-record export limit per CSV may require chunking for large Bilr instances

Twenty's CSV export function caps each export at 20,000 records. Bilr instances for mid-size law firms or multi-attorney practices often contain more than 20,000 time entries spanning years of billing history. FlitStack AI handles this by exporting Bilr data in date-range slices (e.g., by year or by matter batch) and merging them into Twenty's custom objects. The 20,000-record limit applies per object per export run — multiple exports of the same object type are supported as long as each export's record set is unique. We flag record counts above this threshold during the discovery phase so the migration plan accounts for multi-export sequencing.