Migrate your Sharpspring data

SharpSpring's primary data object. Contacts export cleanly as CSV including standard fields (name, email, phone, company). Custom properties are preserved in the export but must be mapped to the destination's field schema. Lead scores and lifecycle stages are included in the export where configured.

SharpSpring's company-level record for grouping contacts. The Account-to-Company mapping depends on whether the destination uses a separate Account/Company object or collapses companies into contact records. We map the Account name and link contacts to the destination's equivalent.

SharpSpring applies Tags to Contacts for segmentation. Tags are free-form string values exported in the contact CSV. We preserve them as Tags in the destination, but where the destination uses a different tagging model (e.g., HubSpot's separate Labels object), we map them into the closest equivalent and flag any that may need manual reassignment.

SharpSpring supports both static lists and dynamic lists (powered by query rules). Dynamic list logic does not export and must be recreated in the destination as segmentation rules. Static list membership is preserved by mapping each contact to the destination list. We flag which lists are dynamic and document their rule logic for manual rebuild.

SharpSpring's Campaigns are containers for tracking email sends and automation assignments. The campaign name and status export, but the campaign's email performance metrics (opens, clicks) are SharpSpring-internal and do not carry over. We map campaign names and link associated contacts to the destination campaign.

SharpSpring Forms capture lead data and map directly to CRM fields. Form definitions export as field lists, but the form layout and styling do not transfer. We export the field mappings and recommend recreating forms in the destination using those mappings. Custom fields referenced by forms must be created first.

SharpSpring Landing Pages are built on a proprietary page builder and have no export mechanism. HTML export is not available. We cannot migrate landing page content directly; we document the page structure and content so it can be rebuilt in the destination platform. We recommend capturing screenshots and key copy during the migration scoping call.

SharpSpring email templates include HTML body, text version, and embedded images. We export the HTML and extract images to a file package for re-upload. The template name and subject line are preserved. Dynamic content blocks and personalization tokens must be identified and mapped to the destination's equivalent syntax.

SharpSpring's Visual Workflows are action-and-trigger-based automations that have no native export or API retrieval. Workflow logic must be manually documented from the UI and rebuilt in the destination. We provide a workflow audit worksheet during scoping to capture each automation's triggers, conditions, and actions for manual rebuild. This is the highest-effort object in any SharpSpring migration.

SharpSpring's lead scoring model assigns numeric scores based on behavioral and demographic rules. Scoring rules export as a configuration export, but scores themselves are recalculated in the destination based on rebuilt rules. We map the scoring model and flag which contacts have high scores so they can be prioritized post-migration.

VisitorID tracks anonymous website visitors before they convert to contacts, mapping IP addresses to company names and page visits. This data is tied to SharpSpring's tracking infrastructure and cannot be exported. The anonymous visitor history is lost on migration. We flag this for customer awareness and recommend capturing any named conversions before the cutover.

SharpSpring custom fields on Contacts, Companies, and Deals are exported in the contact CSV but require manual creation in the destination before import. We produce a field-mapping worksheet listing each custom field's name, data type, and picklist values so the destination fields can be configured in advance of the import.