Migrate from SuperOffice CRM to HubSpot

SuperOffice Contact (associate) records map directly to HubSpot contacts. Email, phone, address, and title fields carry over. Owner assignment uses email match against HubSpot users. SuperOffice's N:N contact-company relationship (via ContactLink table) maps to HubSpot's associative Contact-Company relationship record using HubSpot's association API.

SuperOffice Company records map to HubSpot companies. Name, address, phone, and domain map directly. Parent-company hierarchies map to HubSpot's parent-company property. Multi-company N:N links with contacts are resolved via the association API at migration time. The mapping also preserves original company identifiers and ensures that any subsidiary relationships are reflected as parent-company links in HubSpot.

SuperOffice Sale records map to HubSpot deals. Deal name, amount, close date, and probability migrate directly. The sale's pipeline (SaleType) becomes a custom property (Sale_Type__c) and a HubSpot deal stage mapping plan is delivered before migration runs. During the mapping, we capture the original sale heading and preserve it as a custom field, ensuring historical context is retained in HubSpot.

SuperOffice sale types (named pipelines) have independent stage definitions stored in SaleStageLink. We map each sale type to a HubSpot deal stage range and create a Sale_Type__c custom picklist property on deals to preserve which pipeline the deal originated in.

SuperOffice diary entries (appointments) map to HubSpot meetings with subject, start/end time, location, and original owner preserved. The SuperOffice appointment-done flag (completed/incomplete) translates to a meeting status note. All meeting details including attendee list, description, and any linked contacts are transferred to HubSpot, with the original create timestamp recorded for audit purposes.

SuperOffice document links attach to multiple parent records simultaneously. We re-upload document content to HubSpot Files and attach to the relevant contact/company/deal as a file record. A note on the primary record points to the file for cross-object document scenarios.

SuperOffice Project has no native HubSpot equivalent. We create a Project__c custom object for project headers and map project members (associates) to HubSpot contacts or companies with the project association label preserved. Tasks and milestones map to custom task and milestone child custom objects.

SuperOffice project memberships (associate-to-project links) map to custom Project__c association records. The associate's role in the project (project leader, member) becomes a role property on the association. Each association record also stores the associate's email for owner matching and captures any specific permissions assigned in SuperOffice, which are translated into HubSpot team access settings.

SuperOffice tickets (Customer Service module) map directly to HubSpot support tickets. Ticket title, status, priority, category, and description carry over. Source channel (email, phone, web) maps to a custom ticket source property. All ticket attachments are migrated as HubSpot file links, and any internal notes are preserved as ticket conversations for complete context.

SuperOffice selections are dynamic record groupings with filter criteria stored in the database. We export selection definitions and recreate them as HubSpot static lists or active lists. Dynamic rule-based lists require manual rebuild in HubSpot's list builder. During the export, we capture each selection's creation date and owner, which can be used to prioritize rebuild efforts in HubSpot.

SuperOffice associates map to HubSpot owners via email matching. We flag any associate records without a matching HubSpot user email before migration. SuperOffice role and rights configuration does not migrate — it is a destination-side schema item rebuilt in HubSpot's access-control model.

SuperOffice user-defined fields on any object map to HubSpot custom properties. Field types (text, number, date, picklist, decimal) are translated to the nearest HubSpot type. Multi-value picklists require custom property creation with specific value mapping. We also log the original SuperOffice field IDs to support future audits and to help rebuild any dependent reports or integrations in HubSpot.