Migrate from Perfect Portal to Freshsales

Perfect Portal clients map directly to Freshsales Contacts. The primary matter association becomes the AccountId lookup after the Account is created. Clients without an assigned matter default to a standalone Contact record in Freshsales. During the migration, each matter's client creates an Account record in Freshsales, and the Contact's AccountId field points to that Account. If a client is linked to multiple matters, first matter processed determines the Account linkage.

Referrers (agents, lenders, third parties) stored as separate client records in Perfect Portal map to Freshsales Contacts. A custom field Referral_Source__c identifies the referral relationship in Freshsales, since Freshsales has no native referrer object. This field stores the referrer type (Agent, Lender, Other) and can be used to filter deals by referral source. If referrers are linked to a matter, each appears as a separate Contact with same Referral_Source__c value.

Each Perfect Portal matter becomes a Freshsales Deal. The matter name becomes the Deal name; the matter type determines which Freshsales pipeline the deal is assigned to. Matter stage progression is stored as a custom field (Matter_Stage_History__c) since Freshsales does not natively track multi-stage history beyond deal stage.

Perfect Portal stage values (Inquiry, Engaged, Document Review, Settlement, Closed) map to Freshsales Deal Stage names per pipeline. Stage-entered timestamps are stored as a custom field (Stage_Entered_Date__c) on the deal record for audit continuity. Each pipeline has its own stage names; the mapping aligns Perfect Portal stage labels to the corresponding Freshsales stage. Stage_Entered_Date__c records the date and time the matter entered its current stage for reporting.

When Perfect Portal uses multiple matter types (e.g., Purchase, Refinance, Litigation), each type maps to a separate Freshsales Deal Pipeline. Freshsales Pro and Enterprise plans allow multiple pipelines; Growth plan has one pipeline by default. If you are on the Growth plan and require multiple pipelines, you must upgrade to Pro or Enterprise before migration, otherwise matter types are consolidated into a single pipeline using a custom field filter.

Referrers associated with a matter are stored as Contact records with a custom referrer-type field and linked to the deal via a custom deal field (Referrer_Contact_Id__c). This preserves the referral relationship without a native equivalent in Freshsales. The referrer-type field stores the role (Agent, Lender, Other) for segmentation, and the deal field holds the contact ID for referral reporting. Multiple referrers on a matter appear as separate Contacts with role.

Matter documents are downloaded and re-uploaded as Freshsales Files attached to the corresponding Deal, Contact, or Account record. File naming preserves the original matter document title for traceability. During upload, we keep the original file extension and set ownership to the Freshsales user who owned the matter, preserving attribution. If the file exceeds storage limits, we alert your admin to consider archiving or upgrading.

Communication logs and notes in Perfect Portal migrate as Freshsales Sales Activities (type: Note) or Notes objects. Original timestamps and author information are preserved on the activity record. Each activity is linked to the parent Deal, Contact, or Account based on matter context, so communication history appears in the relevant record. If the author email does not match a Freshsales user, the activity is assigned to a migration user.

Perfect Portal custom fields at the matter level are created as custom fields on the Freshsales Deal object. Field type is mapped (text, number, date, picklist) to the nearest Freshsales field type. Picklist custom fields require value-by-value mapping. Before migration, we verify each custom field's data type and create the Freshsales field, applying validation rules. During import, data is transformed to match the format, ensuring loss of information is avoided.

Perfect Portal user assignments resolve by email match against Freshsales users. Unmatched owners are flagged before migration — your team either invites them to Freshsales or assigns records to a fallback user. No record lands without a valid Freshsales owner.

Perfect Portal stage-update triggers and client notification workflows do not have an equivalent in Freshsales. These must be rebuilt in Freshsales Workflows after migration. FlitStack exports the workflow definitions as a reference document for your admin. During discovery, we capture trigger events, conditions, and actions for each workflow, so your Freshsales admin can rebuild them using Freshsales Workflow's trigger‑action model. This documentation includes sample configurations for common stage‑change notifications.

Perfect Portal grants referrers and clients portal access to view matter status. Freshsales has no native client/referrer portal equivalent. External sharing links or Freshsales customer portal setup (Freshsales Suite) must be configured post-migration. If you require real‑time visibility, consider enabling Freshsales Suite's customer portal, which provides a branded portal for clients and referrers to track deal status. Alternatively, you can generate secure sharing links per record for on‑demand access.