Migrate from Spotler Mail+ to Zoho CRM

Spotler Mail+ Contacts map directly to Zoho CRM Contacts. Standard fields (first name, last name, email, phone, address) migrate 1:1. We create a corresponding Account record for each Contact during migration using the contact's company domain as the Account name, then link Contact to Account via the Account Name lookup. This resolves the data model difference where Spotler stores company data as contact fields and Zoho separates Account as a distinct object.

The company name field from each Spotler Contact becomes an Account in Zoho CRM. We extract the company domain from the email address when no explicit company name is present, create one Account per unique company, and resolve the AccountId on the Contact record at migration time. If multiple Spotler contacts share a company, they link to the same Account.

Spotler Contact tags map 1:1 to Zoho CRM Tags. Tags are a native object in both platforms. We extract all unique tag values from the Spotler contact export, create the corresponding Tags in Zoho before Contact import, and apply them via the tag association during the contact insert phase. Tag-based segmentation in Spotler translates to Tag filtering in Zoho Views.

Spotler lead scores migrate as a numeric custom field on the Zoho CRM Contact object. If the destination Zoho CRM has Zoho Bigin or SalesIQ scoring enabled, we configure a corresponding scoring model in Zoho using the imported score values as baseline data points. Score thresholds and tier labels from Spotler are documented separately for the admin to configure in Zoho.

Spotler custom field types (text, numeric, currency, list, date, date of birth, permission) map to Zoho CRM field types with equivalent behavior. Text maps to Single Line or Multi Line; numeric and currency map to Number or Currency fields with decimal precision preserved; list maps to Picklist or Multi-Select Picklist; date and date of birth map to Date fields. Permission fields map to Checkbox fields representing consent status.

Spotler audience segments do not export as automation rules. We extract the resulting contact sets (the contact IDs belonging to each segment) and migrate them as Zoho CRM Views filtered by Tag, Score, or Custom Field values that define the segment. The customer receives a mapping document that lists each Spotler segment name and the Zoho View filter criteria that reproduces it. Segment rebuild requires manual configuration in Zoho.

Spotler form submissions are flat records linked to contacts. We denormalize form submission data into Zoho CRM Notes attached to the Contact, or into a custom Form_Submissions module if the submission data includes multiple fields that warrant a related record. Survey closure rules (date-triggered or quota-triggered) do not export and are documented for manual rebuild.

Spotler mailing interaction data (opens, clicks, delivery stats) migrates to Zoho CRM Activity records linked to the Contact. We scope the export to the 24-month window because Spotler anonymizes interactions older than 24 months. Each mailing becomes a Call or Event activity record with the subject, send date, and engagement metrics preserved as custom activity fields. Automated campaign logic does not migrate as executable rules.

Spotler email templates are platform-native assets with drag-and-drop layouts that do not export as portable HTML. We extract the template content, images, and text as HTML/CSS assets for manual reassembly in Zoho CRM's Email Templates module. The customer receives a template inventory document listing each Spotler template with its content summary and recommended Zoho template structure.

Spotler user accounts with role assignments migrate to Zoho CRM Users. We extract user name, email, and role level. Spotler role levels map to Zoho CRM profiles (Standard, Professional, or Administrator) and the customer configures the specific permission set in Zoho during the initial setup. Users without email matches in the destination Zoho org are flagged for manual provisioning before record import.