Migrate from Snapforce CRM to Freshsales

Snapforce Accounts map directly to Freshsales Account records. The Account Name, Website, Industry, Phone, and Address fields migrate by label match. Account is the first object imported because Contacts and Deals both carry AccountId lookups that must be satisfied at insert time. Custom fields on Snapforce Accounts are captured during discovery and recreated as custom fields in Freshsales before import begins.

Snapforce Contacts map to Freshsales Contacts with the contact-account linkage preserved via the AccountId lookup. The Snapforce Mailbox email syncs map to Freshsales's built-in email tracking on Contact records. We migrate the full name, email, phone, title, address, and owner assignment. Custom Contact fields replicate by label match. Duplicate contacts are flagged using email as the dedupe key per Freshsales import settings.

Snapforce Leads are a separate module with their own lifecycle and custom lead fields. They map to Freshsales Lead records with first name, last name, email, phone, company, and any custom fields preserved. The lead status values in Snapforce map to Freshsales lead status picklist values that we configure during the Freshsales setup phase. Lead conversion rules in Freshsales are configured separately by the customer's admin after migration.

Snapforce Opportunities map to Freshsales Deals. The pipeline stage names from Snapforce are captured and recreated as Freshsales Deal stages during configuration. Amount, close date, probability, owner, and associated Account all migrate. Snapforce custom fields on Opportunities (stage-specific properties, product lines, deal sources) are recreated as custom fields in Freshsales before Deal import. The deal-account linkage is preserved by resolving AccountId at migration time.

Snapforce Activities include call logs (auto-written by VoIP), tasks, and meetings. These split into Freshsales Tasks (call logs, tasks, notes) and Events (calendar meetings). Call disposition, duration, and timestamp migrate to Task custom fields. Meeting location, start/end time, and attendee list migrate to Event records. The parent record linkage (Contact, Account, or Deal) is preserved by resolving the WhoId and WhatId at migration time. Tasks and Events are among the last objects migrated to ensure all parent records exist first.

Snapforce Documents attached to Accounts, Contacts, and Deals migrate to Freshsales Notes with file attachments. We export documents to local storage, preserve the parent record linkage by filename convention, and re-attach them to the corresponding Freshsales Contact, Account, or Deal record. Document metadata (creation date, author) migrates as note body text if the destination supports it.

Snapforce Users with role assignments and data ownership map to Freshsales Users. We export the user list by email and map each to a corresponding Freshsales User provisioned by the customer's admin before migration begins. Owner assignment on Contacts, Deals, and Leads references the User email match. Any Snapforce Owner without a Freshsales User counterpart goes to a reconciliation queue for admin provisioning before record import resumes.

Voicemail audio files stored per-user mailbox in Snapforce (up to 500 per mailbox) are not structured data exports. We extract voicemail metadata (timestamp, duration, caller ID) and the audio file, preserve the contact linkage by filename or metadata tag, and re-associate the audio file as an attachment on the corresponding Freshsales Contact record. This process is manual per-file and must be scoped explicitly before migration because it significantly affects timeline for accounts with large voicemail archives.

Snapforce Campaigns are an add-on module ($8/user/month above base CRM) containing target audiences linked to Leads and Contacts. We map Campaign membership records to Freshsales Campaign membership by resolving the contact and lead email lookups at migration time. Note that Freshsales does not migrate Sequences, Workflows, or Webforms — these are delivered as a written rebuild inventory. Campaign import is conditional on the customer confirming the Campaigns add-on was active at the time of data collection.