Migrate from Sharpspring to monday CRM

SharpSpring contacts map directly to Monday CRM People entities. Each contact's name, email, phone, and custom properties become the Person record's corresponding fields and custom columns. SharpSpring contacts without an email are flagged for manual review before import since Monday requires an email for People creation.

SharpSpring company records map to Monday CRM Organizations. Company name, domain, industry, employee count, and annual revenue become Organization fields. Multi-company associations on a single SharpSpring contact are preserved by linking the primary Organization and surfacing secondary companies as text in a custom column.

SharpSpring deals map to Items on Monday CRM deal boards. Each deal's name, amount, close date, and owner become Item columns. The SharpSpring pipeline stage value maps to the Monday Status column option, preserving the stage name and associated probability as a number column for reference.

Each SharpSpring deal pipeline becomes a Monday CRM Board. The board name matches the pipeline name. SharpSpring stage names are created as Status column options on that board. Stage order and probability are preserved in a companion number column for forecasting continuity.

SharpSpring does not separate Leads and Contacts at the object level the way traditional CRMs do. We map all SharpSpring contacts to Monday People regardless of lifecycle status. For reporting continuity, we flag contacts that were actively worked as opportunities in SharpSpring using a custom Status column (e.g., New, Working, Qualified).

SharpSpring engagement records — emails logged, calls recorded, meetings scheduled, and notes — migrate as Updates on the related Monday Item with original timestamps and owner attribution. Each update records the activity type, subject, and body so the full contact history is visible in the Monday Item timeline.

SharpSpring tags applied to contacts and deals migrate as Monday Labels (if the board uses the Labels column type) or as comma-separated text in a custom Text column. We preserve all tag values so segmentation logic referenced in SharpSpring automations can be reconstructed using Monday's filtering capabilities.

SharpSpring custom contact properties (field-level custom fields created by the user) become Monday custom columns on the People entity. Field type determines the Monday column type: text properties map to Text columns, pick-list properties map to Dropdown columns with value-by-value mapping, and date properties map to Date columns.

SharpSpring custom deal properties migrate as custom columns on deal board Items. For deal-specific pick-list values (e.g., deal type, product line), we map each SharpSpring option to a Monday Dropdown value. Custom number fields (e.g., deal probability override) map to Monday Number columns.

SharpSpring's VisitorID tracking generates anonymous visitor profiles and behavioral data (pages visited, session duration) that has no Monday CRM equivalent. We preserve the raw tracking data as a custom Text column for reference, but the behavioral intelligence layer must be rebuilt using Monday integrations or a separate analytics tool post-migration.

SharpSpring's numeric lead score (calculated from page visits, email engagement, and form fills) has no native equivalent in Monday CRM. We copy the score value to a custom Number column on the Person record. The automated scoring logic itself — how points accumulate per behavior — must be rebuilt in Monday using formula columns or an external scoring tool.

SharpSpring form submissions are preserved as Updates on the associated contact's Monday Person record, documenting the form name, submission date, and all fields submitted. Landing page context including the source URL, referring domain, and UTM parameters (utm_source, utm_medium, utm_campaign) is preserved as text within the update body so the acquisition channel context remains visible in Monday's timeline for each contact.