Migrate from Dashcord to Zoho CRM

Dashcord Contact records in Salesforce map directly to Zoho CRM Contacts. We read standard Contact fields (Name, Email, Phone, Title, MailingAddress) plus any Dashcord-added custom fields we discover during schema introspection. The Salesforce Contact ID is preserved in a Zoho custom field dashcord_contact_id__c for cross-system audit. Account relationship is resolved via the Salesforce AccountId lookup at migration time.

Dashcord Lead records map to Zoho CRM Leads. Standard fields (Name, Email, Phone, Company, Status, LeadSource) migrate directly. Dashcord lifecycle stage values are stored as custom picklist fields on the Salesforce Lead; we preserve these raw values in a Zoho custom field original_lifecycle_stage__c so the admin can configure Zoho Blueprint stages or workflow rules to replicate the logic post-migration.

Salesforce Account records map to Zoho CRM Accounts. Standard fields (Name, Industry, Website, BillingAddress, Phone) migrate directly. The Account name becomes the Zoho Account lookup target for Contacts migrated in the same batch. We deduplicate by Account Name during import.

Dashcord wraps Salesforce Campaigns for marketing automation. Salesforce Campaign records map to Zoho CRM Campaigns with Campaign Name, Type, Status, StartDate, and EndDate preserved. Budget and actual cost fields map to Zoho Campaign custom fields if configured. Campaign Member status tracking migrates separately as Campaign Member records.

Campaign Members link Contacts and Leads to Campaigns in Salesforce. We migrate Campaign Member records by resolving the Contact or Lead lookup and the Campaign lookup at migration time, then write to Zoho CRM Campaign Members with Status preserved as a custom picklist if Zoho's default status values do not match the source. Status normalization rules are defined during pre-flight.

Dashcord stores numeric or tiered lead scores as Salesforce custom fields on Lead records. These custom fields are discovered during Salesforce org introspection and mapped to Zoho CRM custom fields of matching type (Number or Picklist). We flag any scoring model metadata stored in Dashcord custom objects that cannot be directly represented as a field value and document the gap for the customer's admin.

Dashcord assigns lifecycle stage values to Leads and Contacts as custom picklist fields. We preserve the raw stage value in a Zoho custom field original_lifecycle_stage__c. The customer's admin configures Zoho Blueprint stages or workflow rules to replicate the lifecycle logic post-migration; we provide a stage-mapping table as part of the handoff documentation.

Dashcord's event management module stores event records as custom Salesforce objects. Schema varies by Dashcord package version; we discover the active custom object during pre-flight via Salesforce Metadata API. Event records map to a Zoho CRM custom module with fields matching the discovered schema, or to the Zoho Events extension if the customer has CRM Plus. Event attendee data migrates as related custom module records.

Dashcord tracks email, call, meeting, and task activity via Salesforce Activity records (Task and Event objects). We migrate Tasks with Status, Priority, ActivityDate, and Subject preserved. Salesforce Event records migrate to Zoho Events with Start Date Time, End Date Time, and Location. Parent record lookups (WhoId, WhatId) are resolved to Zoho Lead or Contact IDs at migration time.

File attachments on Campaign, Contact, or Account records are stored in Salesforce as ContentDocument or Attachment objects. We export file binary data and re-attach to the matching record in Zoho CRM. Files exceeding Zoho's attachment size limits are flagged for the customer to address manually or store in Zoho Docs.