Migrate from BackDocket to HubSpot

BackDocket clients map one-to-one to HubSpot contacts. All standard contact properties—first name, last name, email, phone, and address fields—map directly to HubSpot equivalents. Custom client fields like client_type and billing_rate migrate as HubSpot custom properties, requiring pre-migration property creation in HubSpot's property settings.

BackDocket stores company associations on clients when firm clients are tracked separately from individual contacts. If BackDocket contains a distinct company entity, it maps to the HubSpot Company object. Client-to-company associations are preserved during migration as HubSpot contact-to-company associations using the existing association records.

BackDocket matters map to HubSpot deals. The matter name becomes the dealname, matter description becomes deal description, matter value becomes amount, and assigned attorney becomes the HubSpot owner via email match. Case status maps to dealstage using value mapping between BackDocket status labels and HubSpot pipeline stage IDs.

BackDocket case status values—Active, Pending, Closed Won, Closed Lost—map to corresponding HubSpot deal stage values. Stage-entered timestamps are preserved as custom datetime fields on the deal record for reporting continuity and historical analysis in HubSpot dashboards.

BackDocket tasks map directly to HubSpot tasks. Task subject maps to Task subject, description maps to body, and due_date maps to hs_timestamp. Original owner assignments and creation timestamps are preserved on each migrated task record.

BackDocket calendar events map to HubSpot meetings. Event title, start and end times, location, and attendee information migrate to HubSpot Events object. Original owner and timestamps are preserved on each meeting record.

BackDocket document links and URLs cannot be re-hosted automatically since BackDocket storage becomes inaccessible post-migration. Document links are preserved as custom text fields on the related deal for manual re-hosting. Original document titles migrate as file_name__c custom text fields for reference during document re-upload.

BackDocket staff members map to HubSpot users by email address match. Staff roles map to HubSpot user roles or teams via value mapping. Unmatched staff records are flagged for fallback owner assignment before migration to prevent orphaned records.

BackDocket custom fields without native HubSpot equivalents—intake_date, practice_area, billing_rate, referral_source—create as HubSpot custom properties. Date fields map to HubSpot date type, picklists map to HubSpot picklist, and currency fields map to HubSpot currency or number type based on BackDocket field definitions.

BackDocket intake form data often contains both client properties and matter properties mixed together. These fields split during migration based on context: client-facing intake fields attach to the HubSpot Contact record while matter-related intake fields attach to the associated Deal record.

BackDocket task sequences and deadline reminder automations are platform-specific and have no equivalent in HubSpot's workflow system. We export complete workflow definitions as a reference document for your HubSpot administrator to use as a blueprint when rebuilding automations in HubSpot's workflow builder.

BackDocket notes attached to clients, matters, or tasks map to HubSpot notes. Original timestamps and owner assignments are preserved on each note record. Rich-text formatting is retained where BackDocket supports it, maintaining note readability in HubSpot.