Migrate from HaloCRM to HubSpot Service Hub

HaloCRM Tickets map 1:1 to HubSpot Service Hub Tickets. Status, priority, assignee, requester, created date, and last modified date transfer directly. HubSpot's ticket pipeline stages map from HaloCRM ticket status, with the HaloCRM Priority field mapped to a HubSpot Ticket Priority property. We disable any active HaloCRM SLA escalation rules before migration to prevent breach-action emails firing against migrated historical tickets. Ticket thread/conversation history migrates as a chronological sequence of HubSpot conversation updates preserving the original timestamp and author.

HaloCRM Client records map to HubSpot Contacts. The Client name, email, phone, and address fields transfer to the corresponding HubSpot Contact properties. HaloCRM Client-scoped custom fields map to standard Contact properties or HubSpot Contact custom properties with explicit type alignment. Any Client records that have no email address are flagged during scoping for the customer's admin to review before migration, as HubSpot requires a unique identifier for Contact deduplication.

HaloCRM Organizations map to HubSpot Companies. We preserve the Organization-to-Client relationship by resolving the organization identifier on each Client record during import and linking the resulting Contact to the corresponding HubSpot Company via the contact-to-company association. Company domain, address, and custom properties transfer directly. The HubSpot Company object serves as the parent record for Contact-to-company linkage.

HaloCRM Agent records carry name, email, and role. We extract all Agent emails referenced on ticket, client, and organization records and match by email against the destination HubSpot portal's User table. Any Agent without a matching HubSpot User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission mappings are documented for manual reconfiguration in HubSpot because access control models differ substantially between the platforms.

HaloCRM Knowledge Base articles transfer to HubSpot Knowledge Base articles with article body, category assignment, and publication status preserved. Article-to-category relationships map to HubSpot Knowledge Base categories, which we create in HubSpot to match the source hierarchy before article import. Draft, published, and archived status flags translate to HubSpot's article state model. Inline images referenced in article bodies are downloaded and re-hosted in HubSpot's file manager during migration.

HaloCRM Service Contract records (dates, values, linked client and organization entities) have no direct HubSpot Service Hub standard object equivalent. We create a HubSpot custom object matching the contract schema during schema design, including contract date fields, monetary values, and lookup relationships to the migrated Contact and Company records. The custom object is pre-created in HubSpot before any data import begins, so the lookup references resolve at insert time.

HaloCRM device and asset records with serial numbers, device types, and custom info fields map to a HubSpot custom object pre-created during schema design. Serial number, device type, and linked ticket relationships transfer with device ID preserved in a legacy_id__c field for audit traceability. If the customer uses HubSpot's Assets feature (Service Hub Enterprise), we evaluate whether the native Assets object is appropriate instead of a custom object.

File attachments associated with HaloCRM tickets and Knowledge Base articles are downloaded from the source platform's storage, uploaded to HubSpot's file manager, and re-attached to the corresponding ticket or article in HubSpot. Large attachment batches are chunked into groups of 50 files per batch to avoid API timeout. We log the original file size and MIME type for the customer's admin to verify after migration.

Tags applied to HaloCRM tickets and Knowledge Base articles export as flat label arrays and re-apply as HubSpot Tags on the corresponding records. Tag-to-record associations migrate in the same batch as the parent object to preserve relationships. Tags in HubSpot appear in the Tag Management section of the portal.

HaloCRM SLA definitions (response time, resolution time, business hours, breach actions) map to HubSpot Service Hub SLA policies available from Professional tier. Response time and resolution time thresholds transfer directly. Custom breach-action logic (custom notification triggers, escalation assignments) does not migrate because HubSpot's SLA policies handle breach notification through workflow automation, not as a native SLA property. We document every HaloCRM breach-action for the customer's admin to rebuild as HubSpot Workflows post-migration.

HaloCRM canned text entries migrate as HubSpot saved replies (available in Starter tier and above). Variable substitution syntax differs between platforms; we flag any dynamic placeholders ({{client_name}}, {{ticket_id}}) as comments in the migrated template body for the customer's admin to update to HubSpot variable syntax ({{contact.name}}, {{ticket.id}}) post-migration.

HaloCRM Client-scoped custom fields are explicitly mapped to HubSpot Contact custom properties during the field alignment phase. We validate the target property type (text, number, date, dropdown) in HubSpot before migration. HaloCRM Client-scoped fields that have no equivalent in HubSpot are flagged in the field-mapping document for the customer's admin to review and decide whether to create a new HubSpot custom property or drop the field.