Migrate from Sierra Interactive to Zoho CRM

Sierra's Lead object maps directly to Zoho's Lead module. The Lead's standard fields (first name, last name, email, phone, address) map to Zoho's corresponding fields by name. After migration, your team can convert individual Leads to Contacts in Zoho at a time of your choosing — Sierra does not have a separate Contact object, so all records arrive as Leads.

If your Sierra configuration uses a lifecycle or status field to indicate a converted client, FlitStack can split records at migration time: records with a 'Customer' or 'Client' status value route directly to Zoho Contacts rather than Leads, bypassing the Lead-to-Contact conversion step. This split is configurable based on your Sierra status field values — we document the split logic in the migration plan before execution.

Sierra Lead Ponds are groupings of leads managed together — commonly used for team-based lead distribution. Zoho has no native Pond equivalent. We create a custom 'Lead_Ponds' module with fields for Pond name, description, and member lead count, and populate each pond as a record. Individual lead-to-pond associations are stored as a multi-select lookup field on the Lead record pointing back to the Pond.

Sierra notes attached to leads (retrieved via GET /getLeadNotes) map to Zoho Notes with the parent Zoho Lead ID linked via the Related_To field. Original note body, created date, and owning user are preserved. Rich-text formatting in Sierra notes is flattened to plain text to avoid rendering issues in Zoho's Notes editor.

Sierra lead tasks (created via POST /addLeadTask or retrieved via GET /findLeadTasks) migrate as Zoho Tasks with the Subject, Due Date, Status, and Priority fields mapped. The task is linked to the migrated Zoho Lead record. Task owners are resolved by email match against Zoho Users — any unmatched owners are flagged and assigned to a fallback owner you designate before the migration runs.

Sierra Saved Listings (returned via GET /savedListings per lead) have no Zoho native equivalent. We create a 'Saved_Listings' custom module in Zoho with fields for Property_Address, Property_Price, Listing_Status, Property_URL, and a Contact lookup pointing back to the migrated Zoho Contact. Custom module files use the _C naming convention so Zoho recognizes them automatically during import. If your Sierra account stores property fields beyond these standards, we create additional custom fields in the module before writing data.

Sierra Saved Searches store a lead's property criteria (price range, bedrooms, area, etc.). We create a 'Saved_Searches' custom module in Zoho with criteria fields (Price_Min, Price_Max, Beds_Min, Area, etc.) and a lookup to the Contact. Search criteria values that don't map directly to Zoho pick-lists are stored as free-text custom fields.

Sierra lead sources (website form, Zillow, Realtor.com, referrals, etc.) are stored as a pick-list value on the lead. We map Sierra's source values to Zoho's Lead Source pick-list on a value-by-value basis. Any Sierra source values that don't match Zoho's pick-list options are flagged — your admin chooses whether to add new pick-list values to Zoho or consolidate them under an 'Other' value.

Sierra agents (retrieved via GET /findUsers or GET /findAgents) carry name, email, phone, and office association. We map Sierra agents to Zoho Users by email matching — the email address is the unique key. Before migration, we export your Zoho Users list and reconcile against Sierra's agent list. Agents that exist in Sierra but not in Zoho are flagged; your team creates their Zoho accounts first or assigns their records to an existing user.

Sierra records property views as events (via POST /addPropertyView) capturing the property ID, date/time, and lead association. These migrate to Zoho Events with Subject set to the property address, Start_DateTime and End_DateTime preserved, and the Zoho Lead lookup linked. If the property URL is available, we store it in the Event description field.

Sierra WebHook subscriptions are URL-based notification endpoints for real-time lead event delivery. Zoho has its own Webhooks and extension notification system with different configuration interfaces. WebHook subscriptions cannot be migrated and must be re-created manually in Zoho under Settings > Developer Space > Webhooks. We provide a list of all active Sierra WebHook URLs as a reference for your admin to re-enter in Zoho.

Sierra Action Plans are automated sequences of emails, texts, ringless voicemails, and task tasks tied to lead behavior or time delays. These represent workflow logic with no direct equivalent in Zoho CRM's Blueprint or Workflow Rules models. FlitStack AI does not migrate Action Plans. We export your Action Plan definitions (step names, triggers, delay times, content references) as a structured reference document so your Zoho admin can reconstruct the logic in Blueprint or Workflow Rules after migration.