Migrate from Dashcord to Salesforce Sales Cloud

Dashcord Contact records are standard Salesforce Contacts with custom Dashcord lifecycle and scoring fields. We export all standard Contact fields plus any Dashcord-specific custom fields enumerated during pre-flight schema discovery. The primary mapping challenge is ensuring the AccountId lookup is populated correctly for each Contact so that relationships to the Account object are preserved after Dashcord is uninstalled.

Dashcord Lead records are standard Salesforce Leads with custom Dashcord scoring and lifecycle fields. We preserve the full field set including any custom Dashcord picklist values for lifecycle stage. The original Dashcord lifecycle stage value is preserved in a custom field dashcord_lifecycle_stage__c for reporting continuity.

Dashcord uses standard Salesforce Account records for company and organization data. We export all standard Account fields including billing address, industry classification, and any custom fields. Account is created before Contact import so that AccountId lookups are resolved at the moment of Contact insert.

Dashcord wraps Salesforce Campaigns for marketing automation. We export Campaigns with all standard fields, campaign type, status, budget cost, and expected revenue. Campaign hierarchy (parent and child campaigns) is preserved via the ParentId field. Dashcord campaign-specific custom fields are enumerated and mapped during pre-flight.

Dashcord Campaign Members link Contacts and Leads to Campaigns with status and timing data. We export all CampaignMember records and preserve the MemberStatus and HasResponded flags. Status value normalization may be required if Dashcord used custom status values not present in the destination org's Campaign Member Status picklist; we add missing values before migration.

Dashcord tracks email sends, opens, and clicks via Salesforce Activity records. We export EmailMessage records (the email content) linked to Tasks (the activity timeline entry). The WhoId on Task points to the Lead or Contact; the WhatId points to the related Campaign, Account, or Opportunity. Campaign attribution data migrates to preserve marketing attribution history.

Dashcord assigns numeric or tiered lead scores stored as custom fields on Lead records. We export the raw score values and preserve them in a custom field dashcord_lead_score__c in Salesforce. If the destination org uses Salesforce's native Lead Scoring, we map values into that model during scoping. Score distribution analysis is included in the pre-flight audit to flag any negative or non-numeric values that require transformation.

Dashcord stores lifecycle stage as a custom picklist or number field on Contact and Lead. We preserve the raw values in dashcord_lifecycle_stage__c on both objects and map them to the destination CRM's equivalent field if one exists. If the destination org runs Salesforce Marketing Cloud Account Engagement (Pardot), lifecycle stage maps to the Pardot Prospect lifecycle field.

Dashcord's event management module stores event records as custom objects within Salesforce. Schema varies by Dashcord package version. We inspect the custom object's field definitions during pre-flight. Events can be migrated to Salesforce Campaign (using Campaign Type = Conference or Event) or to a custom event object that we provision during schema design. We flag any undocumented picklist values and event-specific fields that require custom Salesforce field creation.

Any custom fields added by Dashcord or created on top of the package are Salesforce custom fields. We read field metadata via the Salesforce API, enumerate all custom properties on each object, and map them to either standard Salesforce fields (if a semantic equivalent exists) or preserved custom fields with a dashcord_ prefix. Validation rules on custom fields are flagged during pre-flight and coordinated with the customer's admin before migration.

File attachments on Campaign, Contact, or Account records are stored as Salesforce Attachment or ContentDocument records. We export file binary data and re-attach to the matching record in the destination org. Files over 25 MB require chunked migration via the Salesforce Content API. We verify file access permissions during pre-flight to ensure the migration user has read access to all attached files.

Dashcord customers using Opportunities for deal tracking export them as standard Salesforce Opportunity records. We map Opportunity fields including StageName, Amount, CloseDate, Probability, and any custom fields. If Dashcord used custom stage values, we add them to the destination org's Sales Process before migration. OwnerId resolution is required at migration time; owners without matching Salesforce Users go to the reconciliation queue.