Migrate from Spotler CRM to Zoho CRM

Spotler Contacts with a defined buyer status or assigned to a Company with active pipeline work map to Zoho Contact tied to an Account. Unqualified or early-stage contacts without pipeline assignment map to Zoho Lead. We compute the split using Spotler's contact status field and any custom lifecycle or stage property, then preserve the original Spotler status in a Zoho custom field for audit. The split rule is defined during scoping and reviewed against the customer's sales process before migration begins.

Spotler Company records map directly to Zoho Accounts. The Company name becomes Account Name, industry and size fields map to standard Zoho picklists, and the primary address fields map to Billing Street, City, State, and Country. We use Company name as the dedupe key during import. Account is created before Contact import so the Account lookup relationship is satisfied at insert time.

Spotler Opportunities map to Zoho Deals. Pipeline stage names from Spotler are collected during scoping and mapped to Zoho Stage values, which we configure in Zoho before migration. Deal value, expected close date, probability (if set), and owner all transfer directly. Spotler Opportunity custom fields map to Zoho Deal custom fields, which we create during schema setup.

Each Spotler pipeline stage becomes a Zoho Deal Stage value in the sales pipeline configuration. Stage probability percentages are set on the Zoho pipeline setup page. If Spotler uses a custom stage naming convention (Won, Lost, Quoted, Negotiation), we preserve those exact labels in Zoho and configure the Stage Won and Stage Lost flags accordingly.

Spotler Activity records (Tasks, Calls, Meetings, Notes) map to Zoho Activities. Call records become Zoho Tasks with Call Type set to Outgoing or Incoming and Call Duration in seconds. Meetings become Zoho Events with Start DateTime, End DateTime, and Location preserved. Notes become Zoho Notes linked to the parent record via the Related To field. Activity dates are preserved to maintain the chronological timeline in Zoho's Activity History tab.

Spotler Users are exported by email, name, and role. We match by email against the destination Zoho CRM User table. Any Spotler User without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Role names (Admin, Standard, Read-only) map to the closest Zoho Role configuration available in the target Zoho edition.

Spotler Quotations (Professional and Enterprise only) map to Zoho CRM Quotes. Each quotation's line items, pricing, quantity, discount, and tax fields transfer to Zoho Quote Items. Quote status (Draft, Sent, Accepted, Declined) maps to the Zoho Quote Status picklist. If the customer requires PDF output, we flag that the Zoho Quote PDF template needs to be configured post-migration.

Spotler Cases (Professional and Enterprise only) map to Zoho Cases. Case priority, status, and assignment fields transfer to the standard Zoho Cases module. SLA configuration does not migrate because it carries platform-specific logic; we document the SLA rules in a written specification for the customer's admin to rebuild using Zoho Service Desk workflows if Service Cloud is enabled.

Spotler custom fields on Contacts, Companies, Opportunities, and Quotations require explicit schema mapping. Spotler stores dropdown list values as internal reference IDs in the data export. We export the field definition table alongside the record data, then recreate each custom field in Zoho with the matching field type (text, picklist, number, date, checkbox) and repopulate the picklist value mappings before importing record values. Custom fields are created in Zoho before any data load to avoid silent failures on the first import pass.

Spotler tags applied to Contacts and Companies are exported as tag name strings per record. We create Zoho Tags with matching names and apply them to the migrated Contacts and Accounts. If Spotler uses static Lists for segmentation, we recreate these as Zoho Tags or CRM Campaigns depending on the customer's intended use. Tags are applied after the parent record import to avoid orphaned tag assignments.