Migrate from Populate to Freshsales

Populate Person records migrate as Freshsales Contacts for qualified records. Freshsales Contact records require an AccountId lookup — if the linked Organization does not yet exist in Freshsales as an Account, contacts land with a placeholder assignment pending Account creation. Original create date and last-modified date preserved as custom datetime fields on the Contact record.

Populate Person records with status='Lead' or unconverted status route to Freshsales Lead objects. The split is based on a status field value in Populate — the migration mapping defines which Populate status values map to Lead versus Contact in Freshsales. Lead-to-Contact conversion in Freshsales creates both Account and Opportunity records when triggered by your admin post-migration.

Populate Organization records map directly to Freshsales Account records. Account name, domain, industry, employee count, and annual revenue fields migrate as direct field mappings. Parent-child Organization hierarchies in Populate map to Freshsales Parent Account lookups — the parent must migrate before the child so the ParentId foreign key resolves correctly.

Populate Deal records migrate as Freshsales Opportunities. Each Opportunity requires a pipeline assignment and stage value — the migration maps Populate deal stage names to Freshsales pipeline stage pick-list values on a per-pipeline basis. Amount, close date, deal name, and owner fields migrate as direct mappings with owner resolved by email match to Freshsales user accounts.

Populate pipelines carry stage names that map directly to Freshsales pipeline stage sets. Freshsales supports multiple pipelines, each with its own set of stage values. The migration creates Freshsales pipelines matching the Populate pipeline count and maps each Populate stage label to the corresponding Freshsales stage name within that pipeline.

Populate call activities migrate as Freshsales Tasks with Type='Call'. Original call duration, subject, and owner preserved. The task is linked to the parent Contact or Lead record via the WhoId field in Freshsales. Timestamps for call start and completion migrate as custom datetime fields if available from Populate's API response.

Populate email activities migrate as Freshsales Tasks with Type='Email'. Email subject, body content (plain text), and sent timestamp preserved. The task links to the Contact or Lead via WhoId. Rich-text email formatting is simplified to plain text since Freshsales Tasks do not support HTML email bodies natively.

Populate meeting records migrate as Freshsales Events with original start time, end time, location, and title preserved. Events link to the Contact or Lead via the WhoId field and to the Account via the WhatId field if the meeting is associated with a deal or account in Populate.

Populate notes migrate as Freshsales Notes objects. Note title, body content, and association to the parent record (Contact, Lead, Account, or Opportunity) preserved. Freshsales Notes use a separate Notes object from the legacy Note type — the migration targets the standard Notes object for modern compatibility.

Populate custom fields on Person records require Freshsales custom fields to be created first via Admin Settings > Contacts/Leads > Custom Fields. Text, number, pick-list, date, and checkbox field types map to Freshsales equivalents. Pick-list custom fields in Populate require Freshsales pick-list value mapping if the values differ between platforms.

Populate custom fields on Deal records migrate to Freshsales Opportunity custom fields. These must be pre-created in Freshsales Admin Settings > Deals > Custom Fields before the migration run. Numeric and currency custom fields map directly; pick-list values require value-by-value mapping if the source values differ from Freshsales pick-list definitions.

Populate product records map to Freshsales Products. If Populate tracks line items on deals, those migrate as Freshsales Opportunity Line Items attached to the corresponding Opportunity. Product pricing information migrates as custom fields on the Product object if Freshsales native price list fields do not cover the source data structure.

Populate owner_id on records resolves to Freshsales users via email address matching. The migration flags any Populate owner whose email does not match an existing Freshsales user — your team either invites them to Freshsales first or assigns their records to a fallback owner before the migration commits. Unresolved owners do not block migration but result in unassigned records in Freshsales.