Migrate from MarketSharp to Salesforce Sales Cloud

MarketSharp's Lead object maps directly to Salesforce Lead. Standard fields (name, email, phone, company, source) migrate as-is. The split between MarketSharp Lead and Contact does not automatically map to Salesforce's Lead vs. Contact split — records with an active 'Job' in MarketSharp may route to Salesforce Contact if the relationship qualifies, otherwise they remain as Salesforce Leads. Owner resolution happens via email match against Salesforce users before records load.

MarketSharp Contact maps to Salesforce Contact with a direct AccountId lookup. MarketSharp contacts without a primary company get attached to a default 'Unassigned Account' placeholder record. For contacts with multiple associated companies in MarketSharp (N:N relationship), the primary company maps as AccountId and secondary associations surface as Account Contact Relations in Salesforce.

MarketSharp Company maps to Salesforce Account. Company name becomes Account Name, domain/website maps to Account Website, industry maps to Account Industry via value mapping against Salesforce's default pick-list, employee count maps to NumberOfEmployees, and annual revenue maps to AnnualRevenue. Parent-child company hierarchies in MarketSharp map to Account.ParentId — the parent company must migrate first; circular references are flagged before the full run.

MarketSharp Job is the core project object — it ties a contact, crew, job type, site address, and financial data to a single project record. It maps to Salesforce Opportunity with a direct Amount field (Job value or estimate), StageName mapped from Job status via value mapping, CloseDate set to Job completion date or estimated close, and Name set to Job title or Job number. MarketSharp job-type categories (e.g., 'Roofing', 'Kitchen Remodel') map to Salesforce RecordTypeId so each job type can have its own page layout and stage pick-list values.

Each MarketSharp job-type category creates a Salesforce RecordType on the Opportunity object. This is the highest-impact mapping decision in the migration — every job type needs its own RecordType so that stage pick-list values, probability, and forecast category are scoped correctly per job category. We deliver a RecordType setup plan (object name, label, description) before data lands in Salesforce.

MarketSharp job status values (e.g., 'Estimate Sent', 'Proposal Accepted', 'Job Won', 'Job Lost') map to Salesforce Opportunity StageName values per RecordType. Each RecordType has its own stage pick-list, so the value mapping is scoped by the job-type RecordType. Stage probability and forecast category re-applied based on Salesforce's stage model. Historical stage-entered timestamps preserved as custom datetime fields on the Opportunity.

MarketSharp appointments (with date, time, duration, assigned salesperson, crew, and product/job association) map to Salesforce Events. Original start time, end time, and owner are preserved. The 'crew' and 'product' associations in MarketSharp have no native Salesforce equivalent — these migrate as custom fields on the Event (Crew_Assignment__c, Job_Product__c) or as a lookup to a custom Job Visit object if your team wants to track multiple appointments per opportunity in a structured way.

MarketSharp follow-up tasks, call logs, and notes map to Salesforce Tasks with Type, Subject, Status, and Priority preserved. Original create dates surface as a custom Created_In_Source__c datetime field since Salesforce's CreatedDate is set at migration time. Owner resolved via email match to Salesforce users.

MarketSharp file attachments (proposals, photos, contracts) attached to Jobs or Contacts re-upload to Salesforce Files (ContentDocument / ContentVersion model). Salesforce's default per-file limit is 25MB — files larger than this are flagged and split or linked externally. Inline images in notes are downloaded and rehosted in Salesforce's file storage.

MarketSharp custom fields (e.g., 'Lead Source Detail', 'Referral Partner', 'Insurance Carrier', 'Roofing Square Footage') created under Settings → Custom Lead Fields require equivalent Salesforce custom fields. FlitStack AI creates these with the __c API suffix, applies the correct field type (text, picklist, number, date, checkbox), sets field-level security per profile, and assigns them to the correct page layouts before data loads. Custom field count is the primary driver of migration complexity and price.

If MarketSharp Jobs track line items or products (e.g., 'Shingle Package', 'Labor Rate'), these map to Salesforce Opportunity Products. A Pricebook and Product2 records must exist in Salesforce first — FlitStack creates these from MarketSharp product data during the migration prep phase, or maps against your existing Salesforce Pricebook if one is already configured.

MarketSharp notes attached to Leads, Contacts, or Jobs migrate as Salesforce Notes using the enhanced Notes object (not the legacy Note object). Rich-text formatting, bullet points, and embedded links are preserved during transfer. The parent record link in MarketSharp (associating the note to a specific contact, company, or job) maps to the Salesforce WhoId or WhatId field, linked to the corresponding Salesforce record ID generated during the migration run. For traceability, the original MarketSharp note create date and author are preserved in custom datetime and text fields on the Salesforce Note record.