Migrate from ConSol*CM to HubSpot Service Hub

ConSol*CM Requests map directly to HubSpot Tickets. We extract all Request fields including custom field group properties, status, priority, category, and origin channel (email, portal, phone). The Request ID is preserved in a custom Ticket field for audit traceability. Conversation history is extracted separately and linked to the Ticket as message records.

Conversations linked to ConSol*CM Requests export as message threads in HubSpot Tickets. We preserve the author attribution, timestamp, internal/external flag, and message body. HubSpot supports both public replies and private internal notes, which we map from ConSol*CM's conversation visibility flags. Attachments on individual messages are downloaded and re-uploaded to the associated HubSpot Ticket.

ConSol*CM Contacts with organization associations map to HubSpot Contacts linked to HubSpot Companies. Contacts without an organization association map to HubSpot Contacts only. Custom field groups on ConSol*CM Contacts require field-by-field mapping to HubSpot custom properties; we document each non-standard field during the discovery phase and map it to an equivalent HubSpot Contact property type.

ConSol*CM Resources represent internal staff or system entities. We extract Resource records and match them by email to HubSpot Users. User assignments on Requests (owner, assignee, watcher) are remapped to HubSpot Ticket owner and assigned agent fields. Resource naming conventions and ID structures differ from HubSpot's User model, so explicit email-based lookup is required to avoid orphaned assignments.

ConSol*CM organizational units and team structures map to HubSpot Teams. We preserve team-to-agent assignments from the Resource mapping so that ticket routing logic documented during discovery can be rebuilt by the customer's HubSpot admin. Team-level permissions and inbox assignments require manual configuration in HubSpot after migration.

File attachments associated with ConSol*CM Requests and Conversations are downloaded and re-uploaded to the corresponding HubSpot Ticket. We handle filename deduplication by appending a sequence number to duplicate filenames within the same ticket. We verify attachment size limits against HubSpot's per-file and per-ticket limits and flag any files exceeding limits for customer decision before re-upload.

Tags on ConSol*CM Requests and Contacts export as flat lists. We map them to HubSpot's tagging schema using the same tag names where possible. During the import dry-run, we flag any naming conflicts (e.g., identical tag names on different object types) for the customer to resolve before committing to full migration.

ConSol*CM knowledge base articles export with article content and metadata, but the category hierarchy and portal gating structure require manual mapping to HubSpot's Knowledge Base schema. We extract all article content, titles, slugs, and metadata fields, then deliver a mapping document showing how ConSol*CM categories map to HubSpot Knowledge Base categories. Multi-portal setups in ConSol*CM (separate portals per product or customer segment) require separate Knowledge Base creation in HubSpot.

ConSol*CM's extensible Contact model uses field groups that can vary per installation. We extract the field group configuration via ConSol*CM's system documentation export and map each field individually to HubSpot Contact properties. HubSpot's supported property types (string, number, date, dropdown, checkbox, etc.) are matched to the source field type, and any unsupported types are converted or flagged for customer decision. Customer sign-off is required on all non-standard field mappings before migration.

ConSol*CM Requests support custom field groups beyond the standard status, priority, and category fields. We extract these via the system documentation export and map each to a HubSpot Ticket property. The mapping is validated during the dry-run phase, and any ticket fields that cannot map directly to HubSpot's property types are flagged with transformation options (e.g., free-text merged into a notes field, multi-select converted to a comma-separated string property).

ConSol*CM's system documentation feature exports system configuration to a file describing custom objects, field definitions, and workflow settings. We review this export to understand the full schema including any custom objects or field groups not visible in the standard Request-Contact-Resource triad. Workflow configurations described in this export form the basis of the workflow inventory document we deliver for manual rebuild in HubSpot Service Hub.

ConSol*CM version 6.17.1 extended the REST API to search for records where specific data fields have no value set. We use this during the profiling phase to identify incomplete records. Empty values on mapped fields are preserved as empty in HubSpot rather than defaulting to placeholder text, so reporting on data completeness remains accurate post-migration.