Migrate from Crank CRM to HighLevel

Crank CRM Contacts captured during demo sessions or viewer flows map to GoHighLevel Contact records. We extract the contact's name, email address, phone number, and any associated metadata from the session endpoint and map them to the equivalent GoHighLevel contact fields. If CRM modules are inactive on the source account, only screen-share-obtained contacts migrate; the schema audit at migration start determines the contact volume and field completeness.

Crank CRM Organizations stored in the screen-sharing session context map to GoHighLevel Account records. The organization name and any associated domain or session metadata migrate. GoHighLevel Account records must be created before Contact import so that Account lookups can be resolved during the contact insert phase.

Each Crank CRM demo session is tied to an account owner who initiated it. We resolve owners by email match against the GoHighLevel destination User table. Any Crank CRM owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Crank CRM Pipelines and their stage definitions migrate to GoHighLevel Pipelines configured in the destination account before any Deal or Opportunity data moves. We create GoHighLevel pipeline stages with names and order matching the source, and assign stage probabilities if they exist in Crank CRM.

Crank CRM Deals attached to Organizations and Contacts map to GoHighLevel Opportunities. We resolve the Account lookup (from the mapped Organization) and the Contact lookup at migration time. The Deal's stage maps to the corresponding GoHighLevel pipeline stage within the pre-configured Pipeline. Deal value and expected close date migrate directly.

Where CRM modules are active on Crank CRM and custom fields exist on Contacts or Organizations, we detect them during the schema audit phase and pre-create equivalent GoHighLevel custom fields of matching type before migration. Contact custom fields and Opportunity custom fields are created separately per GoHighLevel's object-scoped custom field model. The customer's admin must confirm which fields are actively used versus deprecated before we migrate them.

Crank CRM Demo Sessions have no direct GoHighLevel equivalent. We split the session data into two destinations: session metadata (start time, end time, viewer count, sharing method, recording availability) migrates as a GoHighLevel Contact activity record; the recording URL and any shared file links re-upload to GoHighLevel file storage and are attached to the Contact record as documents. If recording URLs are expired or deleted, we flag the broken link rather than cause a migration failure.

Crank CRM usage information per session (screen share vs. recording vs. email campaign type) migrates to GoHighLevel Activity records attached to the corresponding Contact. The activity type maps to GoHighLevel's activity classification, and the original timestamp is preserved for historical ordering.

Demo recordings and any files shared during a Crank CRM session are extracted via the session endpoint and re-uploaded to GoHighLevel document storage. Each document is linked to the Contact record that initiated or received the session. The migration carries a dependency on the recording URL being live at the time of export; we run the file extraction phase early in the migration window to maximize the window before link expiration.