Migrate from Snapforce CRM to Salesforce Sales Cloud

Snapforce Accounts map directly to Salesforce Account. The Account Name, Industry, Website, Phone, and Billing Address fields migrate with direct field-to-field mapping. Custom fields on the Snapforce Account module are captured by label during discovery and rebuilt as Salesforce custom fields with matching labels. The Account object must be imported before Contact because AccountId is a required lookup on Contact.

Snapforce Contacts map to Salesforce Contact with AccountId resolved via Account name matching. The Snapforce Mailbox email threads link to Contact via the email address; we map email history to Salesforce Task records with Subject containing the thread ID for audit traceability. Primary address from Snapforce maps to Contact MailingAddress; secondary address to OtherAddress. Custom Contact fields migrate by label match.

Snapforce Leads map to Salesforce Lead with direct field mapping on standard properties (FirstName, LastName, Company, Email, Phone, LeadSource). If the customer has been converting Snapforce Leads to Account/Contact, we identify converted records during scoping and route them as Contacts with AccountId resolved; unconverted records land as Salesforce Leads. Lead Status maps from Snapforce's lead stage values to Salesforce standard Lead Status values.

Snapforce Opportunities map to Salesforce Opportunity. StageName migrates from Snapforce's deal stage; Probability migrates from the deal probability field. CloseDate maps from the Snapforce expected close date. Amount maps from the deal value. Custom Opportunity fields migrate by label match. If the customer has multiple pipelines in Snapforce, each pipeline becomes a Salesforce Record Type with a corresponding Sales Process configured before migration.

Snapforce auto-logs call metadata (duration, timestamp, disposition) to Contact records. These migrate as Salesforce Task records with TaskSubtype=Call, CallDurationInSeconds preserved, and CallDisposition in a custom field. Email sync activity from Snapforce Mailbox migrates as Salesforce Task records with Subject and Description populated. Meeting activities migrate as Salesforce Event records with StartDateTime, EndDateTime, and Location preserved.

Snapforce Documents linked to deals, persons, or organizations migrate as Salesforce ContentDocument records attached via ContentDocumentLink to the parent record (Account, Contact, Opportunity). Snapforce's Google Drive sync exports documents to local storage during extraction; we preserve the Google Drive file URL in a custom field on ContentDocument for reference. Documents without a parent record link are attached to a migration holding Account for manual reassignment.

Snapforce Campaigns is a separate $8/user/month add-on above the base CRM tier. Campaign records containing target audiences linked to Leads or Contacts migrate to Salesforce Campaign with CampaignMember records representing membership. We verify during scoping whether Campaign data exists and confirm the customer has the add-on active because base-tier Snapforce customers do not have Campaign records. Campaign influence data migrates to Salesforce Campaign Influence if the destination org has the feature enabled.

Snapforce User records carry role assignments and tie to data ownership. We export the user list and map each Snapforce user to a corresponding Salesforce User by email match. Snapforce's per-owner CSV export requirement means we identify every distinct owner referenced across Account, Contact, Lead, and Opportunity records before migration. Owners without a matching Salesforce User go to a reconciliation queue for admin provisioning before record import resumes.

Snapforce voicemail audio files are stored per-user mailbox (500-voicemail cap per mailbox) as separate files linked to Contact records by filename convention. These are not structured data and are not exported via Snapforce's standard CSV export. We extract voicemail metadata (timestamp, duration, disposition, contact name) as Salesforce Task records, and the audio files are extracted from Snapforce and re-associated via ContentDocumentLink to the parent Contact. This process is scoped explicitly during discovery because it requires per-file handling and a file storage decision at the destination.

Snapforce supports custom fields across all modules, created during import mapping or in settings. Custom field IDs in Snapforce are scoped to the organization and cannot be referenced in Salesforce. We capture the full custom field schema (label, API name, data type, picklist values) for each module during discovery and rebuild the definitions in Salesforce by label match before any data import. Any workflow rules referencing these fields in Snapforce are documented in the Workflow inventory for rebuild in Salesforce Flow using the new field IDs.

Snapforce Workflow automation rules fire on record create/edit/delete events within a single module. They reference internal field IDs that are not portable and cannot be exported as portable data. We do not migrate Workflows. We deliver a written inventory of every active Snapforce Workflow with its trigger, conditions, and actions for the customer's Salesforce admin or a Salesforce partner to rebuild in Flow. Workflow rules that span multiple modules (cross-object) will require redesign because Snapforce's single-module trigger model does not map directly to Flow's multi-object orchestration.

Snapforce Territory Management is a $5/user/month add-on above the base CRM tier and requires the Campaigns add-on for full feature access. Territory assignment records in Snapforce migrate to Salesforce Territory Management (available in Enterprise and Unlimited tiers of Sales Cloud). We verify during scoping whether Territory data exists and confirm the customer's Salesforce edition supports it because Territory Management is not available in Professional tier.