Migrate from CRM Runner to Twenty CRM

CRM Runner Contacts map directly to Twenty CRM People. The CRM Runner contact record (name, email, phone, address, and any custom fields) migrates as a People record. Email becomes the dedupe key during import. CRM Runner custom fields on contacts pre-exist in Twenty as custom fields on the People object. If CRM Runner contacts are linked to a Company record, we preserve the link by resolving the company name to the Twenty CRM Company record via the CRM Runner company_id foreign key.

CRM Runner Company records map 1:1 to Twenty CRM Company. The CRM Runner domain field (if present) becomes the Twenty CRM website field. Company name is the dedupe key. Company records must import before People records so that the People-to-Company relationship is satisfied at the moment of People insert. Any CRM Runner custom fields on Company migrate as Twenty CRM custom fields created under Settings Data Model before import.

CRM Runner Jobs are the most complex migration object because they combine field-service work order data (location, assigned team members, status, time entries) with what functions as a deal record in a sales CRM. We map Jobs to Twenty CRM Opportunity with the CRM Runner job title becoming the Opportunity name, job status mapped to Opportunity stage values, and estimated or actual amounts carried as Opportunity amount fields. The location and assigned team member data does not have a native Twenty CRM equivalent; we preserve these as Note records attached to the Opportunity and flag them for manual rebuild if they drive workflow logic.

CRM Runner Team Members map to Twenty CRM Workspace Members. We extract role, department, and permission level from CRM Runner and migrate these to Twenty CRM member roles under Settings Members. CRM Runner GPS tracking and time-clock features have no equivalent in Twenty CRM; we export this as a separate data package and flag it as outside CRM scope. Permission level rebuild is manual because Twenty CRM's role permissions are structured differently from CRM Runner's permission tiers.

CRM Runner embeds call logs, SMS threads, and in-app chat as discrete communication records attached to contacts or jobs. We flatten these into Note records in Twenty CRM, one Note per communication event. The Note body carries the communication type (call/SMS/chat), timestamp, direction (inbound/outbound), and content. We link each Note to the corresponding People record in Twenty CRM. This loses CRM Runner's threading model for SMS but preserves the full communication history in an accessible format.

CRM Runner Tasks migrate directly to Twenty CRM Task records. Due date, assignee (resolved via Team Member mapping), status, and description carry over. Task assignment in Twenty CRM uses the WorkspaceMember lookup; we resolve CRM Runner assignee references via the Team Member mapping to ensure the assignee is a valid Twenty CRM WorkspaceMember at migration time.

CRM Runner time entries (clock-in/clock-out records tied to Team Members and Jobs) do not map to a standard Twenty CRM object. Twenty CRM has no time-tracking module. We export time entries as a separate CSV package with fields for employee, job reference, date, clock-in time, clock-out time, and duration. This package is delivered alongside the main migration for import into a dedicated time-tracking or payroll tool.

CRM Runner pipeline stages migrate as Twenty CRM Opportunity stage values. We capture the stage name, order, and probability percentage from CRM Runner and configure the corresponding stage in Twenty CRM under Settings Opportunities before migration. Custom stage logic (conditional routing, auto-close rules) does not migrate and is documented for manual rebuild.

CRM Runner custom fields on Contacts, Companies, and Jobs require pre-creation in Twenty CRM before data import. We extract all custom field definitions during scoping (field name, type, options for picklists, required vs optional), create the equivalent Twenty CRM custom fields under Settings Data Model before migration begins, and map the source field values during the import phase. Fields with no equivalent type in Twenty CRM (e.g., CRM Runner-specific field-service field types) are flagged for review.

CRM Runner payment and transaction records are embedded within Jobs or Contacts and are accounting-adjacent. Twenty CRM has no native payment or accounting module. We extract payment records as a separate CSV package with fields for customer, job reference, amount, payment method, date, and status. This package is delivered alongside the main migration for import into a dedicated accounting or bookkeeping tool.

CRM Runner IFTTT-style automations are not migratable. The platform's trigger-action logic is configured through a proprietary interface with no documented export path. We document every active automation we identify during discovery as a written specification: trigger type, conditions, actions, and recommended Twenty CRM equivalent (manual action or workflow rule if applicable). The customer's admin uses this document to rebuild automations post-migration. This is not included in the standard migration timeline.

CRM Runner product catalog entries and QR code configurations are platform-specific display assets with no standard CRM equivalent in Twenty CRM. These must be rebuilt in Twenty CRM or a separate product management tool. We do not include them in the migration scope.