Migrate from Dashly to HubSpot

Dashly users map directly to HubSpot contacts. Dashly stores user properties (name, email, phone, custom properties) which map to HubSpot contact properties. Dashly user IDs are preserved as a custom Source_System_ID__c field for delta-run de-duplication and traceability. Original creation timestamps are kept in a custom Original_Create_Date__c property, and any custom user fields are migrated as HubSpot custom contact properties.

Dashly company records map 1:1 to HubSpot companies. Company properties (domain, industry, employee count) map to HubSpot company standard properties. Dashly parent-child company hierarchies map to HubSpot's parent company association. Dashly company IDs are saved as Source_System_ID__c for reference, and any custom company fields are transferred as HubSpot custom company properties. Industry picklist values are aligned to HubSpot’s default options, with manual mapping for non‑standard values.

Dashly supports multiple companies per user (N:N model via company_ids array on the user object). HubSpot uses many-to-many associations via the built-in association model. We create HubSpot associations for each Dashly user-to-company link, defaulting the primary company by most-recent-activity rule.

Dashly conversation threads contain ordered messages between the user and team members. We split threads into individual engagement records on the contact: agent messages become notes on the contact, user messages become internal notes, and message timestamps are preserved. Thread-level context (conversation ID, channel) is stored in a custom property.

Individual messages map to HubSpot notes attached to the contact record. The note body preserves the original message text, sender type (user vs. agent), and timestamp. Agent messages are labeled as internal notes; user messages become contact timeline entries. The conversation ID and channel information are stored in custom note properties to allow thread reconstruction if needed.

Dashly knowledge base articles migrate to HubSpot's knowledge base with article title, body content, category, and SEO settings. Article-to-bot associations are not preserved; bots must be rebuilt as HubSpot workflows and linked to articles manually post-migration. Each article’s Dashly ID is saved in a custom Source_System_ID__c property for cross‑reference, and the original category hierarchy is recreated in HubSpot’s knowledge base structure.

Dashly's leadbots, triggered messages, and auto-reply rules are bot logic with no direct HubSpot equivalent. Bot configurations cannot be extracted as migration-ready data — they must be documented and rebuilt as HubSpot workflows post-migration. We export bot trigger definitions as a reference PDF for your HubSpot admin.

Dashly tracks anonymous visitors before they become known users. The anonymous session data (first page seen, referrer, UTM parameters) migrates as HubSpot contact properties (hs_analytics_source, utm_content) but only for contacts that have an email. Fully anonymous HubSpot contacts are created for session-only records.

Dashly team members map to HubSpot users by email match. Agent IDs are preserved in the engagement notes for audit traceability. Unmatched Dashly agents are flagged before migration — your team either creates HubSpot users or reassigns conversations to an existing user.

Dashly files attached to conversations re-upload to HubSpot Files and are linked to the contact record via the file attachment property. HubSpot's 25MB per-file limit applies; files exceeding this are flagged for manual delivery. Original file names and timestamps are preserved in the HubSpot file metadata, and a custom Large_Files_Archive__c property points to a zip archive for oversized assets. All files are associated with the correct contact to maintain a complete audit trail.