Migrate from FunnelMaker to Freshsales

Discovery and export coordination

We audit the FunnelMaker account for contact count, company count, opportunity count, pipeline count and stage configuration, user-defined custom fields, active workflows and drip campaigns, activity history volume, and lead scoring rules. Because FunnelMaker lacks a public API, we coordinate with the customer to run in-product CSV exports for Contacts, Companies, Opportunities, and Activities. We provide export templates and a checklist to ensure all custom fields are included in the export before extraction begins. The discovery output is a written migration scope with object counts, custom field inventory, and pipeline stage mapping.

Schema design and Freshsales field mapping

We design the destination schema in Freshsales. This includes renaming the four standard modules (Lead, Contact, Account, Deal) to match the customer's terminology, pre-creating all custom fields with the correct types (text, number, date, picklist, checkbox, currency, phone, URL), configuring Deal Pipelines and stage names to match the FunnelMaker pipeline structure, and defining the Lead-to-Contact conversion mapping if Leads will be used. Schema is configured in Freshsales Admin Settings before any data import.

Data cleansing and test import

We review the exported CSV files for data quality issues: duplicate contacts, missing required fields, inconsistent date formats, and invalid picklist values. We recommend the customer run a test import in Freshsales using a subset of records before the full migration to validate field mapping and identify any data issues. Freshsales provides a CSV import tool in Admin Settings that we use for test runs, and we reconcile record counts after each test import before proceeding to full migration.

Account and Contact migration in dependency order

We run production migration in record-dependency order: Accounts (from FunnelMaker Companies), Contacts (with AccountId resolved), Deals (with pipeline, stage, and owner resolved). FunnelMaker Contacts without pipeline associations are mapped to Leads or Contacts based on the conversion mapping defined during scoping. Owner resolution maps FunnelMaker user email to Freshsales User by email match; any unmatched owners go to a reconciliation queue for the customer's admin to provision before import resumes.

Activity history migration

We migrate FunnelMaker activity history (calls, emails, tasks, appointments, notes) as Freshsales Tasks and Appointments linked to the parent Contact, Account, or Deal record. Call metadata (duration, timestamp, owner, linked contact) migrates as Task records with Call subtype. Emails, tasks, and notes migrate as Task records with appropriate activity type indicators. Notes migrate as Freshsales Notes attached via the parent record link. We do not migrate call recording audio files or transcription text.

Cutover, validation, and workflow handoff

We freeze FunnelMaker writes during cutover and run a final delta migration of any records modified during the migration window. We deliver a reconciliation report comparing FunnelMaker record counts to Freshsales record counts for each object. We deliver the workflow and drip campaign documentation inventory to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild FunnelMaker workflows as Freshsales Workflows inside the migration scope; that is a separate engagement or an internal admin task.