Migrate from LeadSmart Channel Cloud to Zoho CRM

LeadSmart Leads map directly to Zoho CRM Leads. All standard Lead fields (Name, Email, Phone, Company, Status, Source) migrate 1:1. LeadSmart's industry-specific custom Lead fields are inventoried during scoping and pre-created as Zoho custom fields before import. The Zoho Lead Status picklist is configured to match LeadSmart's Lead Status values, with any unmapped statuses added as Zoho picklist entries during the configuration phase.

LeadSmart Contacts map to Zoho Contacts. The Contact-to-Account linking uses the same parent-account resolution strategy: Zoho Account is created first from the related LeadSmart Account, then Contact import resolves the AccountId lookup at insert time. LeadSmart's distributor and manufacturer relationship type custom fields map to a Zoho custom picklist field (Relationship_Type__c) that we configure before migration.

LeadSmart Accounts map to Zoho Accounts with parent-account hierarchy preserved for manufacturer-distributor-dealer relationships. The Account Name, Website, Industry, Billing Address, Phone, and Type fields migrate directly. If the customer's LeadSmart instance uses the Account Type field to distinguish Manufacturers from Distributors from Dealers, we map those to a Zoho custom field (Account_Channel_Type__c) and configure Zoho's Account hierarchy to reflect the upstream-downstream relationship.

LeadSmart Opportunities map to Zoho Deals. The Opportunity Name, Amount, Close Date, Stage, Probability, and Description fields migrate directly. LeadSmart pipeline stages map to Zoho Deal Stage values, with a Zoho Pipeline created to correspond to each LeadSmart Opportunity pipeline. Custom Opportunity fields for channel-specific deal types (Distributor Deal Type, Dealer Tier, Commission Rate) are pre-created as Zoho custom fields on the Deal module before import.

LeadSmart Activity records (Task and Event objects) migrate to Zoho Tasks and Events respectively. Task Status, Priority, Subject, Activity Date, and Description migrate directly. Event Start DateTime, End DateTime, Location, and description migrate as Zoho Events. The parent record linkage (WhoId to Contact or Lead, WhatId to Account or Deal) is resolved at migration time via Zoho lookup field IDs.

LeadSmart's Partner Collaboration Portal external partner records (linking internal Accounts to channel reps, brokers, dealers, and distributors) map to a combination of Zoho Account Contact Relationships and a custom Partner_Details__c module. We create a custom picklist field (Partner_Type__c) on the Contact module to distinguish Dealer, Distributor, Broker, and Agent roles. Partner-specific custom fields (Commission_Rate__c, Territory__c, Portal_Access__c) are pre-created on the custom module before migration.

LeadSmart Marketing Campaigns map to Zoho Campaigns. Campaign Name, Type, Status, Start Date, End Date, and Budget Cost migrate directly. Campaign Member status history (Sent, Opened, Clicked, Converted) migrates to Zoho Campaign Member records. LeadSmart's custom marketing automation fields are mapped to Zoho custom Campaign fields during the configuration phase.

LeadSmart extends Salesforce standard objects with distributor and manufacturer workflow fields. We inventory every LeadSmart custom field during scoping, match each to a Zoho custom field (type-matched: text to string, number to integer, date to date, picklist to picklist), and pre-create the Zoho schema before migration. Zoho's 300-field-per-module ceiling applies; if a module's field count approaches this limit, we flag the risk and archive low-priority custom fields into a supplementary export file.

LeadSmart Files and Attachments linked to Leads, Contacts, Accounts, and Opportunities migrate as Zoho Attachments linked to the corresponding Zoho record. We preserve parent record linkage using the record ID mapping generated during the primary data migration phase. Large binary attachments may require chunked transfer to respect API payload limits.

LeadSmart Genius Feed AI-generated customer issue and growth opportunity records migrate as Zoho Notes attached to the relevant Contact or Deal, or as records in a custom Insight module if the customer chooses. We note that Zia's AI replaces the predictive logic in the destination. The customer signs off on this decision during scoping because Zoho does not have a direct equivalent object model for LeadSmart's recommendation engine output.

LeadSmart User records map to Zoho Users by email match. We resolve the Role and Profile from LeadSmart (inherited from Salesforce Role Hierarchy and Profile) to Zoho Roles during the configuration phase. Any LeadSmart User without a matching Zoho User email goes to a reconciliation queue for the customer's admin to provision before record migration resumes.