Migrate from ConSol to HubSpot

ConSol Contacts map directly to HubSpot Contacts. Name, email, phone, job title, and address fields carry across as HubSpot standard properties. Owner resolution happens by email match against HubSpot users. Any ConSol contact fields that do not have a HubSpot standard equivalent are flagged for custom property creation before migration runs.

ConSol supports role-labelled contact-to-company associations (e.g., Technical Contact, Billing Contact). HubSpot's native association model stores a single role label per contact-company pair. When multiple roles exist, we surface all labels in a custom text property; your admin decides how to consolidate.

ConSol Company records map to HubSpot Companies. Name, domain/website, industry, employee count, and annual revenue fields map to HubSpot standard properties. Parent-company hierarchies in ConSol map to HubSpot's Parent Company field. Multi-level hierarchies are flattened to a single parent reference to match HubSpot's data model.

ConSol Case and Incident records map to HubSpot Tickets. The original ConSol case number is preserved in Source_System_Case_Number__c for traceability. Ticket subject, description, status, and priority carry across; close date maps from ConSol's resolution timestamp. Custom case fields require pre-created HubSpot custom properties to avoid data loss during migration.

ConSol Service Requests are distinct from Incidents. We map them to a separate HubSpot Ticket Pipeline so your team can differentiate request-type tickets from incident-type tickets using pipeline-level reporting rather than a single pick-list value. Each pipeline can have its own stages, SLA targets, and assignment rules aligned to the original ConSol workflow.

ConSol Complaint records route to a dedicated HubSpot Ticket pipeline or a custom Complaint__c boolean field depending on your reporting requirements. We confirm the routing preference during the sample migration review before the full run. The pipeline approach enables separate SLA tracking and team assignment for complaint handling versus standard service requests.

ConSol's SLA response-time field has no native HubSpot equivalent. We create SLA_Response_Deadline__c as a custom datetime property on the Ticket object. Note: SLA monitoring requires HubSpot Service Hub Professional — Starter and Basic tiers display the field but do not trigger SLA alerts.

ConSol's resolution-time SLA field migrates as SLA_Resolution_Deadline__c. Combined with the response deadline, these two custom fields allow your team to report on SLA adherence in HubSpot dashboards even at Starter tier, though active breach alerting requires Service Hub Professional. Custom workflows can be configured to send notifications when resolution deadlines approach or pass.

ConSol contracts and SLA agreements with commercial terms map to HubSpot Deals. The contract name becomes the Deal name; the contract value or SLA tier maps to Amount. Deal stage reflects contract status (Active, Pending Renewal, Expired). Custom properties on the Deal capture additional SLA terms that don't fit HubSpot's standard deal fields.

ConSol CM custom fields attached to cases (e.g., bug tracking identifiers, regulatory categories, cost center codes) require pre-created custom properties in HubSpot before migration. We generate the property creation plan based on the ConSol schema export and deliver it as a HubSpot setup checklist.

ConSol file attachments on cases download and re-upload to HubSpot's file storage. File size limits per the destination apply. Inline images or embedded documents in case notes are extracted and re-hosted as separate HubSpot files. Attachment metadata including original file names and upload dates are preserved in HubSpot's file properties.

ConSol case communication history — emails, call logs, internal notes — maps to HubSpot Engagements on the contact and ticket timelines. Original timestamps and owner email preserved so the HubSpot timeline reflects the full case history. Engagement type (email, call, note) maps to HubSpot's engagement type property for filtering and reporting.