Migrate from MarketSharp to HubSpot

MarketSharp leads map 1:1 to HubSpot contacts. All standard lead fields (name, email, phone, address, source) move as contact properties. Lead status values from MarketSharp map to HubSpot contact lifecycle stage or a custom lead status property depending on your HubSpot plan.

MarketSharp contacts map directly to HubSpot contacts. The contact's primary company is resolved via a HubSpot company lookup — the company record must be migrated first so the association links correctly. Multi-address contacts require flattening to HubSpot's single address property.

MarketSharp company records migrate one‑to‑one to HubSpot companies, preserving the company name, domain, industry, employee count, annual revenue, phone, and address as standard HubSpot company properties. Parent‑company hierarchies in MarketSharp translate to HubSpot parent‑company associations, maintaining the original relationship structure. Any custom company fields are recreated as HubSpot custom properties with matching labels and data types. Original create timestamps are retained in a custom field for reporting continuity.

MarketSharp jobs are the primary revenue record in the source system and translate to HubSpot deals. Job number is stored as a custom deal property (Job_Number__c). Job estimated value maps to deal amount. Job type drives deal stage or pipeline routing depending on how your HubSpot pipelines are configured.

MarketSharp job type pick-list values (e.g., Roofing, Siding, Remodeling) map to HubSpot deal stage names or pipeline names per your HubSpot pipeline configuration. We deliver a value-mapping table during the planning phase so your team can set the correct stage routing before migration.

MarketSharp appointment records migrate as HubSpot meetings, preserving the original start and end timestamps, subject line, assigned sales rep, and confirmation status as native meeting properties. Location, description, and attendee details are carried over where present. The reminder_date_time and reminder_sent flag are saved as custom meeting properties (Reminder_Date_Time__c and Reminder_Sent__c) because HubSpot manages reminders through workflows rather than as native fields. This preserves appointment context for reporting and automation design.

MarketSharp tasks migrate as HubSpot tasks, preserving subject, description, due date, priority, and task status as native properties. Owner resolution matches the MarketSharp owner email to a HubSpot user; unmatched owners are flagged for manual assignment before migration. Custom task fields are recreated as HubSpot custom properties with matching labels and data types, retaining specialized tracking such as billing codes or internal categories.

MarketSharp custom lead fields (created under Settings → Custom Lead Fields) are recreated as HubSpot custom properties on the appropriate object. Field type, pick-list values, and labels are matched exactly. We audit the full custom field list during the planning phase to identify which object each field belongs on.

Files attached to MarketSharp contacts, companies, or jobs are downloaded and re-uploaded to HubSpot Files, then associated to the corresponding CRM record. File size limits (25 MB per file in HubSpot) are enforced; oversized files are flagged for manual handling.

MarketSharp email logs become HubSpot email engagements on the associated contact or deal record. Call logs become HubSpot call engagements with duration and outcome preserved. Notes migrate as HubSpot notes with original create timestamps. Each engagement is linked to the parent contact or deal by ID.