Migrate from Clientjoy to Freshsales

Clientjoy Leads map directly to Freshsales Leads. All standard fields (name, email, phone, company, source) migrate as typed fields. Pipeline stage from Clientjoy becomes a custom text field or maps to a Freshsales Lead Status value depending on the stage naming convention used. Any custom fields defined on Clientjoy Leads (available only if sourced from an Agency plan account) are mapped to Freshsales custom fields on the Lead object. We flag any Leads that have already been converted to Customers in Clientjoy for routing through the Freshsales Contact conversion workflow rather than landing as raw Leads.

Clientjoy's Customer object holds both person and company data. We split this into Freshsales Contact (the person) and Account (the company) using the Customer's company association as the Account name. When Clientjoy stores a Customer without a linked company, we create a Contact-only record in Freshsales without an Account parent. We preserve any tags or lifecycle stage values from Clientjoy as custom fields on the Freshsales Contact for reporting continuity.

Clientjoy pipeline definitions and stage names export via API and map to Freshsales Deal pipeline stages. Stage ordering and probability values migrate as Freshsales Deal stage definitions. Custom pipeline configurations may require manual review post-import if stage names in Clientjoy use non-standard terminology that maps ambiguously to Freshsales default stage values. We create the stage mapping table during scoping and validate in a sandbox migration before production.

Clientjoy invoices do not have a direct Freshsales object equivalent. We transform invoice headers, line items, tax rates, and payment status into Freshsales Deals with Product line items and a custom invoice status field. Recurring invoice schedules migrate as metadata (frequency, interval, start date) attached to the Deal record. Currency information from multi-currency Clientjoy invoices maps to Freshsales Deal currency fields. The customer should confirm whether Freshsales's built-in invoicing (Freshsales CRM Docs) or a third-party integration (Freshbooks, QuickBooks) is the intended invoice workflow post-migration.

Clientjoy document templates use merge fields tied to Lead, Customer, and Invoice objects. We extract template content and field associations as a written mapping document. The raw document content migrates as a ContentDocument attached to the relevant Deal or Contact record. Note that e-sign audit trails and cryptographic signing metadata are Clientjoy-specific and do not have a Freshsales equivalent; signed PDFs migrate as static attachments. The customer should confirm which documents require re-signing in Freshsales's DocuSign or PandaDoc integration.

Clientjoy custom field definitions are only available on the Agency plan and above. We export field definitions (label, type, options for picklists) alongside data values and map them to Freshsales custom fields on the equivalent object. Field types (text, dropdown, date, number) map to Freshsales field types with the same constraints. Custom fields on Starter plan accounts did not exist in Clientjoy, so no mapping is generated for those accounts. We confirm plan tier during scoping and flag the custom field availability gap upfront.

Clientjoy email sequences are automation objects tied to trigger conditions and pipeline stage rules. We export sequence steps, timing rules, and trigger criteria as a written inventory document. Freshsales Workflows use a different trigger and action model; sequences require either Freshsales's own Sales Engage module or a third-party sales engagement tool. We deliver a detailed sequence map with trigger conditions, step timing, and recommended Freshsales Workflow or Sales Engage cadence equivalents for the customer's admin to implement post-migration.

Clientjoy client portal configurations including white-label settings, custom domain, CSS styling, and embedded widgets export as configuration data. Portal content and uploaded files require separate file migration. Freshsales does not include a native client portal; customers typically use Freshdesk's customer portal, a Freshworks Experience Cloud equivalent, or a third-party client portal. We document the existing portal structure and configuration so that it can be mapped to the replacement portal solution.

Clientjoy appointment records migrate with date, time, invitee details, and status. Booking page configurations export as scheduling rule metadata. Freshsales has a built-in Calendar module for activity scheduling. We map appointment data to Freshsales Event records with appropriate date and time fields, and flag booking page configurations as requiring recreation in Freshsales Calendar or a Freshcaller integration if the appointment use case involves inbound call scheduling.