Migrate from Assured JobCheck to HubSpot

Assured JobCheck company records (policyholders, property owners) map directly to HubSpot Companies. Salesforce AccountId on Job records resolves to HubSpot Company associations. Parent-child account hierarchies in JobCheck map to HubSpot's parent company relationship. All standard fields such as phone, website, and billing address are carried over as HubSpot company properties, and any inactive accounts are archived rather than deleted to preserve historical job records.

Salesforce Contacts in JobCheck (adjusters, policyholders, crew leads) map 1:1 to HubSpot Contacts. Owner fields resolved by email match. Job-specific role labels (e.g., primary adjuster) preserved as HubSpot association labels on the linked Deal. Duplicate contacts are merged by email, while phone numbers and titles become HubSpot contact properties, and role labels such as primary adjuster are preserved as Deal association labels.

The central Job record in Assured JobCheck is a Salesforce Case or custom Job object. It maps to a HubSpot Deal because both represent a work unit with financial value (reserve amounts, claim totals). Job-specific fields (insurance_policy, loss_type, reserve_amount, loss_address) become HubSpot custom properties on the Deal.

JobCheck job statuses (New Job, In Progress, Awaiting Adjuster, Completed, Invoiced) map to HubSpot Deal stages via value-by-value mapping. Stage-enter timestamps preserved as HubSpot deal property updates. If JobCheck uses custom status values, each one requires explicit value mapping to an existing or new HubSpot deal stage.

Restoration job categories (Water Damage, Fire Damage, Mold Remediation, Contents PackOut) in JobCheck map to a HubSpot custom pick-list property called job_type__c on the Deal. These are not native HubSpot deal fields — they must be created before migration runs.

Insurance metadata (policy number, carrier name, claim number, adjuster contact) stored as Salesforce fields on the Job record. Each maps to a separate HubSpot Deal custom property (insurance_policy_number, insurance_carrier, claim_number, adjuster_name, adjuster_phone). These must be pre-created in HubSpot. We validate each field for format (e.g., phone numbers for adjuster_phone) and apply default values if missing, while mapping any compound identifiers such as policy suffix to separate HubSpot properties for reporting.

The insurance reserve amount or total claim value in Assured JobCheck maps to the HubSpot Deal Amount field. If JobCheck stores multiple financial figures (initial reserve, revised reserve, actual loss), the primary reserve amount becomes Deal.Amount and supplementary figures become custom numeric properties.

PackOut photo attachments stored as Salesforce Files on Job records are downloaded and re-uploaded to HubSpot as Files linked to the corresponding Deal. File names, folder structure (Pre-Existing Damage, Claim Related), and parent-record linkage are preserved. Large photo libraries may require batched file migration.

Job Feed entries (status updates, crew assignments, site visit notes) in Assured JobCheck translate to HubSpot engagements or notes on the linked Deal. Timestamps and owning user are preserved. Original system timestamps help restoration managers maintain job timeline continuity. Any @mentions of team members in the original feed become HubSpot owner tags, and attachments are re-linked to the Deal. Activity order is preserved to provide a complete timeline for managers.

Salesforce user IDs assigned as Job owners in JobCheck are resolved by email match to HubSpot users. Unmatched owners are flagged before migration — teams can invite the Salesforce user to HubSpot or reassign their records to a designated fallback owner before the full run.

If the JobCheck Salesforce org contains custom objects beyond the standard Job, those map to HubSpot custom objects on Enterprise plans. On Starter or Pro plans, custom-object data collapses into Deal custom properties. We document the mapping plan during the pre-migration schema review.