Migrate from GREYHOUND CRM to HubSpot Service Hub

GREYHOUND CRM Customers map directly to HubSpot Contacts. The customer's primary email, phone, and company association migrate to the corresponding HubSpot Contact properties. We preserve the original GREYHOUND customer ID in a custom property greyhound_customer_id__c for reference and reconciliation. If a GREYHOUND Customer has multiple associated Companies, the primary company maps to HubSpot Company and the secondary companies attach as additional Company associations on the Contact.

GREYHOUND CRM Company records map directly to HubSpot Companies. The company domain, address, and description migrate to the corresponding HubSpot Company properties. Company is created before any Contact import so that the Company lookup relationship is satisfied at the moment of Contact insert.

GREYHOUND CRM Tickets map to HubSpot Tickets with status, priority, source, and assignment preserved. The ticket name maps to the HubSpot Ticket subject, and the ticket content or description maps to the ticket body. We resolve the assigned Agent to the corresponding HubSpot User via email match. Ticket pipeline in GREYHOUND CRM becomes the HubSpot Ticket pipeline and status values map to the equivalent HubSpot ticket status.

Each GREYHOUND CRM Custom Ticket Field is evaluated by type and mapped to the equivalent HubSpot property type: string fields map to single-line text or multiple-line text, boolean fields map to single-checkbox, date fields map to date picker, number fields map to number, and select or multi-select fields map to single-select or multiple-select picklist. We create the custom property in HubSpot before migration and reference it in the ticket import. Any GREYHOUND custom field with no HubSpot equivalent is flagged for the customer to decide whether to create a new property or drop the field.

GREYHOUND CRM Conversations map to HubSpot Conversations linked to the corresponding Ticket and Contact. Each message within the conversation migrates as a conversation message with author, timestamp, and body preserved. Private notes in GREYHOUND CRM migrate as private conversation comments in HubSpot (requires the migration user to have conversation access permissions). Attachments on conversation messages migrate as file attachments linked to the conversation thread.

GREYHOUND CRM Agents map to HubSpot Users by email match. Active agents with current HubSpot User accounts map directly. Agents without a matching HubSpot User go to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive or deleted GREYHOUND agents are noted for reassignment of their open tickets before migration.

GREYHOUND CRM Teams map to HubSpot Teams. Team membership migrates so that each HubSpot User is assigned to the correct Team based on their GREYHOUND team association. Teams are provisioned in HubSpot before user migration begins.

GREYHOUND CRM Ticket Associations (related tickets linked for tracking purposes) map to HubSpot Ticket associations using HubSpot's built-in related tickets feature. If the association type does not map directly, we create a custom ticket property (e.g., related_ticket_id__c) to preserve the association reference.

GREYHOUND CRM KB Articles migrate to HubSpot Knowledge Base articles with title, body, author, and status preserved. The article body migrates as rich text, and any embedded images are extracted and re-uploaded as HubSpot file attachments with the URLs updated in the article content. Article status (published, draft, archived) maps to HubSpot's article availability setting.

GREYHOUND CRM KB Categories map to HubSpot Knowledge Base categories. Category hierarchy (parent and child categories) migrates as HubSpot category parent-child relationships. Articles are assigned to categories post-migration using the category mapping established during scoping.

GREYHOUND CRM Tags on Tickets and KB Articles migrate to HubSpot Tags. Tags used for ticket classification migrate as HubSpot ticket tags. Tags used for KB article organization migrate as HubSpot knowledge base article tags. Tag counts and usage patterns are preserved for reporting continuity.

GREYHOUND CRM Attachments on Tickets and Conversations migrate to HubSpot Files attached to the corresponding Ticket or Conversation record. Files are uploaded to HubSpot's file manager and linked via the file association. Very large attachments (over 250 MB) are flagged for the customer to upload manually post-migration or use an external file storage link. We preserve the original attachment filename and upload timestamp.

GREYHOUND CRM custom objects migrate to HubSpot custom objects (Enterprise tier required for custom objects in HubSpot). We pre-create the destination schema in HubSpot including all custom fields, lookup relationships to standard objects (Contact, Company, Ticket), and validation rules before any data import. Custom object API names match the GREYHOUND custom object names with a __c suffix per HubSpot convention.