Migrate from Sales Mantra to Zoho CRM

Sales Mantra Lead records map directly to Zoho CRM Leads. Standard contact fields (name, email, phone, company, source attribution, status) transfer to Zoho standard fields. The Lead Owner assignment migrates by resolving the Sales Mantra Owner name to the corresponding Zoho User via email match. Any Sales Mantra Lead status values not present in the Zoho standard Lead Status picklist are added as custom picklist values before migration.

Sales Mantra Account records (representing organizations) map to Zoho Accounts. Account name, address, industry classification, website, and any exported custom fields transfer to Zoho standard Account fields. The Account is the parent record created before any Contact import so that the Account-Contact lookup relationship is satisfied at insert time.

Sales Mantra Contact records map to Zoho Contacts with a direct lookup to the parent Account. First name, last name, email, phone, title, and department transfer to Zoho standard fields. The Contact-Account relationship is resolved by matching the Sales Mantra Contact's associated Account name or ID to the Zoho Account created in the prior phase.

Sales Mantra Deal records map to Zoho Deals. Deal name, value, expected close date, owner assignment, and associated Account and Contact lookups transfer to Zoho. The pipeline stage mapping is designed during the data audit phase: Sales Mantra custom stage names are normalized to Zoho stage values, and any missing stage values are added to the Zoho pipeline picklist before migration.

Sales Mantra Activity records do not have a uniform sub-type structure in CSV export. During the data audit we classify each activity row by examining field presence: records with duration and call disposition fields map to Zoho Calls; records with start and end timestamps map to Events; records with a due date and status map to Tasks; records with a body text and no temporal fields map to Notes. The classification is validated against the source data before each Zoho import batch is executed.

Sales Mantra contact classification fields may export as delimited multi-value columns (comma-separated or pipe-separated) or as non-standard string formats. We split these columns into normalized rows during the transform phase and create corresponding Zoho multi-select picklist fields to hold the classification values. The original raw export value is preserved in a text field for reconciliation. This step is verified during the data audit before any Zoho schema changes are finalized.

Sales Mantra assigns Deals and Activities to named Owners. We extract the distinct Owner roster from the exported records, match by name or email to existing Zoho Users, and hold any unmatched owners in a reconciliation queue for the customer's Zoho admin to provision. Owner resolution must complete before Deal and Activity imports begin because OwnerId is a required reference on those records.

Sales Mantra document attachments linked to Accounts or Deals may export as URLs or file reference paths rather than binary files. We attempt to extract all reachable file URLs from the export. Files that are unreachable or stored internally without an export path are flagged in the data audit report, and we recommend the customer download critical documents manually or request a bulk file export from Sales Mantra before the migration cutoff date.

Each unique Sales Mantra pipeline stage value in the exported Deals is documented and added to the Zoho Deals pipeline picklist before migration. Stage probability percentages are approximated based on typical Sales Mantra deal lifecycle patterns (if explicit probability data is not exported) and configured on the Zoho pipeline. This ensures Deal stage values are valid picklist entries and not rejected by Zoho validation during import.

Sales Mantra instances that use a separate product catalog export Product records (name, SKU, unit price) to a Products CSV if the feature is active. These map to Zoho Products with Standard Price Book entries. If the Sales Mantra export does not include a Products object, we skip this mapping and note the absence in the scope confirmation. Product-to-Deal line-item associations require the Products import to complete before Deals can be updated with line items.