Migrate from HaystackCRM to Zoho CRM

HaystackCRM has no separate Lead object — all prospects live as Contacts with an Opportunity temperature priority (Hot, Warm, Cold). We establish a split rule at scoping: Contacts with at least one linked Hot or Warm Opportunity with a dollar value above a customer-defined threshold become Zoho Leads (with the Opportunity name as the Lead Company and the contact details migrated). Contacts with existing customer status (closed-won Opportunity or no Opportunity but with historical engagement) become Zoho Contacts attached to a Zoho Account. The original HaystackCRM contact record ID is preserved in a custom text field haystack_id__c on both Lead and Contact for audit and reconciliation.

HaystackCRM Companies map directly to Zoho CRM Accounts. The company name becomes the Account Name field; address, phone, and website migrate to the standard Account fields. We import Accounts first in every migration because Zoho Contacts require an AccountId Lookup reference. Account is the dedupe key; HaystackCRM company IDs are stored in a custom field haystack_company_id__c for cross-system audit.

HaystackCRM Opportunities map to Zoho CRM Deals. The opportunity name becomes Deal Name; dollar value maps to Amount; stage name maps to Stage in Zoho (with a custom picklist we configure to match Haystack's stage names); temperature priority maps to a custom picklist field Temperature__c. Contact linking in Zoho Deals requires the Contact Role feature to be enabled on the deal. We set a default Contact Role of Decision Maker unless the customer specifies otherwise during scoping.

HaystackCRM pipeline stages (typically Prospect, Qualified, Proposal, Negotiation, Closed Won, Closed Lost) are read from the exported Opportunity CSV and re-created as Zoho CRM Deal Stage picklist values. We configure these before migration in the destination Zoho instance using Zoho Setup > Pipeline. Stage probability percentages are set per stage; the customer provides the target probabilities or we default to Zoho's standard probability matrix.

HaystackCRM Tasks export with their parent record linkage (Contact or Opportunity ID in the CSV). We import Tasks after both the Contact-Lead split and the Account-Contact mapping are validated, resolve the parent Zoho record ID via lookup, and attach each Task to the corresponding Zoho Contact or Deal. Task Status, Priority, and Due Date migrate directly. Task Owner maps by email match to a Zoho User record.

HaystackCRM Events (calendar-bound records) export as date-bound entries. We import them into Zoho CRM Events with Subject, Start DateTime, End DateTime, and Location preserved. Attendee information in HaystackCRM Events is linked to the corresponding Zoho Contact via Event Relation records. Calendar sync links (device calendar connections) cannot be reconstructed in Zoho and must be rebuilt manually in the Zoho Calendar integration settings post-migration.

HaystackCRM uses a flat tag model with no hierarchy. Tags export as comma-separated string values per Contact, Company, or Opportunity record. We map these to Zoho CRM Tags (module-scoped, flat) or to a custom multi-select picklist field Tag_List__c on the relevant module, depending on the customer's preference. Tags used for lead scoring or segmentation are preserved as a custom field Segments__c rather than relying solely on the tag system, since Zoho Tags have no native reporting aggregation at the tag level.

HaystackCRM Item/Catalog records map to Zoho CRM Products. Product Name, SKU (hs_sku), Unit Price, and Product Category migrate to the standard Product fields. We import Products before Line Items if the customer is migrating any linked Deal-to-Product relationships. Zoho supports multiple Product Categories that map from Haystack's catalog grouping.

HaystackCRM Users export with name, email, and role. We match each user by email against the Zoho CRM destination User table. If a Zoho User account does not exist for a given email, the record goes to a User reconciliation queue; the customer's Zoho admin must provision the User before record import can resume (because OwnerId is a required reference on Leads, Contacts, and Deals). Active and inactive status is preserved from HaystackCRM during scoping.

HaystackCRM file attachments are stored via Dropbox, iCloud, or OneDrive integration links. We export the attachment reference URLs from the CSV and store them in a custom URL field Attachments_Link__c on the parent Zoho record (Contact, Account, or Deal). Customers must verify that the linked cloud storage remains accessible post-migration; we cannot migrate the files themselves through the CSV import mechanism. We document the full list of attachment URLs in the pre-migration scope document.

HaystackCRM Quotes generated from Opportunities export with line items and PDF link references. We import Quote headers and line items into Zoho CRM Quotes, linking each Quote to the corresponding migrated Deal. The original PDF links stored in HaystackCRM are preserved in a custom text field Original_Quote_URL__c on the Zoho Quote. The Quote PDF itself does not transfer because HaystackCRM does not expose PDF content via export.