Migrate from Pega Sales Automation to Freshsales

Pega Accounts (economic decision-making units in the B2B model) map directly to Freshsales Accounts. The Pega Account Name, Industry, Website, and Address fields map to Freshsales Account Name, Industry, Website, and City/State/Country fields. We import Accounts first because they are the top-level parent with no foreign-key dependencies, matching Pega's import sequence requirement and resolving the AccountId reference needed by all downstream entities in Freshsales.

Pega Contacts map to Freshsales Contacts with AccountId resolved from the Account mapping. First Name, Last Name, Email, Phone, Job Title, and Address fields map directly. The Contact-to-Account foreign key is satisfied at migration time by matching the Pega Contact's Account reference to the imported Freshsales Account ID. Pega's operator records (individual users) can be mapped to Freshsales Users by email match, but Pega access groups and reporting hierarchies do not have Freshsales equivalents and require manual configuration post-migration.

Pega Leads (unconverted prospects) map to Freshsales Leads. Pega disposition codes and lead source fields migrate as custom fields in Freshsales. If the customer's Pega instance uses Leads as the primary prospect object, we preserve the lead score as a custom numeric field on the Freshsales Lead. Pega lead status values map to Freshsales Lead Status picklist values that we configure during schema setup.

Pega Opportunities map to Freshsales Deals. Stage progression, amount, close date, and probability migrate as Deal Stage, Amount, Close Date, and Probability fields. The Pega Opportunity-to-Account and Opportunity-to-Contact lookups resolve to Freshsales Deal-to-Account and Deal-to-Contact associations at migration time. Closed-won and closed-lost reasons from Pega custom fields migrate as custom text fields on the Freshsales Deal.

Pega Activities (calls, emails, tasks, meetings) tied to parent entities migrate to Freshsales Tasks and Events. We flatten the activity type hierarchy: calls and tasks map to Freshsales Task with a custom activity_type field; meetings map to Freshsales Event with start_time, end_time, and location preserved. Each activity record is linked to the parent Contact, Account, or Deal via Freshsales' targetable_id and targetable_type fields. Pega SLA timers do not migrate because Freshsales has no SLA entity. Activities load after parent records to satisfy referential integrity.

Pega Products map to Freshsales Products with SKU, Name, and Unit Price preserved. The Opportunity-Product junction (quantity, unit price, discount) migrates as Freshsales Line Items attached to the corresponding Deal. Pricebook support is available on Estate and Forest plans; we configure the default pricebook during migration setup if the customer is on those tiers.

Pega Territories segment Accounts and users by geography or business unit through territory assignment rules that trigger on record creation. Freshsales has no native Territory object. We map territory assignments to a custom multi-select picklist or text field on Account and Contact, preserving the original Pega territory name for reporting purposes.

Pega Sales Teams define access to Account or Opportunity records through a separate assignment entity. Freshsales uses a simpler model where Deals can have a primary owner and additional Users can be added via the Deal Team feature (Estate and Forest only). We map the primary Pega Sales Team member to Freshsales Deal Owner and document any additional team members in a custom text field for the customer's admin to reconfigure post-migration if needed.

Pega custom properties on any base entity require manual enumeration via the Pega API or Ruleset review, as there is no bulk discovery endpoint. We enumerate custom fields entity by entity and map each to a Freshsales custom field of the equivalent type (text, number, date, picklist). Pega data types (Text, Integer, DateTime, Boolean) are matched to Freshsales field types individually. Drop-down values in Pega must exactly match the values we set in Freshsales or the import is rejected — we validate picklist values before loading.

Pega Campaigns group Leads and Activities for coordinated outreach. Freshsales does not have a native Campaign object in the same sense. We map campaign membership to a custom field on the associated Lead or Contact and provide a written mapping of campaign names to the corresponding segmented contacts for the customer to recreate in Freshsales Reports or a dedicated campaign tool.