Migrate from SmartDesk to Zoho CRM

SmartDesk Accounts and Companies map directly to Zoho CRM Accounts. The source account name becomes Account Name, industry classification maps to Industry picklist, and employee count maps to Employees field. Custom properties attached to the account transfer to Zoho custom fields that must be pre-created in the destination before migration. We use Account Name as the dedupe key during import. Account is created before any Contact import so that the Account Lookup is satisfied at the moment of Contact insert.

SmartDesk Contacts carry standard fields: name, email, phone, address, and lifecycle stage. We perform a direct field-to-field mapping and preserve all custom contact properties on every record. Email address is the primary dedupe key. If a Contact in SmartDesk references a parent Account, we resolve the AccountId via the Account mapping completed in the previous phase before Contact insert begins.

SmartDesk separates Leads from Contacts as distinct objects. We map the source Lead records to Zoho CRM Leads, preserving Lead Source and Lead Status as custom fields where the destination schema does not have a native equivalent. If the customer uses SmartDesk's Lead object primarily for unqualified prospects, they remain as Zoho Leads; if they use Leads interchangeably with Contacts, we apply a customer-defined split rule during scoping to determine which records map to Lead versus Contact in Zoho.

SmartDesk Deals map to Zoho CRM Deals. The Deal name, value, expected close date, and owner migrate directly. Stage values must be reconciled against the destination pipeline's stage set, which may differ from SmartDesk's custom stage names and counts. We enumerate the SmartDesk pipeline stages from the live account or export, compare against the Zoho stage configuration, and flag any stage without a direct match for customer review before migration.

SmartDesk allows fully custom Pipelines and Stages with no standard set. When migrating Deals into Zoho CRM, we must first enumerate the existing pipeline stages in the SmartDesk account and map each source Deal to a matching Zoho stage by name or sequence. If no matching stage exists in the Zoho destination, we create a new stage or default to the nearest equivalent and flag the record for customer review. This stage reconciliation pass adds a mapping step to the migration timeline and requires the customer to confirm the target Zoho pipeline layout before Deals are imported.

SmartDesk Tasks attach to Contacts or Deals with assignee, due date, status, and description. We preserve the task owner by resolving SmartDesk owner email to Zoho CRM User email, and preserve linkage to the parent Contact or Deal record via the Zoho WhoId and WhatId fields. Task status and priority map to Zoho Task Status and Priority picklist values. If SmartDesk uses task subtypes (call, email, meeting), we map them to the corresponding Zoho Task subtypes.

SmartDesk Activities include calls, emails, and notes logged against Contacts or Deals. We map the activity type, timestamp, body, and related contact or deal. Call activities migrate as Zoho Tasks with Sub-Task Type = Call and Call Duration preserved. Email activities migrate as Zoho Tasks with Subject and Description. Meeting activities migrate as Zoho Events with Start Date Time, End Date Time, and Location. Notes migrate as Zoho Notes linked via the parent record reference. Some activity metadata may require custom field handling if SmartDesk captures data not represented in Zoho's standard activity fields.

SmartDesk Campaigns store campaign name, type, status, start and end dates. We map these fields to Zoho CRM Campaigns. Email send metrics, open rates, and click data do not migrate as they live in the email delivery system rather than the CRM. Campaign members from SmartDesk are mapped to Zoho Campaign Members linked to the corresponding Contact or Lead records.

SmartDesk Help Desk Tickets are linked to Contacts and carry priority, status, assignee, and conversation threads. We map the ticket body, status, priority, and linked contact to Zoho CRM Cases. If the customer uses Zoho Desk (a separate product), we document the migration path to Cases in Zoho CRM and the corresponding ticket migration path to Zoho Desk separately. Conversation history migrates as threaded Case Comments. This object requires the customer to decide whether Cases in Zoho CRM or Zoho Desk is the destination.

SmartDesk supports Unlimited Custom Fields on all plans, but they must be defined within Zoho CRM before data can be written to them via API. We cannot dynamically create custom fields during import. We detect all custom field definitions in the SmartDesk export, generate a custom field manifest listing every source custom field with its data type, and provide instructions for the customer to create each corresponding Zoho custom field before migration begins. This manifest is a required pre-condition for the migration run.

SmartDesk User and Owner records are mapped by email address. We extract every distinct SmartDesk Owner referenced on Contact, Account, Deal, and Activity records and match by email against the Zoho CRM User table. Owners without a matching Zoho User are held in a reconciliation queue. The customer's Zoho admin provisions any missing Users (active or inactive depending on whether the original SmartDesk user is still active). Migration cannot proceed past Account import until Owner resolution is complete because OwnerId is required on most standard objects.

File attachments associated with Contacts, Deals, or Accounts are downloaded from SmartDesk and re-uploaded to Zoho CRM. We handle file type validation, preserve original filenames, and link each attachment to the parent record in Zoho via the Attachments module. If the customer's Zoho CRM is on a tier with limited storage, we flag attachment volume before migration to confirm adequate storage allocation.