Migrate from Crank CRM to Pipedrive

Crank CRM Contacts captured during demo sessions map directly to Pipedrive Person records. We preserve name, email address, phone number, and any custom properties attached to the Contact at the time of the session. The Crank CRM contact identifier is stored in a custom field crank_contact_id__c on the Pipedrive Person for reconciliation and audit. Demo history for each Contact is accumulated as Pipedrive Activity records rather than embedded in the Person record, preserving the full session timeline.

Crank CRM Organizations stored in session context map to Pipedrive Organization records. The key difference is that Crank CRM Organizations are tied to the screen-sharing session context rather than a full account management entity. We extract the organization name, domain (if present), and any associated session metadata, and we create the Pipedrive Organization as the first parent record so that Person imports can reference it via Organization ID. If the Organization was created solely from a session viewer email domain, we flag it for the customer to verify and merge with any pre-existing Pipedrive Organization.

Crank CRM Demo Sessions are the primary data entity and map to Pipedrive Activity records (calls, meetings, or tasks depending on session type) linked to the corresponding Person and Organization. Session metadata including viewer count, duration, sharing method (link, email, embed), and start/end timestamps migrates as custom Activity fields. The demo recording URL migrates as a separate file attachment linked to the Activity rather than embedded in the activity body. Sessions without an associated Contact are linked to the Organization if one exists, or flagged as orphaned for manual resolution.

Multiple Crank CRM Usage Log entries for a single session (screen shares, recording views, email shares) merge into a single Pipedrive Activity record with session-type details stored as custom fields. Each distinct usage event type gets a type label (screen_share, recording_view, email_share) that maps to a Pipedrive Activity category. We aggregate usage metrics across the session rather than creating one Activity per usage log row, since Pipedrive's activity timeline is best consumed as one entry per meaningful interaction.

Crank CRM Deals, if the CRM module is active on the source account, map to Pipedrive Deals. The Crank CRM deal stage maps to a Pipedrive Pipeline Stage, and we create a Pipedrive Pipeline to receive the Deal data before migration. If multiple Crank CRM pipelines exist, we create corresponding Pipedrive Pipelines and map deal records to the correct Pipeline ID during import. The Crank CRM deal value, expected close date, and any custom fields migrate to equivalent Pipedrive Deal fields.

Crank CRM Pipelines and Stages are only present if the CRM module is active, which we confirm during the schema audit. Each Crank CRM Pipeline becomes a Pipedrive Pipeline with its Stage names and order preserved. If the customer has not activated CRM modules, we skip this object entirely and migrate only screen-sharing and contact data. Pipedrive's visual Pipeline builder receives the stage names in the order defined in Crank CRM, with open stage marked as the active working stage.

Crank CRM session owners map to Pipedrive User records. We resolve each owner by email match against the Pipedrive destination account's user list. Any owner without a matching Pipedrive User is held in a reconciliation queue; the customer provisions the missing Users before record import continues. The owner reference on Activity records (Demo Sessions and Usage Logs) is resolved by Pipedrive User ID at migration time.

Crank CRM custom fields on Contact or Organization are only present if the CRM module is active. We detect them during the schema audit phase, create equivalent custom fields in Pipedrive before data import, and map field values during the Person or Organization import. Field type mapping applies: text fields to Pipedrive text, date fields to Pipedrive date, picklist fields to Pipedrive options. Pipedrive supports custom fields from its first paid plan without additional cost.

Demo recording URLs stored on CrankWheel infrastructure are extracted via the session endpoint and re-uploaded to Pipedrive Files during migration. Each recording is linked to the corresponding Activity record (Demo Session) via a File association. Recordings with expired or deleted source URLs result in a broken link annotation rather than a migration failure; we flag these records in the reconciliation report for the customer to review manually.

Any files shared during a Crank CRM demo session are extracted via the session endpoint and re-uploaded to Pipedrive Files, linked to the parent Activity record. Shared file metadata (filename, upload timestamp, file size) is preserved in Pipedrive File description fields. We do not migrate files that are no longer accessible at the source URL; these are flagged in the skip file for manual resolution.