Migrate from Sagicc to HubSpot Service Hub

Sagicc Cases map to HubSpot Tickets as the primary helpdesk record. Case status, priority, channel source, assigned agent (via owner lookup), team, created/updated/closed timestamps, and custom properties migrate directly. Sagicc case ID is preserved in a custom ticket property sagicc_case_id__c for audit traceability. Case tags migrate as ticket Tags in HubSpot.

Sagicc Conversations (message threads within a Case across all channels including WhatsApp, chat, email, SMS, Facebook, Instagram, Telegram, and web) map to HubSpot Ticket conversations. Each message preserves author, timestamp, body, and channel attribution. HubSpot's conversation threading model groups messages by channel within a Ticket, which mirrors Sagicc's cross-channel thread structure. File attachments within conversations migrate as HubSpot conversation attachments linked to the same Ticket.

Sagicc Contacts map directly to HubSpot Contacts. Contact name, document/ID fields, phone numbers, email, and custom properties migrate. Sagicc contact ID is preserved in a custom contact property sagicc_contact_id__c. Sagicc allows manually created contacts; we migrate all records regardless of source and handle any duplicates via email dedup during import. Company association from Sagicc maps to HubSpot Company via domain or explicit company field match.

Sagicc Agents map to HubSpot Users resolved by email address. Agent profile fields (name, role, team assignment, active/inactive status) migrate as User properties. Any Sagicc Agent without a matching HubSpot User email is held in a reconciliation queue for the customer's admin to provision before the import phase resumes. Performance metrics attached to Cases migrate as part of the Case history.

Sagicc Teams (agent groupings used for routing and SLA assignment) map to HubSpot Teams. If the destination HubSpot account uses the Teams feature (Professional and Enterprise), we map team structure and agent-to-team assignments directly. If the destination uses a simpler inbox routing model without HubSpot Teams, we map team assignments to inbox routing rules that assign tickets to the correct agent group. Sagicc team-to-channel SLA bindings require manual mapping to HubSpot pipeline SLA rules.

Sagicc KB articles migrate to HubSpot Knowledge Base articles with article content, categories, and associations. Formatting and embedded media assets require review; articles with complex layouts may need light reformatting post-migration. HubSpot Knowledge Base supports article publishing, language settings, and availability rules that differ from Sagicc's category model. We document the full article inventory including approval status and recommend a staged publishing plan for the customer admin.

Sagicc SLA definitions (first response time, resolution time, business hours) configured per team or channel map to HubSpot Enterprise SLA features. HubSpot's SLA model attaches to Ticket Pipelines rather than per-team configurations, so we document each Sagicc SLA rule and recommend a mapping to the nearest HubSpot pipeline SLA. If the destination is on Starter or Professional without SLA features, SLA targets are documented as custom ticket properties for manual monitoring.

Custom fields on Cases and Contacts in Sagicc export as field definitions and values, mapping data types (string, number, date, boolean, select, multi-select, checkbox) to HubSpot property types. HubSpot's property type system differs from Sagicc's field type model, so we review each custom field during discovery to confirm the correct HubSpot type. Multi-select fields in Sagicc map to HubSpot multi-checkbox or multi-select properties; single-select maps to HubSpot select.

File attachments within Cases, Conversations, and Knowledge Base articles migrate as HubSpot attachments linked to the parent record (Ticket, Knowledge Base Article). We transfer binary files and maintain the association. Attachments are counted separately from record counts during scoping because file size and count affect migration timeline and staging storage.

Tags applied to Cases for categorization and filtering migrate as HubSpot Tags. Tag names and their associations to Tickets migrate directly. Sagicc's tag taxonomy (if different from the destination's intended taxonomy) is preserved as-is during migration and can be cleaned up post-migration through HubSpot's tag management.

Block List entries (contacts, accounts, or domains blocked from interaction in Sagicc) are exported in full. HubSpot Service Hub has no native block-list feature, so we flag each entry for manual review. For contacts, we recommend setting the HubSpot Contact property Do Not Contact or adding to a static suppression list. For domains, we document for manual domain-level suppression in the customer's email sending system. This is a configuration step the customer admin performs post-migration.

Channel configurations (WhatsApp Business API, web chat, email, Facebook, Instagram, SMS, Telegram) in Sagicc represent communication sources. HubSpot's Conversations Inbox aggregates inbound messages across channels via separate integration setup. We document each active Sagicc channel, its configuration parameters, and the recommended HubSpot equivalent integration. WhatsApp Business API templates require re-approval under Meta; we list all active templates with their approval status so the customer can plan the re-approval timeline under their HubSpot-connected Meta Business account.

Sagicc Flow Rules (automation triggers and actions for routing, case assignment, and canned responses) are exported as rule definitions. HubSpot Workflows are a different automation model with different triggers, conditions, and action types. We do not migrate automations as code. We deliver a written inventory of every active Flow Rule with its trigger, conditions, actions, and recommended HubSpot Workflow equivalent for the customer's admin to rebuild post-migration.

Sagicc Reports are generated from Case and interaction data with filters by campaign, agent, and date. Report definitions are not exportable in a reusable format. We export the underlying data (Cases, Agents, timestamps) so that equivalent HubSpot reports can be rebuilt. We deliver a written inventory of every Sagicc report with its filters, metrics, and recommended HubSpot reporting equivalent. The customer admin or a HubSpot partner rebuilds the reports post-migration.