Migrate from Jitbit Helpdesk to HubSpot Service Hub

Jitbit Tickets map directly to HubSpot Tickets with full history, attachments, internal notes, and status transitions preserved. The Jitbit ticket status (open, pending, resolved, closed) maps to HubSpot pipeline stage values, and we flag any Jitbit Custom Statuses for manual stage creation in HubSpot before the ticket import begins. Custom field values transfer to HubSpot ticket properties with type normalization—Jitbit text fields map to HubSpot single-line text, number fields to number properties, and date fields to date properties.

Jitbit agents and administrators map to HubSpot Users. We resolve by email match against the destination HubSpot portal. Any Jitbit agent without a matching HubSpot User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Agent group memberships from Jitbit map to HubSpot Teams, which control ticket assignment and inbox visibility.

Jitbit end customers (the ticket submitters) map to HubSpot Contacts. The Jitbit user email becomes the Contact email, and the contact name maps from Jitbit user full name fields. We flag any Jitbit users who are also listed as Companies for HubSpot Account creation before Contact import so that the Account-Contact relationship is satisfied at insert time.

Jitbit Company records map to HubSpot Companies with company name and domain preserved. The HubSpot Company is created before any linked Contact import so that the Company-Contact lookup relationship is satisfied at insert time. Companies without a Jitbit-linked domain are created as standalone records with a default company type property set.

Jitbit Categories define ticket routing and default assignment. We map category names to HubSpot Pipeline names during scoping, but the destination pipeline must be created and configured in HubSpot before tickets import. Each category becomes a pipeline, and the customer configures the stages (default: New, Open, Pending, Solved, Closed) before migration begins. We flag this as a pre-migration configuration dependency.

Jitbit tags are plain-text labels on tickets. We transfer all tags and preserve tag-to-ticket associations during migration by applying the tags as HubSpot ticket tags at insert time. HubSpot ticket tags are standard properties that appear on the ticket record and can be used for filtering and reporting without additional configuration.

Jitbit Custom Fields hold structured ticket metadata. We map field types to HubSpot property equivalents where possible: text to single-line text, number to number, date to date, dropdown to single-select checkbox to single-checkbox. Complex or conditional custom fields may require value normalization—for example, Jitbit multi-select checkbox values stored as comma-separated strings map to HubSpot multi-select properties with pipe-separated values. We document every custom field in the pre-migration audit and resolve type mismatches before migration runs.

Jitbit allows custom ticket statuses beyond the defaults. These are configuration artifacts stored in the application database, not portable data. We export all active custom status names and their open/closed semantics during the pre-migration audit. The customer's admin must recreate these as stage values in HubSpot Pipelines before tickets import. We provide a status-to-stage mapping table in the migration scope document so the admin can configure the correct open/closed semantics.

Jitbit KB articles are structured HTML content organized into categories. We export full article text, attachments, and category assignments. For large knowledge bases (100+ articles), we recommend using HubSpot's native Knowledge Base Importer for the bulk article transfer, and we supplement with API-based migration for any articles that fail the importer. We map Jitbit article categories to HubSpot Knowledge Base categories during transfer.

Jitbit Assets are hardware/software inventory records linked to users and tickets. HubSpot Service Hub has no native asset management module, so we create a custom object (Asset__c) in the destination portal with fields for serial number, asset type, purchase date, warranty expiry, and assignment (linked to Contact). We preserve the ticket-asset association by storing the original Jitbit ticket ID as a custom field on the HubSpot ticket for audit. Asset assignment history transfers as a related list on the Asset__c record.

Jitbit Canned Responses are templated replies stored per category. We export the text and category associations. HubSpot does not have a native canned response object at the Service Hub tier, so we recommend recreating them as HubSpot Snippets (available in Professional and Enterprise) with the same category structure. Variable syntax differs between platforms; we document placeholder differences so the admin can update templates post-migration.

Ticket and KB article attachments are stored files. We extract them from Jitbit's storage (SaaS blob storage or on-premise file system) and re-attach them to their target records at the destination using HubSpot's file upload API. Original filenames are preserved. HubSpot's file attachment limit is 300 MB per file; files exceeding this threshold are flagged for the customer to handle manually or split before migration.

Jitbit supports splitting complex tickets into subtickets. HubSpot has no native subticket hierarchy. We flatten subticket hierarchies into linked tickets at the destination, preserving the parent-child relationship as a tag (e.g., parent-ticket-{id}) and a custom ticket property (parent_ticket_id__c) rather than a native hierarchy. This ensures the relationship is queryable and visible to agents without relying on a platform feature that does not exist in HubSpot.

Jitbit Automation Rules are configuration artifacts that trigger actions on ticket events (keywords, status changes, category assignments). These do not export and must be rebuilt in HubSpot Workflows. We document every active automation rule in the pre-migration audit—its trigger, conditions, and actions—with a recommended HubSpot Workflow equivalent using HubSpot's native workflow builder. The customer's admin rebuilds the rules post-migration based on this inventory.