Migrate from Clientify to Freshsales

Clientify Contacts map directly to Freshsales Contacts. Standard fields (name, email, phone, company association, lifecycle stage) migrate as-is. Custom properties on contacts require pre-creation in Freshsales Admin Settings with matching field types before import; picklist values must be whitelisted or import fails for those fields. We preserve any Clientify lead score value in a custom numeric field for reference.

Clientify Companies map to Freshsales Accounts using the company domain as a dedupe key. Industry, size, address, and ownership fields migrate directly. Freshsales uses Account as the parent of Contact; we ensure Account records are created before Contact import so that the relationship is satisfied at insert time.

Clientify Deals map to Freshsales Deals with deal name, value, stage, owner, and expected close date preserved. The pipeline stage labels migrate and are replicated in Freshsales' pipeline configuration. We resolve the owner reference by matching Clientify owner email to Freshsales User email at migration time.

Each Clientify pipeline becomes a Freshsales pipeline with its stage sequence preserved. Stage probability percentages migrate where available. Stage-level automation triggers (if any) are documented in the automation inventory and must be rebuilt manually in Freshsales' workflow builder.

Clientify Leads (distinct from Contacts) map to Freshsales Leads. Source, status, and score fields transfer to Freshsales Lead fields including any custom lead score fields. If the customer uses Lead-to-Contact conversion logic in Clientify, we document the conversion criteria for manual setup in Freshsales Admin Settings under Leads module field mapping.

Clientify logged calls migrate as Task with TaskSubtype=Call. Emails migrate as Task records with body content. Meetings migrate as Event records with start/end time and location. Tasks migrate as Task records. Activity timestamps preserve the original Clientify date so that the Freshsales timeline reflects the correct sequence. Some timestamp formats and activity type labels require normalization during migration.

Clientify custom fields on contacts, companies, and deals map to Freshsales custom fields of matching type. We map text, number, date, and picklist field types directly. Picklist values in the destination must be pre-created in Freshsales or import rejects those records. Required field flags must be set before migration begins. We coordinate with the customer during scoping to ensure the Freshsales schema is prepared.

Clientify campaign records including open rates, click rates, and send volumes migrate to Freshsales Campaign records with performance data in custom fields. The automation logic governing send times, A/B tests, and trigger conditions lives in Clientify's campaign builder and cannot be extracted. We migrate campaign performance history as a data set; campaign execution logic is documented for manual rebuild in Freshsales' marketing module or a dedicated marketing automation tool.

Clientify email templates with dynamic field placeholders export as template body text and structure. Merge field names may differ between platforms and require remapping in Freshsales' template editor. We export the template body and flag any dynamic fields that need updating to Freshsales syntax.

Clientify tags on contacts and companies migrate as Freshsales Tags. Segment definitions based on dynamic filters must be reviewed and manually rebuilt in Freshsales using Freshsales' filter and segment logic, which differs from Clientify's segmentation model.