Migrate from Crank CRM to Twenty CRM

Crank CRM Organizations are extracted from demo session context and mapped to Twenty Companies. The organization's name becomes the Company name field, and any associated demo session count or metadata is preserved as custom fields on the Company record. If the organization has no name (only a domain), we use the domain as the Company name and store the original domain in a custom field.

Crank CRM Contacts captured during demo sessions map directly to Twenty People. Email, name, phone, and role fields migrate by matching on email as the dedupe key. Any demo session association is preserved by linking the People record to the corresponding Demo Session custom record via a lookup relationship. If CRM modules are inactive on the source, only screen-sharing contact captures exist; we migrate those with the session link intact.

Crank CRM Demo Sessions are the primary data entity. We create a custom object in Twenty called Demo Session with fields for session start/end timestamps, viewer count, duration in seconds, recording availability (boolean), recording URL, and sharing method. Demo Sessions link to the associated Company (organization) and People (contact) via lookup fields. The session start timestamp preserves activity ordering.

Crank CRM usage logs per session are extracted and mapped to Twenty Tasks. Task subject carries the session type (screen share, recording, email campaign), Activity Date carries the original timestamp, and task body carries the usage summary. Tasks are linked to the associated Demo Session custom record and the related People record. High-volume usage log migrations require chunking across multiple Task API calls due to Twenty's API rate limits.

Each Crank CRM demo session is tied to an account owner. We extract distinct owner references by email and match against Twenty User records. Owners without a matching Twenty User go to a reconciliation queue for the customer's admin to provision before Demo Session import resumes. Owner references on demo sessions are stored as a custom field on the Demo Session custom object pointing to the Twenty User.

If Crank CRM Pipelines and Stages are active (only present when CRM modules are enabled), we map each Pipeline to a Twenty Opportunity with a custom pipeline name field. Stage names map to Opportunity status values. We preserve stage order and probability percentages as custom fields on the Opportunity record. If CRM modules are inactive, this object is skipped and no Opportunity records exist.

Crank CRM Deals attached to Pipelines map to Twenty Opportunities with the associated Pipeline name stored as a custom field. Deal amount, close date, and stage are preserved as Opportunity amount, close date, and status. Deal-to-Company and Deal-to-Contact associations are resolved as Opportunity-to-Company and Opportunity-to-People lookups during migration.

Where CRM modules are active and custom fields exist on Contacts or Organizations, we detect these during the schema audit phase and create equivalent custom fields in Twenty's Data Model settings. Field types are mapped: text to text, number to number, date to date, checkbox to boolean, and picklist to select. Custom fields on inactive CRM modules are skipped.

Demo recordings are extracted from CrankWheel's infrastructure via the recording URL in the session record. We download each recording file and upload it to Twenty's file storage linked to the Demo Session custom record. If the recording URL has expired or the file was deleted on CrankWheel's side, we note the broken link in a custom field rather than causing migration failure. Shared files from sessions are uploaded and linked to the associated Company or People record.

If Crank CRM applies tags or labels to Contacts, these are migrated as a custom select field on the Twenty People object. The customer chooses whether to use single-select (one tag per contact) or a text field storing all tags as a comma-separated value. This decision is made during scoping based on tag usage patterns in the source account.