Migrate from Pipeline CRM to Freshsales

Pipeline CRM Companies map directly to Freshsales Accounts. Company name serves as the dedupe key during import. Account is created first in the load sequence so that the lookup reference is satisfied when People and Deals import. Industry, size, revenue, and custom Company fields migrate to Freshsales custom Account fields after identically-named fields are created in Freshsales Admin settings first.

Pipeline CRM People can import as Freshsales Leads (then convert post-migration) or as direct Contacts attached to Accounts. We determine the strategy during scoping: teams with clean pre-sale qualification in Pipeline CRM's lifecycle use Leads; teams that have already qualified all contacts use direct Contact import to avoid the conversion step. Email address is the unique identifier for dedupe in both paths. Phone, address, and custom Person fields migrate after Freshsales custom Contact fields are provisioned with matching names and types.

Pipeline CRM Deals map to Freshsales Deals with the Company lookup resolved via Company name match to the Account created in Phase 1. Deal value, stage, probability, and expected close date migrate directly. Pipeline stages map to Freshsales deal stages by name; stages without a match in Freshsales default to the first stage of the admin-default pipeline. Pipeline CRM allows multiple pipelines, but Freshsales caps total pipelines at 10—deals from additional pipelines consolidate to the first stage of the admin-default pipeline, which we flag during scoping.

Each Pipeline CRM deal pipeline maps to a Freshsales Pipeline. Freshsales supports up to 10 pipelines total; if Pipeline CRM has more than 10, we consolidate remaining pipelines' deals into the admin-default pipeline's first stage and document the full stage mapping for the admin to reconcile post-migration. Stage probability percentages migrate from Pipeline CRM to Freshsales deal stage probabilities.

Pipeline CRM Activities linked to People or Companies migrate as Freshsales Activities attached to the corresponding Contact or Account. Email content migrates as Activity notes; call duration and disposition migrate to custom Activity fields. Pipeline CRM's Agenda Events migrate as Freshsales Appointments via the Appointments CSV import type. Freshsales does not migrate email body content from Pipeline CRM Activities into a native email timeline—email activity migrates as Activity records with the timestamp and a content note.

Pipeline CRM Agenda Tasks map to Freshsales Tasks via the Tasks CSV import. Due date, assignee (resolved by email to Freshsales User), status, and priority migrate directly. Tasks without a matching Freshsales User go to a reconciliation queue for the admin to provision. Completed status migrates as Completed in Freshsales.

Pipeline CRM custom fields defined on Company, Deal, and Person objects migrate to Freshsales custom fields on Account, Deal, and Contact respectively. Freshsales requires the destination custom field to be created with the exact same name and field type before import. We export the Pipeline CRM field schema during discovery, create identically-named fields in Freshsales Admin settings before migration, then load data. Text, dropdown, date, number, and checkbox types map directly; multi-select picklists require comma-separated format in the CSV.

Pipeline CRM Owners referenced on Deals and People are resolved by email match against Freshsales Users. Owner ID in Pipeline CRM does not correspond to any Freshsales identifier, so we use email as the cross-platform dedupe key. Owners without a matching Freshsales User go to a reconciliation queue; the admin must provision the User in Freshsales before record import resumes. Inactive Pipeline CRM owners map to inactive Freshsales Users at the customer's direction.