Migrate from Clientjoy to Salesforce Sales Cloud

Clientjoy Leads map directly to Salesforce Lead. The HubSpot-style pipeline stage in Clientjoy maps to Salesforce Lead Status with a custom field cj_original_stage__c preserving the source stage name. Any HubSpot Owner email is matched to Salesforce User by email during import. We extract all standard lead fields plus any custom fields defined on the Leads tab (custom field availability depends on the source plan tier being Agency or above).

Clientjoy's Customer object conflates person and organization into one record. We split this into Salesforce Account (the company or organization name) and Contact (the individual person). For solo freelancers without a separate organization name, we create a Contact with the Account Name set to the individual's name and the Account record flagged as a Sole Proprietor or Person Account (if the org supports Person Accounts). The original Clientjoy Customer ID is preserved in a custom field cj_customer_id__c for reconciliation.

Each Clientjoy pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Clientjoy pipeline configuration to Salesforce StageProbability. Stage ordering is preserved per pipeline.

Clientjoy Deals map to Salesforce Opportunity. The Clientjoy deal stage maps to Salesforce StageName via the Sales Process configured for the associated pipeline. Deal amount, close date, and pipeline assignment transfer directly. If Clientjoy stores a Closed-Lost or Closed-Won reason, we map it to a custom Opportunity field for reporting.

Clientjoy invoices (both one-time and recurring) require a mapping decision during scoping. For organizations that track invoice history as billing records, we create a custom Invoice object in Salesforce with line items, tax rates, payment status, and currency. For organizations that track revenue through Opportunities, we map invoice schedules as metadata on the associated Opportunity. The customer chooses the strategy based on whether they need long-term invoice audit trails or primarily use Salesforce for pipeline and forecast management.

Clientjoy document templates use merge fields tied to Lead, Customer, and Invoice objects. We extract templates and their field associations as a JSON mapping file. The template content itself migrates as raw document files. Salesforce does not natively replicate Clientjoy's template engine; we recommend Salesforce Agreements (native e-sign) or a DocuSign app from AppExchange as the replacement. The customer reviews template outputs post-migration because document builder formatting may not survive translation intact.

Custom fields on Clientjoy Leads and Customers (available on Agency plan and above only) map to Salesforce custom fields with type-appropriate Salesforce field types (text, picklist, date, checkbox, etc.). We pre-create all destination custom fields via Salesforce metadata API before any data import. Starter-plan accounts with no custom field definitions are documented with zero fields to migrate, preventing scope confusion during delivery.

Clientjoy Email Sequences store automation steps tied to trigger conditions. We export sequence definitions (step order, delay rules, email template references) as a JSON document for the customer's admin to rebuild in Salesforce Flow, High Velocity Sales, or a sales engagement tool (Outreach, Salesloft, or Sales Engagement). We do not migrate sequences as executable code.

Clientjoy Portal configurations including white-label settings, custom domain, CSS styling, and embedded widgets are exported as configuration data. Portal content and uploaded files migrate separately. The replacement in Salesforce is Experience Cloud (Community Cloud), which requires separate licensing and rebuild. We deliver a written portal feature map documenting which Clientjoy portal features need rebuilding in Experience Cloud.

Clientjoy appointment records migrate with date, time, invitee, and status preserved as Salesforce Event records. StartDateTime, EndDateTime, Location, and description transfer directly. Booking page configurations are exportable but require recreation in Salesforce's native scheduler or a third-party calendar integration (Calendly, HubSpot Meetings, etc.).

Clientjoy web form definitions and field mappings are exported. Form-to-Lead field associations are preserved in our mapping table so leads submitted post-migration route correctly into Salesforce. Salesforce's native Web-to-Lead serves as the baseline replacement; more complex forms require a rebuild in Salesforce's form builder or a third-party tool. We do not migrate form appearance or styling.

Clientjoy tags stored as properties on Leads, Customers, or Deals migrate to Salesforce multi-select picklist fields. Tags used for content classification migrate to Salesforce Topics with TopicAssignment records. The customer chooses tag strategy during scoping to avoid creating too many picklist values (Salesforce has a 500-value limit per picklist).