Migrate from Gorgias to HubSpot Service Hub

Gorgias Customers (end shoppers) map to HubSpot Contacts. The primary identifier is email address used as the dedupe key during import. Any Gorgias Customers associated with a company (the optional company field) map to a HubSpot Contact with a Company association resolved via the Company mapping. First name, last name, phone, and any custom string or select fields migrate as HubSpot contact properties. Boolean, date, and number custom fields migrate as HubSpot contact properties with equivalent types.

Gorgias's optional company association on Customer records maps to HubSpot Company. The Gorgias company name becomes the Company Name field. If a Customer has no company association in Gorgias, no Company record is created. Company mapping must precede Contact import so that the Company-to-Contact association is satisfied at insert time.

Gorgias Tickets map directly to HubSpot Tickets. Standard fields (priority, status, assignee, timestamps, channel) migrate as HubSpot ticket properties. The Gorgias ticket ID is preserved in a custom field (e.g., gorgias_ticket_id__c) as a reference key. Custom fields on tickets migrate as HubSpot ticket properties with type equivalence: Gorgias select and multi-select become HubSpot single-line text or a custom picklist, boolean becomes a checkbox property, date becomes a date property.

Gorgias's individual messages within a ticket (public replies and internal notes) migrate to HubSpot Ticket Conversations. The author (agent or customer), timestamp, message body, and privacy flag (internal vs public) are preserved. Attachments on conversations are downloaded from Gorgias and re-uploaded to HubSpot via the HubSpot file upload API, with the attachment reference linked to the conversation record.

Gorgias Agents map to HubSpot Users. We match by email address as the reconciliation key. Group membership in Gorgias maps to HubSpot Teams. Any Agent without a matching HubSpot User by email is flagged in the reconciliation queue for the customer's admin to provision before migration continues.

Gorgias Groups (or Teams) map to HubSpot Teams. Group membership on Agents migrates as Team membership on HubSpot Users. Teams are created before agent migration so that team assignments are resolved at insert time.

Gorgias Macros (saved reply templates with variable substitution and dynamic actions) have no native equivalent in HubSpot Service Hub's standard feature set. We export the full macro body, conditions, and action sequence as a written inventory document. The customer's HubSpot admin rebuilds them as Saved Replies in the HubSpot inbox settings or as a knowledge base article linked in a Workflow. Dynamic variable substitution is not preserved automatically.

Gorgias Rules (ticket routing, assignment, and auto-response triggers) have no direct migration path to HubSpot Workflows. We export the full rule logic (conditions, operators, actions) as a written inventory with a recommended HubSpot Workflow equivalent for each rule. The customer's admin rebuilds routing and auto-response logic in HubSpot's Workflow builder. Ticket-assignment rules map to HubSpot Workflow ticket-assignment actions; auto-response rules map to Workflow email-send actions.

Gorgias Views (saved filter configurations) map to HubSpot Ticket Saved Views. The filter logic (field conditions, operators, sort order) is exported and recreated as a saved view in HubSpot. We note any Views that reference custom fields that cannot be mapped 1:1 and flag them for manual review.

Gorgias Knowledge Base categories map to HubSpot Help Desk knowledge base categories. Category hierarchy (parent-child ordering) is preserved. If multi-locale translations are enabled, each locale is fetched via a separate API call per the Gorgias locale-per-call constraint, and the translations are stored in HubSpot's localized article content. We enumerate enabled locales from account settings before beginning the KB export.

Gorgias KB articles (title, body HTML, author, folder/category assignment, status) migrate to HubSpot Help Desk knowledge base articles. Draft articles in Gorgias remain draft in HubSpot. Published articles are migrated as published. Multi-locale translations are fetched per-locale and stored in HubSpot's localized article structure. Articles in draft status are flagged for review before the knowledge base goes live.

Gorgias CSAT ratings (score, free-text response, timestamp, linked ticket) migrate to HubSpot Customer Feedback surveys. The ticket reference is preserved so that CSAT ratings can be associated with the migrated HubSpot Ticket. HubSpot's feedback survey feature must be enabled in the account before migration; it is available from Professional tier.

Gorgias Tags applied to Tickets migrate as HubSpot Ticket Labels. Tags applied to Customers migrate as HubSpot Contact Labels. We flag any tag names that conflict with HubSpot's reserved system labels. The customer selects during scoping whether tags should map directly or be prefixed with a namespace (e.g., gorgias_tag_).</