Migrate from Crank CRM to Microsoft Dynamics 365 Sales

Crank CRM Contacts captured during demo sessions or viewer flows map to Dynamics 365 Sales Contact. Email, phone, name, and organization associations transfer to the Contact standard fields. Demo history associated with each Contact migrates as Activity records (Task with TaskSubtype=Call for calls, EmailMessage for emails, Event for meetings) linked via WhoId to the Contact. Owner assignment maps to Dynamics OwnerId by email match against the User table.

Crank CRM Organizations stored in session context map to Dynamics 365 Sales Account. The organization name becomes Account Name, and any associated session metadata (industry, size hints from session context) maps to standard Account fields or custom fields created during schema design. Account is created before Contact import to satisfy the AccountId lookup on Contact.

Demo Sessions are the primary data entity in Crank CRM with no native Dynamics equivalent. We create a custom Dataverse entity (crnk_demo_session__c) linked to the Account or Contact via lookup fields. Session start/end timestamps, viewer count, sharing method, and recording availability URL transfer as custom fields. The recording URL is extracted and re-uploaded to SharePoint or Dynamics file storage, and the new file URL replaces the CrankWheel-hosted link in the session record.

The session-level usage information from the Crank CRM RESTful API (screen share duration, recording file size, email campaign impressions) migrates to the custom demo_session__c entity as activity metrics fields, or to Note records linked to the parent Contact or Account. The customer chooses during scoping whether to store these as structured custom fields or as notes for flexibility.

Each Crank CRM demo session ties to an account owner who initiated it. Owner references map to Dynamics 365 Sales User by email lookup. Any Crank Owner without a matching Dynamics User goes to a reconciliation queue for the customer's admin to provision before record import continues. OwnerId must be resolved before Opportunity or Contact import to avoid orphaned assignments.

When Crank CRM CRM modules are active, custom fields on Contacts or Organizations are detected during the pre-migration schema audit. We create equivalent custom fields on the Dynamics Contact or Account entity with matching field types (text, number, picklist, date) before migration. Field mapping is validated in a Sandbox phase before production load.

If Crank CRM Pipelines and Stages are active, we create a custom pipeline entity in Dataverse or map the stages to Dynamics Opportunity stage values depending on complexity. For simple single-pipeline setups, we map directly to Opportunity StageName. For multi-pipeline setups with distinct stage sets, we create Record Types and Sales Processes that whitelist the relevant stage values per pipeline.

Demo recording files hosted on CrankWheel infrastructure are extracted via session endpoint URLs. We re-upload recordings to SharePoint (connected to the Account or Opportunity via the native SharePoint document management integration) or to Dynamics native file storage attached to the crnk_demo_session__c entity. The migration holds a dependency on recording URL availability at the time of export; expired or deleted recordings result in broken links rather than data loss. The customer receives a list of recordings that could not be re-uploaded for manual remediation.