Migrate from Seraph to HubSpot Service Hub

Seraph contact records (name, email, phone, company association) map directly to HubSpot Contact properties. The email address serves as the primary dedupe key. Custom Seraph contact fields migrate as HubSpot Contact properties; we create the property in HubSpot before import and map the field type (string, number, date, dropdown, checkbox) accordingly. Phone number formatting is normalized during the transform step to HubSpot's accepted format.

Seraph company or organization records map to HubSpot Company. Domain, name, and description transfer directly. Company is imported before Contacts so that the Contact-to-Company association (via the company_id reference) is resolved at the moment of Contact insert. If Seraph uses a flat contact model without company linking, we create a placeholder Company record and attach all contacts during migration.

Seraph ticket records (subject, status, priority, category, source, owner) map to HubSpot Ticket properties. Ticket status values are mapped to HubSpot Ticket pipeline status options; if Seraph uses a non-standard status vocabulary, we configure the HubSpot pipeline status values to match before migration. The ticket owner maps to a HubSpot User by email match. If Seraph supports multiple ticket pipelines, each maps to a separate HubSpot Ticket pipeline with its own stages.

Seraph conversation threads attached to tickets migrate to HubSpot Conversations linked to the corresponding Ticket. Each message in the thread (author, body, timestamp, attachments) migrates as a conversation message record. We resolve the contact reference by email match against the migrated HubSpot Contact. File attachments migrate as HubSpot file records linked to the conversation. If Seraph conversation metadata (channel type, CC list) has no HubSpot equivalent, we store it in a custom Ticket property for audit.

Seraph email engagements (emails sent or received within the ticket context) migrate to HubSpot EmailMessage records linked to the Contact and the parent Ticket. Email body (plain text or HTML), subject, direction (inbound/outbound), and timestamp transfer directly. Attachments migrate as HubSpot file records. Email addresses are matched to HubSpot Contacts by email lookup.

Seraph call logs attached to tickets migrate to HubSpot Conversations with channel type set to Call. Call duration, disposition, and recording URL (if available) store in conversation metadata fields. We resolve the contact reference by email match. If Seraph call records exist outside the ticket context, they migrate to HubSpot Contact records linked as conversation entries.

Seraph notes attached to contacts, companies, or tickets migrate to HubSpot Notes linked to the parent record. Note body migrates as plain text; rich text notes with embedded images store the image as a separate HubSpot file record and embed by URL reference. We resolve the parent record lookup using email match for contacts and domain match for companies.

Seraph agents map to HubSpot Users by email address. Active agents receive active HubSpot User accounts; inactive or deleted Seraph agents are held in a reconciliation queue so that tickets can be reassigned to a valid HubSpot User before final import. If multiple Seraph agents should map to a single HubSpot User (e.g., shared queue accounts), the customer specifies this during scoping.

Seraph teams or groups migrate to HubSpot Teams. Team membership (which agents belong to which team) migrates as HubSpot User team assignments. Note: the migration of team assignments does not automatically configure ticket routing rules in HubSpot; we document the routing logic from Seraph for the customer's admin to implement in HubSpot Workflows post-migration.

Seraph knowledge base articles (title, body, slug, category, publish status) migrate to HubSpot Knowledge Base articles. Article HTML body migrates as the HubSpot article body. If Seraph uses a multi-portal knowledge base structure, we consolidate articles under a single HubSpot knowledge base and use article tags or categories to replicate the original portal scoping. We do not migrate article access permissions (gated content) as a native HubSpot feature; this requires post-migration configuration or a separate scoping engagement.

Seraph custom ticket fields migrate to HubSpot Ticket custom properties. We create each property in HubSpot during the schema design phase before any data moves. Field type mapping follows: string to single-line text, number to number, date to date, dropdown to single-option, multi-select to multi-option, checkbox to single-checkbox. Picklist values are recreated as HubSpot option labels.

Seraph tags on tickets or contacts migrate to HubSpot Tags. Tags are preserved as-is and can be used for filtering and reporting in HubSpot. If Seraph uses tags as a categorization mechanism (e.g., product category, issue type), we recommend evaluating HubSpot Ticket pipelines or custom properties as a more structured alternative during the migration design phase.