Migrate from ITCO to HubSpot Service Hub

ITCO Customer records map to HubSpot Contacts. We extract customer identifiers, names, email addresses, phone numbers, and company associations from ITCO manually during the discovery phase, then load via HubSpot Contacts API or CSV import. The customer email address serves as the dedupe key. Any ITCO Customer without an email address is flagged for manual review during scoping before import.

ITCO Company records map to HubSpot CRM Companies. The HubSpot company domain is derived from the customer email domain or explicitly recorded in ITCO. We create the HubSpot Company record before importing Contacts so that the parent Company association is satisfied at Contact insert time. If ITCO does not have explicit company records, we create Companies from the unique domains in the Customer email addresses.

ITCO Tickets map to HubSpot Service Hub Tickets. The ticket subject, description, status, priority, and assigned agent migrate directly. We map ITCO ticket stages to HubSpot Ticket pipelines and pipeline stages configured in the destination before migration. ITCO's custom ticket fields require pre-creation in HubSpot (see Custom Ticket Fields mapping) before tickets load. Ticket creation timestamps and last-modified timestamps are preserved as HubSpot hs_ticket_createdate and hs_time_in_stages custom properties for historical analysis.

ITCO ticket stages map to HubSpot Ticket pipeline stages. We configure the HubSpot Ticket Pipeline in Settings before migration, creating stage names that match ITCO's naming convention. Stage ordering and default/open/closed state flags are set to match ITCO's workflow so that reporting continuity is preserved. Each pipeline maps to a HubSpot Ticket Pipeline with ordered stages.

ITCO Agent records map to HubSpot Users. We extract agent email addresses, names, and role/team assignments during manual extraction. Agents are mapped to HubSpot Users by email match. The customer's HubSpot admin provisions any missing Users in HubSpot before the production migration phase begins, since OwnerId references on Tickets are required fields.

ITCO Team structures map to HubSpot Teams. Team membership migrates with agent assignments, and team-level routing rules in HubSpot are configured based on ITCO's team hierarchy. HubSpot Teams are created before Agent migration so that team associations are valid at import time.

ITCO Conversation records (message threads within tickets between customers and agents) map to HubSpot's conversation stream on the parent Ticket. We extract message content, sender, timestamp, and direction (inbound/outbound) manually, then load as conversation records linked to the migrated Ticket. Message ordering is preserved by timestamp sequencing. If ITCO conversations are embedded within the ticket record rather than separate records, we split them into discrete conversation entries during the transformation phase.

ITCO custom ticket fields have no published schema; each customer's configuration may include unique field names, data types, and validation rules. We enumerate all custom fields during a dedicated discovery session, document their ITCO data types, and create equivalent HubSpot custom properties (Text, Number, Date, Checkbox, Dropdown) in HubSpot Settings before any ticket data loads. Data type mismatches are resolved during transformation (e.g., ITCO multi-select text strings become HubSpot multi-checkbox properties). This step extends the discovery phase by 3-5 days per migration.

ITCO agent-level custom properties (internal tracking fields on agent records) that are required for reporting or workflow logic are identified during discovery. We create equivalent HubSpot User properties in the destination and map values during the agent migration phase. If ITCO agent properties track performance metrics relevant to post-migration reporting, we include them as custom properties on HubSpot User records.

ITCO stores custom data on Customers, Tickets, and Agents beyond standard fields. We identify these custom properties during discovery, map them to HubSpot Contact properties, Ticket properties, or User properties as appropriate, and create the destination properties in HubSpot Settings before data load. Multi-value properties (e.g., ITCO fields storing comma-separated values) are transformed into HubSpot multi-select fields.

ITCO does not expose a documented tag taxonomy via API. We do not migrate tags as automated records. We provide a written inventory of unique tag values observed in ITCO ticket data during extraction, recommend HubSpot Tag or multi-select property strategy during scoping, and guide the customer's admin on manual tag application post-migration. If tags are critical for reporting continuity, we create a HubSpot multi-select custom property pre-populated with observed tag values for manual tagging during the review window.

ITCO file attachments on tickets and conversations require manual extraction from the ITCO interface, as no programmatic download is available. We flag attachment-heavy tickets during scoping (typically those with more than 5 file attachments or attachments over 10 MB) and provide a manual backup checklist. Customers download attachments directly from ITCO, upload them to HubSpot File Manager, and we map attachment file names and URLs to the migrated Ticket records via a reference field. This is a customer-performed step with FlitStack AI guidance, not an automated migration component.