Migrate from Crank CRM to Salesforce Sales Cloud

Crank CRM Contacts captured during demo sessions or via screen-sharing viewer flows map to Salesforce Contact. We preserve the contact's email, name, phone, and company association, and link any associated demo history as Salesforce Tasks or custom Activity records against the Contact. The Crank CRM contact record's creation timestamp maps to Salesforce Contact.CreatedDate.

Crank CRM Organizations stored in the screen-sharing session context map to Salesforce Account. The organization name becomes Account.Name, and the organization domain becomes the Account Website field for deduplication. Account is created before Contact import so that the AccountId lookup relationship is satisfied at the moment of Contact insert.

Demo sessions are the primary data entity in Crank CRM. We extract session start and end timestamps, viewer count, recording availability (URL reference), and sharing method. Sessions map to a Salesforce custom object (Demo_Session__c) with fields for SessionStart__c, SessionEnd__c, ViewerCount__c, RecordingUrl__c, and SharingMethod__c, linked to the Contact and Account that initiated or received the session. If the customer has Salesforce Activity Timeline reporting requirements, we alternatively map sessions to Task records with a custom record type.

Crank CRM REST API usage information per session migrates to Salesforce Task records with custom fields indicating usage type (screenshare, recording, email campaign link click). Each Task is linked to the Contact (WhoId) and Account or Opportunity (WhatId) to preserve the accountability trail for session attribution reporting.

Demo recordings stored on CrankWheel's infrastructure are extracted via the session endpoint using the recording URL reference. We re-upload the file to Salesforce Files (ContentDocument/ContentVersion) and link it via ContentDocumentLink to the corresponding Demo_Session__c custom object record or the Contact record. The migration has a dependency on recording URL availability at the time of export; we flag any expired or deleted recordings during extraction so the customer can assess whether the recordings are still needed before we close the Crank CRM account.

Each Crank CRM demo session is tied to an account owner who initiated it. We map the owner reference to Salesforce User by email lookup. Any Crank CRM Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId is required on most standard Salesforce objects.

Crank CRM Pipelines exist only if the CRM module is active. Each pipeline maps to a Salesforce Opportunity Record Type with a corresponding Sales Process that whitelists the relevant stage values. We detect pipeline count and stage names during the schema audit and configure them in the Salesforce Sandbox before migration begins.

Crank CRM Deals, present only if the CRM module is enabled, map to Salesforce Opportunity. The Crank CRM deal stage maps to Salesforce StageName via the Sales Process configured from the Pipeline mapping. Deal amount, close date, and owner migrate to Opportunity Amount, CloseDate, and OwnerId respectively.

Where CRM modules are active, custom fields on Contacts or Organizations are detected during the schema audit and mapped to equivalent Salesforce custom fields. We pre-create the destination custom fields with correct Salesforce data types (text, picklist, number, date) in the Sandbox before migration begins. Custom field API names in Salesforce follow the __c suffix convention matched to the Crank CRM field names.

Files shared during a Crank CRM demo session are extracted via the session endpoint and re-uploaded to Salesforce Files (ContentVersion). We create ContentDocumentLink records linking the file to the related Contact, Account, or Demo_Session__c record. File size and original filename are preserved in Salesforce ContentVersion metadata.

If Crank CRM tracked email campaign link clicks associated with demo invites, we map these to Salesforce Campaign records with CampaignMember entries linked to the corresponding Contacts. Campaign Type is set to Email and Member Status reflects the engagement outcome (Sent, Opened, Clicked).

Session templates (reusable screen-sharing configurations) do not have a direct Salesforce equivalent in Sales Cloud. We document each template's configuration (sharing method, recording settings, invite flow) in a written handoff for the customer's admin to recreate as a Salesforce Flow or a guided setup checklist. This is not a code migration; it is a configuration inventory deliverable.