Migrate from Dashcord to Twenty CRM

Dashcord Contacts map to Twenty People records. We read Contact records via the Salesforce API with all standard fields (Name, Email, Phone, Title, Address) plus any Dashcord-specific custom contact properties discovered during metadata introspection. The Twenty People record is created first so that any related Activities, Notes, or Tasks can be linked at migration time. Email serves as the dedupe key.

Dashcord Accounts map to Twenty Companies. The Account Name becomes Company name, Billing Address migrates to the Company address fields, and Industry and Annual Revenue become custom or standard Company fields as applicable. Account is created before any related People import so the relationship is satisfied on insert.

Dashcord Leads map to Twenty People records with a type distinction. We preserve the Lead Status and any Dashcord custom lead fields on the People record and flag the record source in a custom field for segmentation. The customer's team reviews the Lead-to-People boundary during scoping because Twenty has no separate Lead object; unqualified prospects live as People with a status property.

Dashcord wraps Salesforce Campaigns for marketing automation. We export Campaign records and create a corresponding custom object in Twenty named Campaign (or the customer's preferred label) with fields for Campaign Name, Status, Type, Start Date, and Budget. Campaign Members map separately (see below). If the customer does not require campaign history preservation, we exclude Campaigns from migration scope to reduce complexity.

Campaign Members link Contacts and Leads to Campaigns with status and response tracking data. We create a Campaign Member custom object in Twenty with a Lookup to the Campaign custom object and a Lookup to the People record, plus fields for Status and Member Status. The relationship is resolved at migration time by loading Campaigns first, then People, then Campaign Members last so both parent lookups exist.

If the Dashcord Salesforce org includes Opportunities (Enterprise tier or custom), we map them to Twenty Opportunities. Stage, Amount, Close Date, and Description migrate directly. The Pipeline and Stage values require a configuration step in Twenty's Settings to whitelist the imported stage names before migration, per Twenty's requirement that fields exist before CSV import.

Dashcord assigns lifecycle stage values (subscriber, lead, MQL, SQL, customer, etc.) stored as custom picklist or number fields on Lead and Contact. These have no direct Twenty equivalent — Twenty has no native lifecycle stage concept. We create a custom picklist field named Lifecycle Stage on the People object, populate it with the distinct Dashcord lifecycle values discovered during schema introspection, and migrate the raw stage value for each record.

Dashcord stores numeric or tiered lead scores as custom fields on Lead records. We create a custom number field Score on the People object, migrate the raw score value, and note the scoring model name or rule reference if stored in a separate Dashcord custom object. The scoring model itself (the rules that produced the score) is not migratable and must be rebuilt in Twenty or via an external scoring tool.

Dashcord's event management module stores records as Salesforce custom objects whose schema varies by Dashcord package version. We discover the active event object name and field definitions during pre-flight metadata introspection, export the records, then create a matching custom object in Twenty named Event with fields for Name, Date, Type, Location, and any Dashcord-specific properties. Relationships to People (attendees) migrate as multi-select or linked records depending on the event model.

Dashcord tracks email sends, opens, and clicks via Salesforce Task and Email records. We export Tasks linked to Contacts and Leads where the Subject or Type indicates email activity, preserving the original timestamp, subject line, and body. The migrated Tasks attach to the corresponding Twenty People record via the email address match. Note that Dashcord's email marketing attribution (which campaign drove the send) requires a separate Campaign Member mapping if the customer needs campaign-level attribution preserved.

File attachments on Contact, Account, or Campaign records are stored in Salesforce ContentDocument and ContentDocumentLink. We export the file binary data and store it as a link or file reference on the corresponding Twenty People or Company record. Large file attachments (over 10 MB) require the customer's chosen Twenty hosting method to support the storage size; self-hosted deployments may need additional storage configuration.

Any custom fields added by Dashcord or created on top of the package are Salesforce custom fields. We read field metadata via the Salesforce Tooling API during pre-flight, enumerate all active custom properties on each object, create matching custom fields in Twenty's Data Model, then map the values during data migration. Undocumented or renamed Dashcord custom fields require manual enumeration during scoping because no public schema reference exists.