Migrate from Soffront to HubSpot

Soffront contacts migrate directly to HubSpot contacts. Each contact's primary AccountId in Soffront maps to the primary Company association in HubSpot. Contacts without a Soffront AccountId are created as HubSpot contacts with no company association — users can merge them with companies later in HubSpot.

Soffront accounts map directly to HubSpot companies. The parent‑/child hierarchy in Soffront is translated to HubSpot’s parent‑company property, and the primary contact for each Soffront account becomes the association on the corresponding HubSpot company. Industry, address, and phone fields are mapped one‑to‑one, while multi‑account contacts are added as secondary company associations using HubSpot’s company‑associations model. The Soffront account ID is stored in a custom property for reference and duplicate detection.

Soffront deals map to HubSpot deals. The Soffront pipeline field maps to the HubSpot pipeline property, and dealstage maps to dealstage. Multiple Soffront deal pipelines each become a named pipeline in HubSpot — Sales Hub Professional is required for multiple pipelines.

Soffront users are matched to HubSpot owners by email address. If a Soffront user has no matching HubSpot user, their records are assigned to a designated fallback owner and the unmatched user list is surfaced in the migration report for your team to provision HubSpot seats before cutover.

Soffront Groups serve both collaboration and access‑control purposes, defining record‑level permissions for users. HubSpot Teams are organizational and do not enforce access by default. We map each Soffront group to a HubSpot team, using the group name as the team name, and we export a report flagging where Soffront’s group‑based record assignments require HubSpot sharing‑rule replacements. Your HubSpot admin can configure sharing rules to emulate the access‑control logic after migration.

Soffront tickets migrate to HubSpot tickets with status, priority, and assignment preserved, and custom ticket fields are mapped to HubSpot custom properties. Soffront ticket categories are translated to HubSpot ticket pipelines, and Soffront workflows become pipeline stages in HubSpot. Ticket activity history—comments, status changes, and attachments—is converted to HubSpot ticket engagement records while retaining timestamps. The Soffront ticket ID is stored in a custom property for reference and duplicate detection.

Every Soffront custom field on Contacts, Accounts, or Deals requires a corresponding HubSpot custom property created before import. We deliver a property-creation checklist from Soffront's field schema so your HubSpot admin creates them in advance. Property type (text, number, date, select) is inferred from Soffront's field type metadata.

Soffront custom objects map 1:1 to HubSpot custom objects. This is only available on HubSpot Enterprise tiers. If your destination is HubSpot Starter or Professional, custom objects are preserved as custom properties on the standard Contact or Company object with a note for manual re-evaluation.

Soffront Business Rules Engine workflows have no import path to HubSpot. We export your Soffront workflow definitions (rule conditions, actions, and stage transitions) as a structured JSON reference document. Your HubSpot admin uses this to rebuild equivalent logic in HubSpot Workflows. Workflow migration is not included in the data migration scope.

Soffront call logs, email logs, meeting records, and notes map to HubSpot engagements. Original timestamps and associated contacts are preserved. Soffront notes with rich text are converted to HubSpot note format; attachments are downloaded and re-uploaded to HubSpot's file manager and attached to the corresponding record.

Soffront knowledge base articles are standalone content records with no direct HubSpot equivalent. HubSpot's Knowledge Base is tied to the Service Hub and serves help-center purposes. We export KB articles as HTML files and provide a mapping to HubSpot article structure — your team uploads them to the HubSpot knowledge base manually after migration.

Soffront projects track milestones, resources, and managers. HubSpot has no native project management object. Projects are exported with full detail and assigned to a HubSpot custom object or preserved as a CSV reference sheet — your team chooses the destination in HubSpot after migration.