Migrate from MarketSharp to Freshsales

MarketSharp leads map directly to Freshsales leads. The primary name, email, phone, and address fields translate 1:1. FlitStack resolves the MarketSharp salesperson field to a Freshsales owner user by email match before writing each record. During migration, FlitStack also validates email formats and flags duplicates to prevent re‑creation of existing Freshsales leads.

MarketSharp contacts map to Freshsales contacts. The contact's first name, last name, email, phone, and job title fields are direct translations. FlitStack preserves the MarketSharp contact ID in a custom field for traceability and delta-run deduplication. If a contact already exists in Freshsales, FlitStack matches by email and updates the existing record rather than creating a duplicate.

MarketSharp company records map to Freshsales accounts. Fields including company name, website, address, industry, and employee count translate directly. Parent-child company relationships in MarketSharp map to Freshsales's parent-account hierarchy. FlitStack also replicates the company type (e.g., prospect, partner) as a custom picklist in Freshsales to preserve classification during migration.

MarketSharp's Job object has no direct Freshsales equivalent — jobs are project records tied to a contractor lifecycle. FlitStack maps job records to Freshsales Deals, using the job name as the deal name, job value as the deal amount, and job status as the deal stage. Any job-specific fields without a standard Freshsales equivalent become custom fields.

MarketSharp appointments (meetings, site visits, calls) map to Freshsales Sales Activities. FlitStack preserves the original appointment date, duration, associated contact, and salesperson as owner. Activity type (call vs meeting) maps to Freshsales's Sales Activity type field. If a contact cannot be matched, FlitStack logs the activity under a fallback owner and flags the record for review.

MarketSharp custom lead fields (configured under Settings → Custom Lead Fields) require matching custom fields to be created in Freshsales before migration. FlitStack audits all custom fields, creates the corresponding Freshsales custom fields under the appropriate module, then maps values during migration.

MarketSharp salesperson records are resolved to Freshsales users by email match. If a MarketSharp salesperson has no matching Freshsales user email, FlitStack flags the record for your admin to either invite the user to Freshsales first or assign records to a fallback owner.

MarketSharp lead source values (referral, website, google_ads, etc.) map directly to Freshsales lead_source pick-list values. If MarketSharp uses a custom lead source value not in Freshsales's default list, FlitStack creates it as a custom pick-list option before migration. This ensures every lead's origin is preserved in Freshsales for reporting.

MarketSharp products and service items map to Freshsales Products. Product name, unit price, and description fields translate directly. FlitStack preserves the MarketSharp product ID in a custom field for reconciliation. During import, FlitStack also maps product categories to Freshsales's product families, enabling straightforward filtering and reporting by product line.

MarketSharp file attachments associated with jobs or contacts are re-uploaded to Freshsales as Files linked to the corresponding record. FlitStack downloads each file, re-uploads to Freshsales, and preserves the original filename and attachment date. If a file exceeds Freshsales's size limit, FlitStack stores a reference URL and notifies the admin to handle the file manually.

MarketSharp estimates and proposals are tied to jobs and have no native Freshsales equivalent — Freshsales has a Products catalog and a CPQ add-on, but estimates are not a standard object. FlitStack preserves estimate line items as Deal Products linked to the migrated Deal, or stores them as a custom field reference for manual reconstruction.

MarketSharp workflow rules do not export from the platform. FlitStack documents your active workflow rules during the discovery phase so your Freshsales admin has a rebuild reference. Freshsales workflows must be configured post-migration in Admin → Workflows. We recommend scheduling a workflow design workshop post‑migration to align automations with your updated sales process.