Migrate from Dashcord to HighLevel

Dashcord Contacts are standard Salesforce Contact records read from the host org. We map to GoHighLevel Contact using email as the dedupe key. All standard Contact fields (Name, Email, Phone, Title, Department) map directly. Dashcord custom contact properties are read via Salesforce field metadata and mapped to GoHighLevel custom fields on the Contact object. Any Contact without an email address is flagged in pre-flight for manual review before import.

Dashcord Lead records map to GoHighLevel Contact using email as the dedupe key. Dashcord stores lifecycle stage and lead score as Salesforce custom fields on the Lead object — these migrate as GoHighLevel Contact custom fields. If the customer has both converted and unconverted Leads in Dashcord, we import all Leads as GoHighLevel Contacts and preserve the conversion status in a custom field for reconciliation.

Dashcord Accounts are standard Salesforce Account records representing organizations. GoHighLevel does not have a separate Account object — organizations are represented through the Company field on Contact, and contact-account relationships are implied by shared Company values. We map Account fields (Name, Website, Industry, Billing Address) to GoHighLevel Contact custom fields or use a tag strategy to group contacts by company. The customer's admin selects the grouping approach during scoping.

Dashcord wraps Salesforce Campaigns for marketing automation. We export Campaigns as GoHighLevel Campaigns, mapping Campaign Name, Status, Type, and Start/End dates. Active campaign records transfer directly. Campaign descriptions and budgets migrate as text fields. GoHighLevel Campaigns are used for tracking in conjunction with Workflows — the customer rebuilds campaign-triggered automations post-migration.

Dashcord Campaign Members link Contacts and Leads to Campaigns with status and timing data stored in Salesforce. GoHighLevel does not have an equivalent Campaign Member object — campaign membership is tracked via Contact Tags and Campaign records linked through GoHighLevel's Campaign feature. We map Campaign Member Status to a GoHighLevel tag on the Contact (e.g., campaign_name_attended, campaign_name_responded) and create a Campaign record for reference. The customer reviews the tag strategy during scoping.

Dashcord's event management module stores event records as Salesforce custom objects with schema that varies by Dashcord package version. We discover the active event object schema during pre-flight via Salesforce metadata API, then map event records to GoHighLevel Contact entries using a dedicated event custom field (event_name__c) and a Note attachment with event details including date, type, and status. We flag any event records that cannot be parsed due to undocumented field values during the schema discovery phase.

Dashcord assigns lifecycle stage values to Leads and Contacts stored as custom picklist or number fields in Salesforce. We preserve the raw lifecycle stage values as a GoHighLevel Contact custom field (dashcord_lifecycle_stage__c). Additionally, we create a GoHighLevel tag per unique lifecycle stage value so the customer can use GoHighLevel's tag-based segmentation as a replacement for Dashcord's lifecycle tracking. The customer selects the tagging strategy during scoping.

Dashcord assigns numeric or tiered lead scores stored as Salesforce custom fields on Lead records. We export the raw score value and score tier (if stored separately) and map them to GoHighLevel Contact custom fields dashcord_lead_score__c and dashcord_score_tier__c. GoHighLevel's native contact scoring is a separate feature the customer's admin configures post-migration using the migrated score values as a baseline.

Dashcord tracks email sends, opens, and clicks via Salesforce Activity records (Tasks and Emails standard objects) linked to Contacts and Leads. We export Task records with ActivityDate, Subject, Description, and Status preserved as GoHighLevel Contact activities. EmailMessage records (body, HTMLBody, HasAttachment) migrate as Note attachments on the Contact. Campaign attribution data migrates as a text custom field on the Note for audit. We chunk the activity export using Salesforce Bulk API to handle large volumes.

Any custom fields added by Dashcord or created on top of the Dashcord package are stored as Salesforce custom fields on standard CRM objects. We enumerate all custom fields on Contact, Lead, Account, and Campaign via the Salesforce Field API during pre-flight, create matching GoHighLevel custom fields before import, and map field values using the discovered Salesforce field types. Undocumented Dashcord-specific picklist values are enumerated during schema discovery and flagged for the customer to confirm before mapping.