Migrate from Dashcord to Nutshell

Dashcord Contacts map to Nutshell People records. The Dashcord Contact's email address becomes the Nutshell People email field, which serves as the primary dedupe key. Any Dashcord lifecycle stage values (stored as Salesforce custom fields on Contact) migrate as custom fields on the Nutshell People record. Dashcord contact custom properties discovered during Salesforce org introspection also become Nutshell People custom fields.

Dashcord Leads map to Nutshell People records in the Lead status. Unlike Salesforce which maintains separate Lead and Contact objects, Nutshell uses a single People record that can exist as a lead or contact. We set the People status to Lead and preserve any Dashcord lead score (stored as a Salesforce custom field) as a custom field on the Nutshell People record. The original Lead score model and raw values are preserved for the customer's admin to configure Nutshell's lead scoring logic post-migration.

Dashcord Account records map directly to Nutshell Company records. The Account name becomes the Company name, industry maps to the Company industry field, and billing address maps to the Company address fields. Account custom fields discovered during Salesforce org introspection become Nutshell Company custom fields.

Dashcord wraps Salesforce Campaigns for marketing automation. We export Campaigns with their type, status, start and end dates, budgeted cost, and actual cost. These map to Nutshell Campaign records with equivalent fields. Campaign attribution data linking to People is preserved through the People mapping.

Dashcord Campaign Members (linking Contacts and Leads to Campaigns) migrate as linked People-to-Campaign associations in Nutshell. We preserve the member status (Responded, Sent, etc.) as a custom field on the Nutshell Campaign record and note the response date for each linked People record.

Dashcord's event management module stores events as custom Salesforce objects whose schema varies by Dashcord package version. We discover the active event object schema during Salesforce org introspection. Event name, date, location, and attendee list (linked People) map to Nutshell Activity records with type = Event. The event status (scheduled, completed, cancelled) is preserved as a custom field on the Activity.

Dashcord assigns lifecycle stage values (Subscriber, Lead, MQL, SQL, Customer, Evangelist, etc.) stored as Salesforce custom picklist fields on Contact and Lead. We preserve the raw lifecycle stage value as a custom text or picklist field on the Nutshell People record. The customer decides during scoping whether to use a text field (preserving all historical values) or a picklist (with the admin selecting which values to include as valid options in Nutshell).

Dashcord stores numeric or tiered lead scores as custom fields on Lead records. We export the raw score value and, if stored, the scoring model or rule set name. These migrate to Nutshell People custom fields. The customer's admin rebuilds the lead scoring logic using Nutshell's scoring features or a third-party integration post-migration.

Dashcord tracks email sends, opens, and clicks via Salesforce Activity records (Tasks and Emails objects). Emails migrate to Nutshell Activities with type = Email, preserving the email body, subject, send date, and open/click data if stored in custom fields. Calls migrate as Activities with type = Call and call duration preserved. Meetings migrate as Activities with type = Event with start/end time and location.

File attachments on Dashcord Contact, Lead, or Account records are stored in Salesforce Attachments or ContentDocument objects. We export file binary data and re-attach to the matching Nutshell People or Company record. Large file attachments (over 25 MB) may require chunking or alternative upload methods depending on Nutshell's file size limits.