Migrate your Snapforce CRM data

Accounts is a top-level object in Snapforce's module list. The import module defaults to Accounts and exposes all standard fields plus any custom fields the organization has defined. We map Account fields 1:1 in most migrations.

Contacts sit below Accounts and are related via a lookup relationship. The platform supports 2-way mail sync that auto-logs emails to the Contact record. We preserve the contact-account linkage during migration and flag any contacts without a parent Account for manual review.

Leads are a separate module with their own lifecycle. Snapforce supports custom lead fields that carry over upon lead conversion to Account/Contact. We map Lead fields to the destination's equivalent Lead or Contact object and flag which custom fields require value mapping at conversion time.

Opportunities are the Deals equivalent in Snapforce, tied to Accounts and supporting custom pipeline stages, custom fields, and pipeline-specific workflows. We preserve stage names and probability assumptions, noting that stage IDs are not guaranteed to be stable across organizations.

Activities include tasks, calls, and meetings. Call logs are written automatically by the VoIP system. We handle call logs and tasks as a combined activity feed and map them to the destination's Activity or Engagement object, preserving the linked Contact/Account reference.

Documents can be uploaded to individual deals, persons, and organizations. Snapforce syncs documents with Google Drive. We export documents to local storage, preserve the parent record linkage, and re-associate them at the destination by filename and linked record ID.

Web Forms are Snapforce-hosted form configurations that capture leads into the CRM. They are configuration data, not customer records, and have no exportable record-level data. We do not migrate Web Form definitions; we recommend rebuilding them in the destination platform.

Snapforce supports custom fields across all modules, created during import mapping or in settings. We capture the full custom field schema for each module during the discovery phase and replicate the field definitions in the destination before importing data.

Workflow automation rules are configuration objects that fire on record create/edit/delete events and trigger actions. They reference module field IDs and cannot be exported as portable data. We do not migrate workflows; we document the active rules so the customer can rebuild them in the destination platform.

User records in Snapforce carry role assignments and are tied to data ownership. We export the user list and map each user to a corresponding owner in the destination, flagging any orphaned records where the original owner does not exist in the target system.

The Audit Trail logs every create, edit, delete, import, export, and association with before/after values. It is an append-only historical log and is not replayable in another system. We do not migrate audit logs; we advise the customer to export and retain them independently if required for compliance.

Snapforce offers Campaigns as a separate add-on module beyond the base CRM tier. Campaign records contain target audiences linked to Leads/Contacts. We map campaign membership to the destination's campaign or list object, noting that drip sequences may require rebuilding in the destination's automation tool.

Voicemails are stored per-user mailbox with a 500-voicemail cap per mailbox. They are audio files linked to Contact records. We extract voicemail metadata and audio files, preserving the contact linkage, and re-associate them in the destination as attachments on the Contact record.