Migrate from Road Runner to Twenty CRM

Road Runner customers map directly to Twenty People. Each customer record's name, email, phone, and address fields map to the corresponding Twenty fields. Customer records without an email receive a placeholder domain (e.g., customer-{id}@placeholder.local) flagged for admin review. Phone numbers are normalized to a standard format during import.

When a Road Runner customer represents a business entity rather than an individual, their company name and domain map to Twenty Companies. The companyId relationship links the People record to the Companies record, preserving the account hierarchy that Twenty uses for pipeline reporting.

Road Runner jobs are the primary work unit. Each job maps to a Twenty Opportunity with the job name as the Opportunity name, job amount as the Amount, and the Road Runner status (Scheduled, In Progress, Completed, Invoiced) mapped to a Twenty Opportunity stage pick-list. Job priority maps to a custom Priority field on the Opportunity.

Road Runner's job status field has discrete values that must map to Twenty's Opportunity Stage values. 'Scheduled' maps to a Prospecting or Qualification stage; 'In Progress' maps to an active stage; 'Completed' maps to Closed Won; 'Invoiced' maps to Closed Won with invoice data attached; 'Cancelled' maps to Closed Lost.

Road Runner's container tracking has no direct Twenty CRM equivalent. We create a Container custom object in Twenty with fields for Container ID, Type/Size, Status (On Rent, Available, In Service), and Current Location. Each container links to its associated Company via a relation field.

Road Runner's QB-synced invoices require a custom Invoice object in Twenty if line-item history is needed inside the CRM. We map Invoice ID, date, total amount, and status. If only summary invoice data is required, these fields attach to the parent Opportunity record instead.

Road Runner job notes and communication logs attached to a job record migrate as Twenty Notes linked to the corresponding Opportunity. Timestamps and author attribution are preserved. Call disposition records map to Tasks with the disposition captured in the Task subject or a custom field.

Road Runner driver records map to Twenty Workspace Members by email match if drivers are also CRM users. If drivers are not CRM users, their records migrate as a custom Driver object with name, phone, and status fields, linked to job assignments via a relation field on the Opportunity.

Road Runner attachments (photos, delivery confirmations, container condition reports) download from Road Runner storage and re-upload to Twenty's attached Notes. If the files are large or numerous, we surface them in Twenty as a custom URL field pointing to a shared storage location rather than migrating binary blobs directly.

Any Road Runner custom fields on customer, job, or container records migrate as custom fields on the corresponding Twenty object. Multi-select pick-lists in Road Runner (e.g., service types applied to a job) map to Twenty multi-select fields or a series of boolean fields depending on filterability needs.

Road Runner owner or assigned rep on a job record is resolved by email match against Twenty Workspace Members. Unmatched owners are flagged before migration. You either invite them to Twenty first or assign their records to a fallback owner — no record lands without an owner reference in Twenty.

QuickBooks sync state, QB-specific invoice IDs, and payment reconciliation links do not have an equivalent in Twenty CRM. Invoice header data migrates to the custom Invoice object; QB-level transaction references are stored as a text field for reconcilliation after you connect your accounting tool to Twenty.