Migrate from MARS to Freshsales

Discovery and data audit

We extract a full data dump from MARS covering Contacts, Companies, Deals, Activities, Owners, and custom objects. We document record counts per object, custom field definitions with data types, and pipeline stage configurations. We assess whether MARS uses a Lead object or a flat Contact model, and whether Deals are tied to Contacts directly or through an Account. The discovery output is a written migration scope with object-level mapping, field type matrix, and Freshsales tier recommendation based on API rate-limit requirements.

Freshsales schema provisioning

We pre-create the Freshsales schema including custom fields (matched to MARS field types), pipeline stages, and any required modules. If MARS exposes lead-score or custom scoring data, we create a numeric custom field in Freshsales to receive it. We validate the schema in a Freshsales sandbox or trial account before production migration begins.

Owner reconciliation and User provisioning

We extract every distinct owner email from MARS records and match against the Freshsales destination User table. Any Owner without a matching Freshsales User is listed in a reconciliation queue. The customer's Freshsales admin provisions the missing Users before record import proceeds. OwnerId references are required on Deal and Activity inserts, so this step gates the migration.

Account and Contact migration

We import MARS Companies as Freshsales Accounts first, using domain or company name as the dedupe key. MARS Contacts import second, with the Account lookup resolved at import time using the matched AccountId. Email serves as the Contact dedupe key. Any MARS Contact records with embedded company data generate an Account on the fly before the Contact insert.

Lead and Deal migration

We import MARS Leads (if present) as Freshsales Leads, preserving lead status and score fields. MARS Deals migrate as Freshsales Deals, linked to the resolved Account and Owner. Pipeline stages map to Freshsales pipeline stage values. We run row-count reconciliation after each phase before proceeding to the next.

Activity history migration

We migrate email, call, meeting, and task records in date order, batched to respect Freshsales API rate limits for the target tier. Calls tag the Task with call subtype fields. Meetings create Event records with EventRelation attendees. Emails create Task records of type Email with body content and direction preserved. Each Activity links to its parent Contact, Lead, or Deal via WhoId and WhatId.

Cutover and post-migration handoff

We freeze MARS writes during cutover, run a final delta migration of any records created or modified during the migration window, then declare Freshsales the system of record. We deliver the custom field mapping document, the report inventory, and the integration endpoint list. We support a one-week hypercare window for reconciliation issues. Workflows and automations are documented but not migrated as code; that rebuild is handled by the customer's admin.