Migrate from Crank CRM to Nutshell

Crank CRM Demo Sessions are the primary data entity with no direct Nutshell equivalent. We extract session timestamps, viewer count, sharing method, and recording availability from the session endpoint and write them as custom fields on the linked Nutshell Person record. Session metadata is stored in custom fields named session_date__c, viewer_count__c, and sharing_method__c. If recording links exist, we store them as text fields pending re-upload. If no linked Person record exists in Nutshell, we create a placeholder Person and attach session history as a Note linked via ContentDocumentLink.

Crank CRM contacts captured during demo viewer flows map directly to Nutshell People. Name, email, phone, and address fields migrate as typed Nutshell Person fields. We preserve the Crank CRM contact's associated demo history as a comma-separated list in a custom field demo_session_ids__c and as Note attachments on the Person record for historical reference.

Crank CRM Organizations (present when CRM modules are active) map to Nutshell Companies. The organization name, domain, and address map directly. If CRM modules are not active, Crank CRM stores organization context within the session record; we create a Nutshell Company from the session context and link it to the Person record using the company field on People.

Crank CRM demo sessions reference an account owner who initiated the session. We extract the owner by email and map to Nutshell User. If a matching Nutshell User does not exist, we add the owner to a reconciliation queue for the customer's admin to provision before the migration resumes. Owner references on session records map to the assigned Nutshell User on the linked Person.

If the Crank CRM schema audit reveals active Pipelines and Stages (optional CRM module), we map these to Nutshell Deal with a Deal Status representing the stage. Stage names and ordering migrate to Nutshell Deal fields. Because Crank CRM pipeline configuration is simple, we map each Crank CRM pipeline to a Nutshell Deal with a custom field source_pipeline__c for audit. Pipelines without Deals are documented as an empty inventory item.

Crank CRM Deals (active only if CRM modules are enabled) map to Nutshell Deal records. Deal name, amount, stage, and associated Person/Company links migrate to Nutshell Deal fields. We resolve the Person lookup in Nutshell using email as the dedupe key and the Company lookup using domain or name. Deal creation timestamps migrate as a custom field original_created_date__c.

Crank CRM usage logs (screen share count, email campaign shares, recording views) migrate to Nutshell as Activity records or Note attachments on the associated Person or Deal. Each usage log type gets a distinct custom field on the Person (e.g., screen_share_count__c, recording_view_count__c) or is written as a dated Note capturing the event summary. We preserve timestamps to maintain historical sequence.

If Crank CRM CRM modules include custom fields on Contacts or Organizations, we detect them during the schema audit and create equivalent custom fields on Nutshell People or Companies before migration. Field type mapping applies: text to text, number to number, date to date, picklist to picklist. Custom field API names in Crank CRM are matched to Nutshell field slugs by name normalization.

Demo recordings and shared files are extracted from CrankWheel's session endpoints via URL reference. We download each file and re-upload to Nutshell's attachment system, linking it to the associated Person or Deal record. The migration carries a dependency on recording URL availability at export time; if a recording URL has expired or the file has been deleted on CrankWheel's infrastructure, we record the broken link in a custom field original_recording_url__c rather than causing data loss.