Migrate from Sellsy to HubSpot

Direct map. Sellsy contacts migrate to HubSpot contacts preserving firstname, lastname, email, phone, job title, and address fields. Owner resolved by email match to HubSpot users. Companies linked via HubSpot association if the Sellsy contact has a primary company set.

Direct map. Sellsy company records map to HubSpot companies with name, address, phone, email, website, and industry preserved. Parent-child relationships from Sellsy (parent_id field) require HubSpot association labels or a custom parent_company property since HubSpot uses flat company hierarchy without native parent-child support. We store the parent company name or Sellsy ID for reconstruction if needed.

Direct map. Sellsy deal records migrate as HubSpot deals with pipeline and stage mapping value-by-value. Amount, close date, currency, and owner preserve from Sellsy. Probability percentages per stage transfer to HubSpot dealstage probability fields. Custom fields on deals become HubSpot deal properties created during the schema design phase before migration begins.

Sellsy pipelines with their configured stages and probabilities become HubSpot deal pipelines. We create the HubSpot pipeline structure first, then map stages with probability percentages preserved. Each Sellsy pipeline generates one HubSpot pipeline. Stage ordering and any closed-won/closed-lost stages align to HubSpot's pipeline configuration requirements.

Sellsy invoices do not have a direct HubSpot equivalent — HubSpot has no native billing module. We map invoices to HubSpot quotes where the quote object is available, or create a custom object (Invoice) to preserve billing history. Line items, totals, due dates, and payment status transfer. The mapping approach is defined during schema design based on your HubSpot plan and billing workflow requirements.

Sellsy quotes and proposals map to HubSpot quotes with subject, amount, line items, validity dates, and status preserved. Attachments to quotes re-upload as HubSpot files linked to the quote record. Quote status values map to HubSpot quote_status pick-list using value mapping for each status category.

Sellsy tasks migrate as HubSpot tasks with subject, body text, due date, and completion status preserved. Owner resolves by email match to HubSpot portal users. Tasks without a due date still migrate with status field populated. Recurring task patterns in Sellsy do not transfer — those require manual recreation in HubSpot's task and workflow system.

Sellsy calendar events map to HubSpot meetings with start time, end time, location, title, and attendee information preserved. Original timestamps on events retained in HubSpot meeting properties. Conference call links and meeting body content transfer to HubSpot meeting records associated with the relevant contact or company.

Sellsy email records synchronized via email integration migrate as HubSpot email engagements on the contact timeline. Subject, body content, direction (sent or received), and timestamp preserve through the migration. Association to contact records maintained for full conversation history visibility within each contact's HubSpot timeline.

Sellsy notes migrate as HubSpot notes on the associated contact or company record. Rich-text formatting in note body preserves where Sellsy supports it. Note body content maps directly to HubSpot note body. Attachments on notes re-upload as HubSpot files and re-link to the migrated note record. Notes without a parent record are flagged for manual association during migration review.

Sellsy staff records resolve to HubSpot owners by email match against your HubSpot portal user list. Unmatched staff members are flagged before migration begins — your team can invite them to HubSpot as users or assign their records to a fallback owner. This owner resolution step ensures all migrated records retain proper assignment to the correct team members in HubSpot.

Sellsy custom fields require HubSpot custom property creation before migration runs. We create properties with matching types (text, number, date, datetime, checkbox, picklist) during the schema design phase. Picklist custom fields need HubSpot pick-list value set configuration — we map values by name. Property limits apply on Starter tier (500 total) so we validate scope during planning to confirm your plan accommodates the migrated schema.

Sellsy SmartTags on contacts and companies become HubSpot custom properties (multi-select for tagging taxonomy) or association labels depending on usage pattern. SmartTags on deals map to deal properties or pipeline-stage-specific labels. We analyze SmartTag usage during audit to determine the optimal mapping approach for each tag category in your Sellsy instance.

Sellsy product catalog items migrate as HubSpot products with name, price, description, and unit preserved. Products associated with deals link via HubSpot deal line items after migration. Inventory quantities transfer if your HubSpot plan includes inventory management, otherwise product records contain pricing and description for quote and deal line item reference.

Sellsy document attachments on contacts, companies, or deals re-upload to HubSpot Files with original filenames and MIME types preserved. Files re-attach to the migrated record in HubSpot using the appropriate association type. Large file attachments may require additional processing time during migration. All attachments associate to the parent record to maintain complete document history in HubSpot.