Migrate from SalesTown CRM to HubSpot

SalesTown leads map directly to HubSpot contacts. The SalesTown lead status value (New, Contacted, Qualified, Lost) is preserved as a custom HubSpot pick-list property called SalesTown_Lead_Status__c so your team retains the original classification in HubSpot reporting. Email and phone are the primary match fields.

HubSpot's lifecycle_stage is a required property for automation gating. SalesTown's lead status values map to lifecycle_stage values: 'New' and 'Contacted' route to 'Lead', 'Qualified' routes to 'SQL', and 'Lost' routes to 'Subscriber' with a note flag. Your team confirms the mapping table before migration runs.

When SalesTown contacts are separate from leads (distinct records), they migrate directly to HubSpot contacts. If SalesTown stores contact and lead data in the same object, the mapping uses the SalesTown record type or a status flag to determine lifecycle routing. All standard contact fields (name, email, phone, title, address) map one-to-one.

SalesTown organizations map to HubSpot companies. Company name, domain/website, industry, employee count, and annual revenue fields map directly where they exist. Industry pick-list values are mapped value-by-value against HubSpot's default industry set. Missing HubSpot industry values are set to 'Other' and flagged for your admin to resolve.

SalesTown deals migrate to HubSpot deals. Deal name, amount, expected close date, owner, and stage name all map to HubSpot deal properties. The SalesTown deal stage name is mapped to the HubSpot pipeline stage pick-list value — this requires a value-mapping table that your team approves before migration runs. HubSpot deal owner is resolved by email match against HubSpot users.

SalesTown pipelines map to HubSpot pipelines. Each SalesTown pipeline creates a corresponding HubSpot pipeline with its own stage set. Stage names, probabilities, and display order are mapped from SalesTown's pipeline configuration. If SalesTown uses one pipeline, it becomes HubSpot's default pipeline — additional pipelines can be added post-migration.

SalesTown call logs migrate as HubSpot engagements with engagement type 'Call'. Subject, call disposition, duration, and timestamp are preserved. The HubSpot engagement links to the parent contact and company record using the original SalesTown association data. Original call owner is resolved by email match to a HubSpot user.

SalesTown email logs migrate as HubSpot email engagements. Subject, body, timestamp, and direction (sent/received) are preserved. The engagement attaches to the HubSpot contact and company records that correspond to the original SalesTown association. Email attachments are downloaded and re-uploaded to HubSpot Files linked to the engagement.

SalesTown meeting records migrate as HubSpot meetings with original start time, end time, location, and body text preserved. The meeting engagement links to the associated contact(s) and company in HubSpot. Meeting owner resolves by email match to a HubSpot user.

SalesTown notes migrate as HubSpot notes or engagement notes. The original note body, create date, and note owner transfer to HubSpot. Rich-text formatting in SalesTown notes is preserved where the format is supported; unsupported formatting is stripped and flagged. Notes link to the associated contact or company record.

Files attached to SalesTown contacts, companies, or deals are downloaded from SalesTown storage and re-uploaded to HubSpot Files. The original file name, upload date, and uploader are preserved as HubSpot file metadata. Files are associated with the corresponding HubSpot records after upload. File size limits apply per HubSpot's file storage policy.

SalesTown's quotes module does not have a native HubSpot equivalent. HubSpot handles pricing through the Products + Line Items object and a separate Quotes object (available in Sales Hub Professional and above). We migrate quote content as a custom HubSpot object with the quote fields (line items, totals, tax, discount) preserved as custom properties so the historical quote data is accessible even if the quote cannot be opened as a live HubSpot quote.

Every SalesTown custom field becomes a HubSpot custom property. The property name is normalized to HubSpot's camelCase naming convention (e.g., referral_source becomes referralSource). Property type is mapped: text → string, number → number, date → date, picklist → enumeration. All custom properties must be pre-created in HubSpot settings before the migration load — we deliver a HubSpot setup checklist with every custom property definition before data lands.

SalesTown workflows, automated rules, WhatsApp triggers, and email automation sequences do not migrate. They must be rebuilt in HubSpot's workflow engine. FlitStack AI exports your SalesTown workflow definitions (rule triggers, conditions, and action sequences) as a structured reference document your HubSpot admin can use to rebuild the logic in HubSpot Workflows or Sequences.

Report and dashboard definitions do not migrate. The underlying data (contacts, companies, deals, activities) migrates, so your team can build equivalent HubSpot reports from the same data after go-live. We document the SalesTown report names and field references as a rebuild guide so your admin knows which HubSpot reports to create for each retired SalesTown report.