Migrate from Crank CRM to Zoho CRM

Crank CRM Contacts captured during demo sessions or via the screen-sharing viewer flow map directly to Zoho CRM Contact records. Email, phone, name, and company association migrate as standard fields. Any demo history attached to the Contact (sessions attended, recordings viewed) migrates as a custom multi-line text field or as linked Task records, depending on the customer's preference for activity tracking. Owner assignment maps from Crank Owner to Zoho CRM User lookup.

Crank CRM Organizations stored within demo-session context extract to Zoho CRM Account records. The Organization name becomes the Account Name field, and any company-level metadata from the session (industry, size, website if captured) migrates to the corresponding Account fields or custom fields. We resolve the Organization-to-Account relationship before Contact migration so that AccountId is available as a lookup on each Contact.

Demo Sessions are the primary data entity in Crank CRM. We offer two migration strategies: map each session to a Zoho CRM Task or Event (preserving start/end timestamp, viewer count, recording URL, and sharing method as custom fields on the activity), or create a custom Demo Sessions module in Zoho CRM to keep demo history separate from standard CRM activities. The customer selects the strategy during scoping. Recording availability and viewer count migrate as custom numeric and checkbox fields.

Crank CRM Usage Logs exposed via the RESTful API map to Zoho CRM Task records. Each log entry's session type (screen share, recording, email campaign) becomes the Task Subject or a custom picklist field, and the timestamp becomes ActivityDate. Usage volume and session duration migrate as custom numeric fields on the Task for reporting in Zoho Analytics.

Each Crank CRM demo session is tied to an account owner who initiated it. We resolve Crank CRM Owners by email match against Zoho CRM User records. Any Crank Owner without a matching Zoho User enters a reconciliation queue for the customer's admin to provision before record migration continues. OwnerId on Zoho CRM records (Contact, Account, Task) is set at migration time using the resolved User record.

Custom fields on Contacts or Organizations exist only if the customer has activated CRM modules in Crank CRM. We detect these during the pre-migration schema audit and create equivalent custom fields in Zoho CRM before data import. Field types (text, picklist, numeric, date, checkbox) are matched during the schema audit. Custom field API names in Crank CRM are preserved as Zoho CRM custom field names with the underscore-C naming convention if the customer uses Zoho's self-service migration wizard.

Pipelines and Stages exist only if the customer has activated CRM modules on Crank CRM. We flag them during scoping. Each Crank CRM Pipeline becomes a Zoho CRM Pipeline (in the Deals module or a custom module depending on the customer's Zoho edition). Stage names and order migrate to Zoho stage definitions, and stage probabilities migrate as percentage values in the Pipeline configuration. If no CRM modules are active, this object does not exist and is not mapped.

Demo recordings are stored externally on CrankWheel's infrastructure and linked via URL reference in the session record. We extract recording files via the session endpoint and re-upload them to Zoho CRM's native attachment storage or Zoho WorkDrive during migration. The recording URL migrates as a custom URL field on the parent record (Task, Event, or custom Demo Session module). Expired or deleted recordings result in broken links rather than data loss; we document any URLs that return errors at migration time.

Deals exist only if the customer has activated CRM modules in Crank CRM. If present, Deal records map to Zoho CRM Deal records. Deal name, amount, stage, close date, and owner assignment migrate as standard Deal fields. Pipeline association maps to the Zoho CRM Pipeline configured during the pipeline discovery phase. We flag Deals during scoping and include them in the migration scope only if CRM modules are confirmed active.

Any custom objects created in Crank CRM's optional CRM layer map to Zoho CRM custom modules. We conduct a schema audit during discovery to enumerate all active custom objects, their fields, and any lookup relationships to standard objects. Custom module names and field API names are preserved as Zoho CRM custom module and custom field names. Lookup relationships are re-created in Zoho CRM before data import so that referential integrity is maintained during the migration.