Migrate from Sharpspring to Zoho CRM

SharpSpring contacts with lifecycle_stage = 'customer' or 'opportunity' route to Zoho CRM Contacts. All other lifecycle stages (subscriber, lead, MQL, SQL) route to Zoho CRM Leads. The routing decision is made at migration time based on the final lifecycle_stage value on each SharpSpring record. We preserve the original SharpSpring lifecycle stage value in a custom field (Lifecycle_Stage__c) on both the Zoho Lead and Contact record so no stage history is lost.

SharpSpring Companies map directly to Zoho CRM Accounts. The company name becomes Account Name, domain becomes Website, industry maps via value mapping against Zoho's industry pick-list, and annual revenue maps to Annual Revenue. SharpSpring parent-company hierarchies map to the Zoho Account ParentId field — the parent Account must be migrated first and we flag circular references before the run.

SharpSpring supports N:N contact-to-company associations natively. Zoho CRM contacts have one primary Account lookup plus Account Contact Relations for secondary associations. We migrate the primary company (most recently modified in SharpSpring by default, or your specified rule) as the Contact.Account lookup and surface remaining associations as Zoho Account Contact Relations.

SharpSpring Deals map to Zoho CRM Deals with deal name → Deal Name, amount → Amount, close date → Close Date, and owner → Deal Owner resolved by email match. Pipeline stages map value-by-value to Zoho stage pick-list values for each deal's pipeline. The deal's primary company becomes the Account lookup in Zoho — the Account must exist first in the migration sequence.

Each SharpSpring deal pipeline maps to one Zoho CRM Deal Pipeline. Zoho allows multiple pipelines with their own stage configurations. We create Zoho pipelines matching SharpSpring pipeline names and configure each stage's probability and forecast category to match SharpSpring's stage settings. Stage order is preserved from the source pipeline configuration.

Zoho CRM has no native lifecycle stage equivalent. SharpSpring lifecycle_stage values (subscriber, lead, MQL, SQL, customer, evangelist) are preserved as a custom pick-list field (Lifecycle_Stage__c) on both Lead and Contact modules. The pick-list values are created to match SharpSpring's exact values. Stage-changed timestamps are stored in a companion custom datetime field.

SharpSpring lead scoring values (numeric engagement scores) migrate to a custom Number field (Lead_Score__c) on Zoho Contacts and Leads. If SharpSpring uses fit-score and engagement-score separately, both are stored as custom fields in Zoho. We do not migrate the scoring model logic itself — that requires Zoho workflow reconstruction.

SharpSpring VisitorID tracking stores page visits, referrer data, and anonymous visitor profiles on contact records. This data migrates as a multi-line text custom field (Visitor_Tracking_Data__c) on Zoho Contacts. We preserve the raw tracking data as a JSON string so it is readable in Zoho but not natively processed by Zoho analytics.

SharpSpring logged calls, emails, and notes map to Zoho CRM Tasks. Task Subject carries the activity type, Description carries the body content, and the original timestamp is preserved. Task status is set to Completed on migration. The related Contact or Lead lookup is resolved by matching the SharpSpring contact ID to the migrated Zoho record ID stored in our source-system ID field.

SharpSpring scheduled meetings map to Zoho CRM Events with Subject, Start DateTime, End DateTime, and location preserved. The invitee list (contact names) migrates as Event attendees. Original create date is stored as a custom datetime field since Zoho Events use the record creation date as the audit timestamp.

SharpSpring file attachments on contacts, companies, and deals are downloaded and re-uploaded to Zoho CRM's attachment storage. Zoho's per-file size limit is 10 MB for files attached via the API; larger files are flagged for manual re-upload. We preserve the original file name and attach each file to the corresponding Zoho record using the record ID resolved from our migration mapping table.

SharpSpring form submissions are recorded as engagement events with form name and submission timestamp. This contextual data migrates as a custom text field (Form_Submission_Source__c) on the Zoho Contact record, storing the form name and date as a concatenated value. The full submission data (field-level form answers) is preserved as a JSON blob in a notes attachment.

SharpSpring email campaign membership and send/open/click data has no direct Zoho CRM equivalent. We create a custom module (Campaign_History__c) that stores campaign name, send date, open count, click count, and contact ID as a lookup. This preserves campaign attribution data for reporting even though the campaign itself (and its automation triggers) cannot migrate.

SharpSpring owner assignments on contacts, companies, and deals are resolved by matching the owner's email address against Zoho CRM users. Unmatched owners are flagged before migration with a pre-flight report. You can invite unmatched users to Zoho CRM before the run, or assign their records to a fallback owner — no record lands without a Zoho owner assigned.