Migrate from DoneDone to HubSpot Service Hub

DoneDone Issues map directly to HubSpot Tickets. The DoneDone Issue title maps to Ticket subject, description maps to Ticket body, status maps to Ticket status within the selected Pipeline, priority maps to Ticket priority, and due date maps to Ticket due date. We preserve the full Issue edit history as internal Notes on the Ticket, and map private comments on DoneDone to HubSpot Notes with the internal-only visibility flag. Assignee maps to Ticket owner by email resolution. The DoneDone issue ID is preserved in a custom HubSpot property donedone_issue_id__c for cross-reference.

Each unique DoneDone Project becomes a HubSpot Service Hub Pipeline. DoneDone's custom Workflow (status set and transition rules) for each Project maps to a corresponding Pipeline with custom stage values. Teams with divergent Workflows across Projects will have multiple Pipelines in HubSpot, each with their own stage configuration. We enumerate every distinct Workflow during scoping and confirm the Pipeline-stage mapping with the customer before migration begins.

DoneDone Workflows define ordered Status values and permitted transitions. We map each Workflow's status sequence to HubSpot Pipeline stages in the same ordinal order, preserving status names and color assignments where possible. Transition rules (what statuses can follow which) have no direct HubSpot equivalent and are documented in the Workflow inventory for the admin to rebuild in Service Automation if Professional or Enterprise tier is purchased.

DoneDone Tags are flat labels applied across Issues. We map Tags to HubSpot Labels on Tickets, which are available from Starter tier. If the customer uses Tags as a classification system for routing or reporting, we may recommend a custom multi-select property on the Ticket object to preserve Tag values as a structured filterable field rather than a plain label.

DoneDone Saved Replies are agent template snippets. HubSpot Service Hub Starter+ includes Canned Snippets with variable support. We migrate Saved Replies as Canned Snippets in HubSpot Snippets, with the DoneDone Saved Reply title preserved as the Snippet name and the body preserved as content. If the customer is on the Free tier (which does not include Canned Snippets), we flag this and recommend upgrading or documenting Saved Replies for manual rebuild.

DoneDone private comments (visible only to internal team members) map to HubSpot internal Notes attached to the Ticket. We apply the internal-only visibility flag on import. Failure to preserve this distinction risks exposing internal team discussions to end customers viewing the Ticket thread. This mapping is applied by default and confirmed with the customer during scoping.

DoneDone Issues support multiple watchers in addition to a primary assignee. HubSpot Tickets support a single owner. We map the primary DoneDone assignee to Ticket owner by email resolution. The full watcher list is preserved as a custom contact-array property donedone_watchers__c on the Ticket so that all original stakeholders are traceable. Customers should verify whether their SLA or routing rules depend on single-assignee semantics before cutover.

DoneDone attachments on Issues reference files stored via Google Drive integration. We download each attachment by URL, preserving file name, size, and uploader metadata, and re-upload to HubSpot's file storage attached to the corresponding Ticket. Files exceeding HubSpot's storage limits per tier are flagged for the customer to resolve before migration. The attachment uploader's email maps to the HubSpot Contact who uploaded it if a matching Contact record exists.

DoneDone Issues can reference other Issues as sub-tasks or related items with relationship semantics (parent-child, blocks, relates-to) that vary by project configuration. We preserve the raw linked-Issue IDs and target Issue IDs as a custom text property linked_issues__c on each migrated Ticket, and document the relationship types for the customer to rebuild using HubSpot's Ticket Associations or a custom association object in Service Hub Professional+.

Every DoneDone Issue carries a timestamped history log of field changes (status transitions, assignee changes, priority changes, description edits). We export this as a chronological array of change events and replay it as internal Notes on the Ticket in the same temporal sequence. Each history entry is attributed to the DoneDone user who made the change if that user has a corresponding HubSpot Contact record.

DoneDone Issues are associated with a reporting Contact (name, email). We map this to a HubSpot Contact record. If the Contact email matches an existing HubSpot Contact, we link the Ticket to that Contact. If no match exists, we create a new Contact record or register the reporter as a Ticket contact depending on the customer's HubSpot tier and contact management preferences.

DoneDone's Reports dashboard generates data on-demand from the issue history log and is not stored as a discrete exportable data object. We cannot migrate historical reporting snapshots, SLA compliance charts, or velocity metrics. We flag this during scoping and advise the customer to export any needed reports as PDFs or screenshots before migration cutover. Service Hub's native reporting replaces these capabilities post-migration.