Migrate from Dashcord to Freshsales

Dashcord uses Salesforce Leads as lifecycle entry points. Standard Salesforce Lead fields (Name, Email, Phone, Company, Status, LeadSource) map directly. Dashcord-specific custom fields storing lifecycle stage values and lead scores migrate as Freshsales custom fields named during scoping (for example, dashcord_lifecycle_stage__c and dashcord_lead_score__c). We deduplicate by email match and flag any duplicate emails in a reconciliation report before insert.

Dashcord Contacts are the primary audience records in the lifecycle model. Standard Contact fields (Name, Email, Phone, Title, Department) map to Freshsales Contact. Dashcord custom contact properties migrate to Freshsales custom fields with the same field label and data type. We preserve the Salesforce Account relationship by mapping to Freshsales Accounts using domain or account name as the dedupe key.

Dashcord Accounts represent company and organization records linked to Contacts and Opportunities. Standard Account fields (Name, Website, Industry, BillingAddress, Phone) map to Freshsales Account. Any custom Account fields added in the Dashcord package or Salesforce org migrate to Freshsales custom fields. Account-to-Contact relationships are preserved via AccountId on Contact records.

Dashcord wraps Salesforce Campaigns for marketing automation. We export Campaigns and map them to Freshsales Campaigns, preserving Campaign Name, Type, Status, StartDate, EndDate, and BudgetedCost. Campaign Members linking Contacts and Leads to the Campaign migrate to Freshsales Campaign Members with Member Status mapped to Freshsales campaign member status values.

Campaign Members link Dashcord Contacts and Leads to Campaigns with status and timing data. We export all member records and map them to Freshsales Campaign Members, resolving the Contact or Lead reference and the Campaign reference at migration time. Campaign Member status values (Sent, Responded, Opened, Clicked) are normalized to Freshsales status labels.

Dashcord assigns lifecycle stage values (Subscriber, Lead, MQL, SQL, Customer, Evangelist) stored as custom picklist fields on Lead and Contact records. These are not Freshsales standard fields. We create a Freshsales custom picklist field during pre-flight schema setup and migrate the raw values. The customer chooses whether to map these to Freshsales lifecycle stage defaults or keep them as-is for audit. This field is queryable and usable for segmentation in Freshsales.

Dashcord stores numeric or tiered lead scores as custom number or picklist fields on Lead and Contact records. We export the raw score values and the scoring model name if stored in a related custom object. Freshsales has its own Freddy AI behavioral scoring that activates on Growth and above; we create a custom numeric field (dashcord_score__c) to preserve the original Dashcord score and allow comparison against Freshsales' AI score after migration.

Dashcord's event management module stores events as custom Salesforce objects whose schema varies by Dashcord package version. We introspect the Salesforce org's custom object definitions during pre-flight to identify the event object name and field set. Standard event fields (Event Name, Start Date, End Date, Location, Description) map to Freshsales Appointments. Attendee records map to Freshsales Appointment Contact records. Schema variations require manual enumeration during pre-flight; we flag any fields with no Freshsales equivalent in the mapping document.