Migrate from Snapforce CRM to Zoho CRM

Snapforce Accounts map directly to Zoho CRM Accounts module. The Account Name, Website, Industry, Phone, and Address fields map to their Zoho equivalents by field label. Account is the top-level object with no parent dependencies, so we import it first in the migration sequence. Custom fields on Snapforce Accounts migrate as custom fields in Zoho, which must be created before import; we capture the field label and data type from Snapforce during discovery and create the corresponding Zoho field upfront.

Snapforce Contacts map to Zoho CRM Contacts with a mandatory Account lookup. We resolve the Contact-to-Account relationship using the account_name or account_id field from Snapforce, creating the Account in Zoho first if it does not exist. Snapforce Mailbox email threads linked to the Contact record (not the email content itself) migrate as Tasks with a note flagging that the full email body is preserved in Zoho's Email module only if the customer uses Zoho's native email integration. The 2-way mail sync configuration does not migrate and must be re-established in Zoho by the customer's admin.

Snapforce Leads map to Zoho CRM Leads with their own lifecycle (Lead Status, Rating, Source). Lead custom fields migrate as Zoho custom fields on the Leads module. If the customer has been using Lead conversion in Snapforce, any converted Leads will have been written to Account/Contact records; we deduplicate by email during import so that a Lead and a Contact with the same email address do not create duplicate records in Zoho.

Snapforce Opportunities map to Zoho CRM Deals. Pipeline stages from Snapforce map to Zoho Deal Stage values; we capture the stage name, probability percentage, and order from Snapforce and pre-configure the Zoho Deal layout before import. Deal Amount, Close Date, and Owner map to Zoho Amount, Closing Date, and Owner. If Snapforce has multiple pipeline definitions, we create multiple Zoho Deal pipelines and map each Snapforce pipeline to its corresponding Zoho pipeline during import.

Snapforce Activity records (call logs, tasks, meetings) map to Zoho CRM Tasks. Call disposition, duration, and timestamp from Snapforce migrate to Zoho Task custom fields. Meeting records map to Zoho Events with Start DateTime, End DateTime, and Location preserved. We set the Activity Date to the original Snapforce timestamp to maintain the historical timeline. Activity records that reference Contacts or Deals use the migrated Zoho record IDs resolved via email match and Deal name lookup.

Snapforce voicemails are audio files stored per-user mailbox with a 500-voicemail cap per mailbox. They are not structured data in the CSV export — they are files with a contact name in the filename. We extract the audio files from Snapforce, preserve the contact linkage by parsing the filename, and upload them as file attachments to the corresponding Contact record in Zoho. The contact-activity linkage that existed in Snapforce (voicemail visible in the contact's activity feed) does not carry over as a structured activity record in Zoho; the voicemail appears as a file attachment on the Contact. This is a manual per-file process that must be scoped explicitly before migration and is the primary reason audio file migrations move to a higher price tier.

Snapforce Documents uploaded to Deals, Contacts, or Accounts migrate as file attachments in Zoho CRM. We export documents to local storage, preserve the parent record linkage by filename or record reference, and re-upload them to the corresponding Zoho record. If Snapforce has Google Drive sync enabled for documents, we download the local copies and attach them directly. Documents that were shared across multiple records require duplication in Zoho because Zoho's attachment model attaches per-record, not shared.

Snapforce Users (with role assignments) map to Zoho CRM Users by email address. We export the user list and match each Snapforce user to a Zoho user by email; if the Zoho user does not exist, we hold that owner reference in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated records (Contacts, Deals, Leads) uses the User mapping. Inactive Snapforce users are mapped to inactive Zoho users to preserve historical ownership without generating new Zoho seat charges.

Snapforce Campaigns are an add-on module ($8/user/month) and may not exist in all customer accounts. We verify during scoping whether Campaign data exists. If present, Campaign records migrate to Zoho CRM Campaigns with target audiences and member status. Campaign membership (which Contacts and Leads were in which Campaign) migrates to Zoho Campaign Members linked to the migrated Contact and Lead records. If the customer does not have the Snapforce Campaigns add-on, this object is skipped.

Snapforce custom fields scoped to any module migrate as Zoho CRM custom fields on the corresponding module. Zoho enforces a limit of 300 fields per module with a maximum of 5 lookup fields. We audit the total custom field count per module during discovery; if any module exceeds 300 fields, we flag the overage and work with the customer to archive inactive fields before migration. Custom field IDs from Snapforce are not portable — we match by field label and data type during import, and any workflow rules referencing these fields in Snapforce will need to be rebuilt in Zoho using the new field IDs.

Snapforce supports custom fields across all modules but does not have a first-class custom object construct in its documented API. If the customer has records stored in a non-standard module or a custom module configuration, we create a corresponding Zoho custom module during schema setup. The Data Migration wizard in Zoho recognizes files named with a _C suffix (e.g., Properties_C.csv) as custom modules and creates them automatically. We name the import file accordingly and pre-configure the module layout before loading data.