Migrate from SalezShark to HubSpot

SalezShark's Lead object maps directly to HubSpot's Contact object. Email, name, phone, job title, and address fields migrate as HubSpot contact properties. The original SalezShark lead status value is preserved as a custom property for reporting continuity. All lead-to-contact associations are transferred using HubSpot's association API to preserve the relationship graph.

SalezShark Account maps to HubSpot Company. Company name, domain/website, industry, employee count, and annual revenue transfer as HubSpot company properties. Multi-branch account structures map to HubSpot's parent-company association where applicable. The mapping also preserves the original SalezShark account ID as a custom property on the HubSpot company record for cross-reference and audit trails.

SalezShark Deal migrates to HubSpot Deal. Deal name, amount, close date, and owner transfer directly. Pipeline and stage values require value-by-value mapping since the pick-list values differ between platforms. Historical stage-transition timestamps are preserved as custom datetime properties. The migration also records the original SalezShark deal ID as a custom property on the HubSpot deal to support future data reconciliation.

Each SalezShark pipeline becomes a HubSpot deal pipeline. The pipeline name maps as-is; stage names are mapped per pipeline on a value-by-value basis. Probability and forecast category are re-applied using HubSpot's stage-probability settings post-migration. The mapping also ensures that any custom pipeline-specific fields (e.g., product line or region) are transferred as custom properties on the deal object.

SalezShark activities (calls, emails, meetings, notes) map to HubSpot engagements. Original timestamps, owners, and parent-record links are preserved. Each activity type maps to the corresponding HubSpot engagement type so the timeline view renders correctly on the contact and deal records.

SalezShark custom fields on Contact, Account, and Deal objects require pre-creation of equivalent HubSpot custom properties before migration. Field types (text, number, date, pick-list, checkbox) are mapped to HubSpot property types. Pick-list values require value-by-value mapping where source and destination values differ.

SalezShark user records are matched to HubSpot owners by email address. Unmatched owners are flagged before migration — teams either pre-create HubSpot users or assign records to a fallback owner. Owner history on deals is preserved by linking the matched HubSpot owner ID.

SalezShark product catalog items map to HubSpot line items. Product name, unit price, quantity, and discount transfer as HubSpot line item properties. Line items are associated with deals via the HubSpot deal-to-line-item association. The migration also preserves the original product ID as a custom property on each line item to enable downstream reporting and reconciliation with external inventory systems.

SalezShark tasks migrate as HubSpot tasks. Subject, description, due date, completion status, and owner transfer directly. Parent-record links (contact, account, deal) are preserved using HubSpot's association model so tasks appear in the correct record timelines. The migration also retains the original SalezShark task identifier as a custom property for audit traceability.

SalezShark workflow definitions do not migrate. Professional-tier workflows built in SalezShark must be rebuilt using HubSpot's workflow tool or automation sequences. FlitStack AI exports the workflow definitions as a structured reference document for your HubSpot admin to use during the rebuild phase.

SalezShark marketing campaigns and mass email records have no direct HubSpot equivalent at the CRM level. Email campaign history is preserved as activity records on the contact timeline. Rebuilt campaigns in HubSpot use HubSpot's campaign tool and are handled separately from the data migration.

SalezShark lead status values (e.g., Open, Qualified, Converted) map to HubSpot deal status values. The mapping is one-to-one where values are identical; custom status values require explicit value-by-value mapping. Status change timestamps are preserved as custom datetime properties on the deal.

SalezShark document attachments linked to contacts, accounts, or deals are downloaded and re-uploaded to HubSpot's file manager. Files are associated with the corresponding record via HubSpot's file-to-record association. HubSpot's file size limit (25MB per file) applies to oversized attachments. During re‑upload, the original file name and creation timestamp are preserved as metadata properties to maintain document lineage.

SalezShark Fair Usage Policy flags and batch operation logs have no functional equivalent in HubSpot. These are preserved as read-only custom properties on the relevant records for audit continuity. The flags are informational only and do not affect HubSpot's operations.