Migrate from Snapforce CRM to HighLevel

Snapforce Accounts map to GoHighLevel Contacts with the company name stored in a custom company_name__c field on each Contact record. If a Snapforce Account has multiple associated Contacts, we split it into separate GoHighLevel Contact records all referencing the same company_name__c value, preserving the original account-category assignment as a tag or custom field. The Account's industry, website, and address fields map to corresponding GoHighLevel custom fields on the Contact.

Snapforce Contacts map directly to GoHighLevel Contacts. The Contact-Account lookup is resolved by matching the parent Account name to the GoHighLevel company_name__c field we set during the Account migration phase. Email address is used as the dedupe key during import. Custom fields on the Snapforce Contact module are recreated in GoHighLevel by label match before the import phase begins.

Snapforce Leads map to GoHighLevel Contacts that enter the pipeline at a designated stage (typically the first stage, 'New Lead' or equivalent). The Lead's lifecycle status, source information, and any lead scoring values stored as custom fields migrate to GoHighLevel custom fields. After migration, GoHighLevel's pipeline stages replace Snapforce's Lead status as the primary progression mechanism.

Snapforce Opportunities map to GoHighLevel Deals with the pipeline stage preserved as a GoHighLevel Pipeline stage value. We configure the GoHighLevel Pipeline to match Snapforce's stage names and probability percentages before import. Deal amount, expected close date, owner, and associated Account-Contact linkage migrate directly. Snapforce's custom pipeline stages (if multiple pipelines exist) map to separate GoHighLevel Pipelines.

Snapforce VoIP call logs (duration, timestamp, disposition, direction) map to GoHighLevel Call records linked to the Contact. Call direction (inbound/outbound) maps to GoHighLevel's call_direction field. Disposition notes from Snapforce migrate to a custom field on the Call record. Call recordings and voicemail audio files are extracted separately as file attachments and re-associated by matching the Contact name and timestamp against the Call record in GoHighLevel.

Snapforce voicemails are audio files stored per-user mailbox with a 500-voicemail cap per mailbox. We extract the audio file, identify the associated Contact by filename metadata or caller ID, and attach the audio to the corresponding GoHighLevel Call record. This is a manual per-file step that must be scoped explicitly during discovery because the voicemail audio is not accessible via the Snapforce API and requires either UI-based download or file-level extraction. The Contact linkage in GoHighLevel is resolved by matching the voicemail caller number to a Contact phone number field.

Snapforce Mailbox email threads tied to Contact records map to GoHighLevel Conversations on the Contact. Each email in a thread migrates as a separate message entry within the Conversation, preserving sender, recipient, timestamp, and body content. The Outlook-style threading structure is flattened into a linear Conversation feed in GoHighLevel. Attachments from emails migrate as file attachments linked to the Conversation.

Snapforce Tasks map to GoHighLevel Tasks with Status, Priority, due date, and assigned user preserved. Owner assignment resolves by matching the Snapforce owner email to a GoHighLevel User account. Tasks linked to a specific Contact or Opportunity carry the GoHighLevel Contact or Deal ID after parent-record resolution.

Snapforce Campaigns (add-on module at $8/user/month) map to GoHighLevel Campaigns. Campaign membership records — which Contacts and Leads were targeted — migrate as Campaign member entries in GoHighLevel. The drip email sequence logic and automation triggers within Snapforce Campaigns do not migrate as code; we document every active campaign and its sequence steps so the customer's admin can rebuild the cadence in GoHighLevel's workflow builder.

Snapforce custom fields on Accounts, Contacts, Leads, and Opportunities are recreated in GoHighLevel by label and data type match during the schema setup phase. Field IDs from Snapforce are organization-scoped and cannot be referenced in GoHighLevel. We capture the full custom field schema per module during discovery, create the corresponding GoHighLevel custom fields before import, and note that any workflow rules in Snapforce referencing these fields must be rebuilt in GoHighLevel using the new field IDs.