Migrate from Perfect Books to Freshsales

Direct map for standard contact fields. Perfect Books contacts without a company affiliation land directly as Freshsales Contacts. For contacts with inline Perfect Books company data, an Account record is created first and the Contact is linked via AccountId. This ensures every contact with embedded company information resolves to both a Contact and an Account in Freshsales, maintaining the relationship integrity of the original data.

Perfect Books contacts at the 'Prospect' or 'Unqualified' lifecycle stage route to Freshsales Leads. Contacts marked as 'Customer' or 'Active' route to Freshsales Contacts. The split is based on the Perfect Books contact status field value at migration time. This ensures unqualified prospects enter Freshsales as Leads for further nurturing, while established customers become Contacts with full account history.

Perfect Books stores company name, domain, industry, and employee count directly on the contact record. These extract into a Freshsales Account record linked to the Contact by AccountId. Deduplication logic groups contacts sharing the same company name into a single Account.

Perfect Books deals map to Freshsales Opportunities. The deal name becomes Opportunity Name, amount maps to Amount, close date maps to CloseDate, and owner resolves by email match to Freshsales users. Pipeline and stage values map via the value-mapping table defined per pipeline.

Perfect Books pipelines map 1:1 to Freshsales sales pipelines. Each pipeline retains its stage sequence and stage names. Stage order is preserved; stage probability values are mapped from Perfect Books' stage configuration. This one-to-one mapping ensures pipeline visibility and reporting continuity carry over without requiring pipeline reconstruction in Freshsales.

Perfect Books stage names map value-by-value to Freshsales stage names. Where Perfect Books uses a stage-entered timestamp, that date is stored in a custom datetime field (Stage_Entered_Date__c) on the Opportunity for reporting continuity. This preserves historical stage timing data that would otherwise be lost during migration.

Every Perfect Books custom property requires a corresponding Freshsales custom field to be created before migration. We deliver a pre-migration setup plan specifying field label, type (text, number, picklist, date, datetime), and any pick-list values to pre-populate. This ensures all custom data has a destination field ready before the migration run begins.

Perfect Books call logs map to Freshsales Tasks with Type='Call'; emails map to Tasks with Type='Email'; meetings map to Events with start and end times preserved; notes map to Freshsales Notes with original timestamps and parent-record links retained. All activity history maintains its chronological context in the destination system.

Perfect Books file attachments on contacts, companies, or deals are downloaded and re-uploaded to Freshsales as attachments linked to the corresponding record. File size limits per Freshsales apply; files exceeding the limit are flagged for manual handling. This preserves document context alongside related CRM records.

Perfect Books owner IDs are resolved by email match against Freshsales users. Unmatched owners are flagged before migration — the team either creates Freshsales user accounts for them or assigns their records to a fallback owner. No record lands without a valid Freshsales OwnerId.