Migrate from Web+Center to HubSpot Service Hub

Web+Center Incidents map to HubSpot Service Hub Tickets. The source Incident status (Open, In Progress, On Hold, Closed) maps to HubSpot ticket pipeline stages; we configure the pipeline during scoping so the stage set matches the customer's active Web+Center status values. Priority (Critical, High, Medium, Low) maps to HubSpot priority values. Conversation threads migrate as ticket comments in chronological order. Any custom Incident fields require explicit field-level mapping because each Web+Center deployment has a different custom field set.

Web+Center Customer records map to HubSpot Contacts. Email address, phone number, first name, last name, and portal preferences transfer directly. The Customer-to-Incident linkage migrates as ticket associations so each Contact retains its full ticket history in HubSpot.

Web+Center Company records map to HubSpot Companies. The Company-to-Customer relationship migrates so that each HubSpot Company is associated with the correct Contacts. If the customer has duplicate Companies in Web+Center, we discuss whether to merge or keep separate records during scoping.

Web+Center Assets (hardware and software inventory) map to a HubSpot Custom Object named Asset. Custom asset fields such as serial number, purchase date, warranty expiration, and assignment status vary per deployment and require explicit field mapping. We pre-create the Asset custom object schema in HubSpot before migration begins.

Web+Center categories and subcategories are stored as lookup tables. We extract the full set of active values and map them to a HubSpot ticket pipeline, where each top-level category becomes a stage group and subcategories map to stage values. If a category has no HubSpot equivalent, we flag it during scoping for the customer to decide whether to collapse or create a new stage.

Ticket attachments are stored as files on the Web+Center server filesystem with database path references. We resolve each path reference, extract the binary content, and upload to HubSpot's file storage linked to the corresponding ticket. We run a pre-migration path validation step to identify broken or orphaned file references before the migration window opens.

Web+Center user and agent records map to HubSpot Users. We export by email address as the matching key. Password hashes cannot be migrated for security reasons; agents receive setup emails from HubSpot to establish credentials post-migration. Inactive or deleted Web+Center agents are noted for the customer's admin to handle manually.

Web+Center KB articles use a proprietary content format. We extract the text content and any embedded images, convert to HubSpot Knowledge Base article schema, and import with original author and creation date preserved. HTML formatting may require minor post-migration cleanup if Web+Center used non-standard markup. Article categories map to HubSpot Knowledge Base categories or topic tags.

Web+Center SLA timers are calculated using priority level and configured business hours. We preserve the Incident creation timestamp and original priority so HubSpot's SLA engine can recompute deadline and breach status on import. Any time already elapsed against an SLA at the source is not carried forward. The customer reviews HubSpot SLA policy configuration before going live.

Web+Center allows administrators to add custom fields to Incidents beyond the standard set. Each deployment has a unique custom field set; we inventory all custom fields during discovery and map each to a HubSpot custom ticket property of the matching type (text, number, date, single-select, multi-select, checkbox). If HubSpot does not support an equivalent type, we discuss alternatives such as text fields or tag-based approximations during scoping.

Web+Center internal notes on Incidents map to HubSpot ticket comments. We preserve the author name, creation timestamp, and full note body. Internal versus external visibility is mapped to HubSpot's internal note flag so that agent-only notes remain private post-migration.

Historical closed Incidents migrate as closed HubSpot Tickets with original close date preserved. We set the ticket status to the appropriate closed stage and maintain the original resolution notes, assignee, and closed timestamp so that historical reporting is intact after cutover.