Migrate from MarketSharp to HighLevel

MarketSharp stores contact records as 'Leads' or 'Customers' in its CRM. These map directly to HighLevel Contacts. The contact's email, phone, name, address, and company association transfer as standard HighLevel fields. Contacts without a company link create as standalone HighLevel contacts with a tag marking their original MarketSharp status.

MarketSharp company records—including business name, address, website, and industry—map directly to HighLevel Companies using a one‑to‑one field correspondence. The company's primary contact is linked through HighLevel's built‑in contact‑company association, preserving the relationship. If MarketSharp contains parent‑child or hierarchical company structures, those relationships are replicated in HighLevel using the Company‑to‑Company link feature, ensuring that corporate groups remain intact after migration.

MarketSharp Jobs are the core sales object representing a contractor project or service sale. Jobs carry properties like job type, product category, status, estimated amount, and appointment data. In HighLevel, Jobs map to Opportunities with a custom field (Job_Type__c or similar) preserving the original MarketSharp job type category. Each MarketSharp job status becomes a HighLevel pipeline stage.

MarketSharp custom lead fields (contractor-specific properties like 'Project Type', 'Referral Source', 'Insurance Claim #') have no direct HighLevel equivalent. FlitStack creates matching custom fields on the HighLevel Contact object before migration and populates them with values from MarketSharp. Field types (text, picklist, date, number) are matched to their HighLevel equivalents.

MarketSharp allows custom fields on job records beyond the standard job properties. These migrate to custom fields on HighLevel Opportunities. The job-specific nature requires a custom field prefix (e.g., MS_Job_Custom_) to distinguish them from contact-level custom fields during the migration.

MarketSharp stores appointments with date, time, assigned salesperson, and appointment type. HighLevel's Calendar Events capture the same data — start/end time, assigned user, and a custom field for the original MarketSharp appointment type. Cancelled or rescheduled appointments migrate as completed events with a status flag preserved in a custom field.

MarketSharp notes attached to contacts or jobs migrate to HighLevel Contact Notes. Notes preserve the original create date (as a custom date field since HighLevel Notes use insertion time), the creating user (matched by email to HighLevel users), and the note body text. Notes linked to specific jobs carry a tag linking them to the corresponding Opportunity.

MarketSharp stores contact labels such as 'Hot Lead', 'Insurance Job', or 'Referral' as tags attached to each record. HighLevel provides a native Tags object that can be applied to contacts, companies, and opportunities. FlitStack transfers every MarketSharp label to a matching HighLevel tag using the same spelling and casing, so the original segmentation logic remains intact and can be used for filtering, reporting, and automation in the new system.

MarketSharp assigns jobs and contacts to salespeople. HighLevel assigns records to users by email match. FlitStack resolves MarketSharp owner names or IDs to HighLevel user email addresses. Unresolved owners are flagged before migration — you either invite them to HighLevel first or assign their records to a fallback user.

MarketSharp divisions organize data by team or branch. HighLevel's sub-account model isolates data per client or team. If your MarketSharp account uses divisions to separate client data, these map to separate HighLevel sub-accounts. If divisions separate internal teams within one business, they map to a custom tag (Division__c) on contacts and opportunities instead.

MarketSharp allows file attachments on job records (proposals, photos, contracts). HighLevel does not store files natively on Opportunities. FlitStack extracts file URLs from MarketSharp and stores them in a custom field (MS_Attachments__c) on the Opportunity as a text list of download links. For critical files, an external storage strategy (Google Drive, Dropbox) is recommended post-migration.

MarketSharp proposals and estimates are linked to jobs but stored as separate records. HighLevel does not have a native proposal object. The proposal amount, status, and link are merged into the corresponding Opportunity as custom fields (Proposal_Amount__c, Proposal_Status__c, Proposal_Link__c). Full proposal documents require a separate file migration step.