Migrate from Bill4Time to Twenty CRM

Bill4Time Clients map directly to Twenty Companies. Address, phone, email, and account-manager fields carry over as Company fields. Clients with a billing name distinct from the legal name get the billing name stored in Company.name with the original client name preserved in a custom text field.

Bill4Time Projects become Twenty Opportunities. Project name maps to Opportunity.name, and the project budget or flat-fee amount maps to Opportunity.amount. The project status (Open/Closed) maps to Opportunity.stage as a custom pick-list — Open maps to an active pipeline stage, Closed maps to Won or Lost based on the project's outcome field.

Bill4Time Time Entries migrate as Twenty Tasks linked to the parent Company and Opportunity (project). The description field maps to Task.title, entry date to Task.dueDate, and hours to a custom number field (Task_Billable_Hours__c). The billable/non-billable flag is preserved as a custom select field (Billable__c) on the Task.

Twenty has no native invoice object. We create a custom Invoice object in Twenty (Settings → Data Model → Custom Objects) and migrate invoice metadata (invoice number, date, amount, status, client link) as fields on that object. The full invoice body — line items, taxes, notes — is preserved as a JSON blob in a long-text field or attached as a Note to the associated Company record.

Bill4Time User records map to Twenty Workspace Members. First name, last name, email, department, and billing rate carry over. Unmatched users (employees who do not yet have a Twenty account) are flagged before migration and must be invited to Twenty before their records can be assigned.

Bill4Time Expense records migrate as a custom Expense object linked to the parent Company and Project. Expense amount, date, category, and billable flag are custom fields. If the custom object is not pre-created in Twenty, expenses attach as Tasks with a custom Expense_Amount__c field and an Expense__c checkbox.

Bill4Time Enterprise-tier custom fields on Clients (text, number, date, list, client-list, user-list types) migrate to custom fields on Twenty Companies. List-type custom fields require value mapping if the pick-list options differ between platforms. The custom field schema must be created in Twenty (Settings → Data Model) before the import batch runs.

Bill4Time custom fields on Projects migrate to Twenty Opportunity custom fields using the same type-mapping logic. ProjectType (Hourly/Flat Fee/Percentage) becomes a custom select on the Opportunity. Billing rates and overtime rates from the Project record store as custom currency fields.

Bill4Time custom fields on Time Entries — such as litigation codes or activity type categories — migrate as custom select or text fields on Twenty Tasks. Activity type maps to Task.Status or a custom select field depending on Twenty's field availability at migration time.

The Bill4Time accountManagerId on a Client record resolves to a Twenty Workspace Member by email match and links to the Company as the assigned owner. If the account manager has no Twenty account, the Company is assigned to a fallback owner flagged in the pre-migration owner-resolution report.

The Bill4Time assignedTo user on a Project resolves by email to a Twenty Workspace Member and populates the Opportunity.assignee field. Unresolved assignments map to a placeholder assignee and surface in the pre-flight report for manual correction before the full migration commits.

Bill4Time invoice PDF attachments have no native Twenty equivalent. FlitStack re-uploads each PDF as a Twenty Note linked to the corresponding Company record, sets the custom Invoice_Document__c checkbox to true, and names the Note using the original invoice filename. The PDF blob is stored as a file attachment on the Note, preserving the full document for download while the custom field enables quick filtering in Twenty.