Migrate from Sercom to HubSpot

Sercom contact records migrate directly to HubSpot Contacts. All standard fields (name, email, phone, job title) map 1:1. Contacts associated with multiple Sercom companies get their primary company assigned as the HubSpot primary company; secondary associations are preserved via HubSpot's Company Contact Associations feature.

Sercom custom fields on contact records that do not match HubSpot's standard property names require pre-creation in HubSpot Settings > Properties before migration. FlitStack delivers a custom property manifest listing each Sercom field name, its data type, and the HubSpot property internal name your admin should create.

Sercom company records map to HubSpot Companies. The company name maps to the HubSpot name property, domain maps to the website property, and industry maps to HubSpot's industry pick-list with value mapping applied for any Sercom industry values not in HubSpot's default list.

Sercom custom fields on company records are migrated as HubSpot custom properties on the Company object. Each property must be pre-created in HubSpot Settings with the matching field type — dropdown, number, date, text, or checkbox — and pick-list options defined as needed. FlitStack provides a manifest listing each Sercom field name, its data type, and the suggested HubSpot internal name your admin creates, ensuring data loads without skipping fields.

Sercom deal or project records migrate as HubSpot Deals. The deal name, amount, and close date map directly. Sercom's internal stage or status field maps to a HubSpot pipeline stage via value mapping — if Sercom uses multiple stage values across record types, we map each to a distinct HubSpot pipeline stage for your pre-configured destination pipeline.

Sercom stage or status pick-list values are mapped to HubSpot pipeline stage names. The mapping is 1:1 per pipeline. Stage probability values are not preserved in HubSpot's stage definitions but can be configured as custom probability fields on the Deal object.

Sercom support cases migrate as HubSpot Tickets. The case subject maps to the ticket subject, and case content or description maps to the ticket content property. Priority flags map to a custom ticket property (Ticket_Priority__c) since HubSpot Tickets have no built-in priority field.

Sercom ticket status values (open, in progress, resolved, closed) map to HubSpot Ticket pipeline stage names. If Sercom uses additional statuses beyond HubSpot's default set, those are mapped via value mapping and your admin configures the destination pipeline stages accordingly.

Sercom engagement records map to HubSpot Engagements. Calls map to HubSpot calls with subject, duration, outcome, and recording URL preserved. Emails map as engagement emails with body content and timestamp. Meetings map with subject, start/end times, and the associated contact or deal link.

Sercom notes migrate to HubSpot Notes attached to the corresponding Contact, Company, or Deal record. The note body maps to HubSpot's note body property. If Sercom stores notes with create and update timestamps, those are preserved as HubSpot note metadata.

Sercom product or service line records map to HubSpot Products. Product name, description, price, and SKU map to the corresponding HubSpot Product properties. Products must exist before line items can attach to Deals in HubSpot, so we sequence the migration to load Products before Deals.

Sercom line item records attached to deals map to HubSpot Line Items with quantity, price, and product reference. The line item is linked to the migrated Deal via the dealId field. Each line item's product reference is resolved against the migrated Product records.

Sercom file attachments on contacts, companies, deals, or tickets are downloaded and re-uploaded to HubSpot Files. Each file is associated with the target record by ID after upload. HubSpot's file size limit is 250 MB per file; larger files are flagged for manual handling.

Sercom owner IDs are resolved by email address match against HubSpot Users. The owner email on each Sercom record is matched to a HubSpot user account; if no match is found, the record is assigned to a designated fallback HubSpot user and flagged in the migration report for admin review.