Migrate from Aritic Desk to HubSpot Service Hub

Aritic Desk Tickets map directly to HubSpot Service Hub Tickets. We transfer ticket ID, subject, description, status (Open/Closed/Pending mapped to HubSpot's pipeline stage values), priority, type, channel source, created and updated timestamps, and internal notes. Custom ticket fields migrate as typed HubSpot custom properties (string, number, date, single-select, multi-select, checkbox). We extract conversations as ticket replies in HubSpot's thread model, preserving the author, timestamp, body, and any attachments. Parent-record resolution (which Contact or Company owns the ticket) is resolved via email match during migration.

Aritic Desk Customer records map to HubSpot Contacts with name, email, phone, company, address, and lifecycle timestamp preserved. Customer-specific properties and tags transfer as HubSpot contact properties. The customer-to-ticket association is maintained by resolving the Aritic customer email to the HubSpot Contact record created during this phase. We verify that contacts created from Aritic Organizations are linked to the corresponding HubSpot Company record where applicable.

Aritic Desk Organization records (company-level accounts) map to HubSpot Companies with name, domain, industry, size tier, and owner assignment preserved. The link between Aritic Customer records and their parent Organization transfers as a HubSpot Company-Contact association. We use the organization domain as a deduplication key during import.

Aritic Desk Agent profiles map to HubSpot Users. We transfer name, email, role (Admin/Agent), department assignment, and active/inactive status. HubSpot has no native department object, so department assignment maps to a custom single-select property department__c on the User record. We resolve agents by email match against the destination HubSpot portal's user list. Agents without a matching HubSpot user go to a reconciliation queue for the customer to provision before record import continues.

Aritic KB Categories map to HubSpot Knowledge Base Hubs. We configure the HubSpot KB structure before article import, creating one Hub per Aritic Category. If the customer uses multiple Aritic portals (multibrand support), each portal's KB maps to a separate HubSpot Hub. The parent-child hierarchy within the KB structure is preserved by mapping Aritic Sections to HubSpot article folders within each Hub.

Aritic KB Sections map to HubSpot article folder groupings within each Knowledge Base Hub. We replicate the category-section parent-child relationships by creating the folder structure before article import begins. This ensures articles land in the correct organizational context in HubSpot.

Aritic KB Articles transfer with title, body content, author, creation date, and publish status. We strip embedded Aritic dynamic tokens and conditional content blocks before import so that articles render correctly in HubSpot without broken placeholders. Each article with non-portable dynamic elements is flagged for the customer's KB team to review post-migration. HubSpot's Knowledge Base importer does not support custom fields on articles; if the customer has custom metadata on KB articles in Aritic, we store it in a custom text property on the HubSpot article record. Attachments are extracted and uploaded to HubSpot's file manager with links stored in a custom field on the article.

Aritic macros are text response templates with dynamic placeholders such as {{ticket.customer_name}} and {{ticket.id}}. We extract the plain-text macro content, strip the Aritic-specific tokens, and document each macro with its original name, trigger conditions, and body text. HubSpot Service Hub does not have a native macro token engine equivalent to Aritic's; the customer rebuilds these as HubSpot templates and snippets using HubSpot's variable syntax. We deliver the macro inventory as a written handoff document.

Aritic SLA policies define first response time and resolution time targets per ticket priority or type. We document each SLA as structured metadata (name, metric type, target duration, business hours, applicable ticket criteria) and map it to the equivalent HubSpot Professional SLA Policy configuration. SLA migration is a configuration task, not a data migration; we provide the written specification for the customer to configure in HubSpot Settings after migration.

Aritic Desk triggers and business rules (ticket routing, priority escalation, notification routing) are event-driven automations tied to Aritic-specific field names and operators. We extract trigger conditions and actions as structured metadata and deliver a written automation inventory with each rule's trigger, criteria, and action described in HubSpot-equivalent terms. Rebuilding these in HubSpot Service Hub is a post-migration admin task.

CSAT ratings and survey responses from Aritic Desk link to ticket records. We migrate the rating value, respondent email, and ticket reference into HubSpot custom properties on the Ticket record (csat_rating__c and csat_respondent_email__c). The rating scale is preserved as a number or mapped to HubSpot's available scale type based on configuration during scoping. If the customer used Aritic's survey model extensively, we recommend configuring HubSpot's built-in surveys post-migration to capture future responses natively.

File attachments on tickets and KB articles are extracted from the Aritic export or database, uploaded to HubSpot's file manager, and linked to the parent record via a custom URL property or embedded in the ticket thread. We flag files exceeding HubSpot's 10 MB per-file limit for manual handling. Inline images embedded in ticket descriptions or KB article bodies are extracted separately and re-inserted as HubSpot-hosted file URLs post-migration.

Tags applied to tickets and customers transfer as flat label arrays in HubSpot. We verify character encoding compatibility between the Aritic export format and HubSpot's tag requirements. Tags used for segmentation or reporting are preserved for use in HubSpot filters and workflows post-migration.

Billable or internal time logged against Aritic tickets transfers as structured time records (agent, duration, description, billable flag) stored in HubSpot custom properties on the Ticket record. HubSpot Service Hub does not have a native time-tracking object; the custom property approach preserves the data for reporting purposes even if the native time-entry workflow requires post-migration configuration.