Migrate from Sharpspring to HubSpot

SharpSpring contacts map 1:1 to HubSpot contacts. The primary company association migrates as a HubSpot company association. Contacts without a company are created as standalone HubSpot contacts. Original SharpSpring create dates are preserved as a custom datetime field since HubSpot's native CreatedDate reflects the migration timestamp.

SharpSpring lead scores (fit + engagement) migrate as a custom numeric property on the HubSpot contact record. FlitStack creates the custom property during setup. No native HubSpot equivalent exists for SharpSpring's separate lead scoring page, so the score is stored as a static value at migration time — ongoing scoring requires rebuilding in HubSpot workflows.

SharpSpring contact stages are tracked via workflow membership and list membership rather than a single property. FlitStack maps the most-recent workflow-exited stage to HubSpot's lifecycle_stage pick-list (subscriber, lead, MQL, SQL, opportunity, customer). Stage transitions that SharpSpring tracked over time become a single lifecycle value in HubSpot; original stage history is preserved in a custom audit field.

SharpSpring companies map to HubSpot companies. Company domains, industry values, employee counts, and annual revenue migrate as HubSpot company properties. SharpSpring parent-child company hierarchies map to HubSpot's associated company relationships. Multi-company associations on SharpSpring contacts collapse to the primary company association in HubSpot.

SharpSpring deals map to HubSpot deals. Each SharpSpring deal pipeline maps to a named HubSpot pipeline. Deal stage names are mapped value-by-value to HubSpot stage names within the corresponding pipeline. Deal amount, close date, owner, and custom deal fields migrate directly. Unmapped custom deal fields require HubSpot custom deal properties created during setup.

SharpSpring form submission events — which form was filled, submission date, and field values — migrate as engagement notes on the HubSpot contact record. Form names and submission timestamps are preserved. Field values from SharpSpring forms that map to known HubSpot contact properties are migrated to those properties; unmapped fields are stored in custom properties on the contact.

SharpSpring email send and open events (from Smart Mail and tracked emails) migrate to the HubSpot contact's email activity timeline. Subject, send date, open date, and click data are preserved as engagement records on the contact. HubSpot's native email tracking recreates the engagement log for new emails going forward.

SharpSpring VisitorID captures anonymous visitor page views and correlates them with contacts by email after form submission. HubSpot has no equivalent anonymous-to-contact correlation model. Visitor page view history is preserved as a custom multi-line text property on the HubSpot contact for reference, but the behavioral timeline from anonymous visits cannot be fully reconstructed in HubSpot without rebuilding tracking from day one.

SharpSpring notes and tasks attach to contacts and companies. Notes migrate as HubSpot notes on the contact or company record with original timestamps and note body content preserved. SharpSpring tasks migrate as HubSpot engagement tasks linked to the contact record. Owner assignments on notes and tasks are resolved by email match to HubSpot users.

SharpSpring custom objects migrate to HubSpot custom objects, but HubSpot Custom Objects require an Enterprise-tier account. FlitStack flags this requirement before migration. If the HubSpot account is not Enterprise, SharpSpring custom object records are migrated as custom properties on the closest standard object (Contact or Deal) and the limitation is disclosed in the migration plan.

SharpSpring workflow membership and campaign list assignments do not have a direct HubSpot equivalent. SharpSpring workflow history (which workflows a contact was enrolled in and when) is exported as a custom text property on the contact for audit reference. Rebuilding enrollment logic requires creating HubSpot lists and workflows from the SharpSpring workflow definitions exported as part of the migration package.

SharpSpring file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot's file manager. Files are then associated with the corresponding HubSpot record. File size limits per HubSpot's upload constraints apply (25MB per file). Inline images embedded in SharpSpring notes are extracted, re-uploaded, and re-linked in HubSpot notes.