Migrate from Clientjoy to HighLevel

Clientjoy Leads map to GoHighLevel Contacts. The HubSpot pipeline stage assignment in Clientjoy becomes a GoHighLevel Contact tag and optionally a custom field (e.g., pipeline_stage__c). We preserve the Lead's email address, phone, source, and any custom field values. If the Lead has been converted to a Customer in Clientjoy, we migrate the Customer record instead and flag the original Lead as a duplicate.

Clientjoy Customer records map to GoHighLevel Contacts. Customer contact details, company info, lifecycle status, and tags transfer directly. GoHighLevel does not have a separate Company object at the Contact level without enabling the Account module; we discuss with the customer whether to create a Company field on Contact or enable Accounts during scoping. Multi-currency data from Agency plan Customers transfers to GoHighLevel custom fields.

Clientjoy pipeline definitions and stage names export via the API. Each Clientjoy pipeline becomes a GoHighLevel Pipeline with stage names mapped to GoHighLevel stage values. Custom pipeline configurations (stage probabilities, automation triggers per stage) require manual recreation in GoHighLevel's pipeline settings after migration. Stage ordering is preserved in the migration metadata file.

Clientjoy Deals map to GoHighLevel Opportunities. The deal amount, stage, associated contact, owner, and close date transfer directly. We map Clientjoy's deal stage to GoHighLevel pipeline stages using the pipeline mapping file generated during scoping. Deal custom fields migrate as GoHighLevel custom fields pre-created before import.

One-time Clientjoy invoices migrate as GoHighLevel Invoice records with line items, amounts, tax rates, currency, and payment status preserved. Invoice PDFs are exported as files and attached to the corresponding GoHighLevel Invoice record. Note that GoHighLevel's invoice module is separate from its CRM and requires the Payments add-on to process transactions; we confirm whether the customer enables this during scoping.

Clientjoy recurring invoice schedules (frequency, interval, start date, end date) migrate as metadata attached to the related Contact or Opportunity. GoHighLevel does not have native recurring invoice automation outside of the Payments module, so the schedule parameters are stored as custom fields (e.g., recurring_frequency__c, recurring_next_date__c) for the customer to configure in GoHighLevel's automation builder post-migration.

Clientjoy custom field definitions export from Agency plan and above. We create matching custom fields in GoHighLevel before importing data. Field types (text, dropdown, date, number, checkbox) are mapped to GoHighLevel field types. Note that Starter plan users cannot create custom fields in Clientjoy, so any custom field data on Starter accounts was never saved and cannot migrate.

Clientjoy document templates use merge fields tied to Lead, Customer, and Invoice objects. We extract template definitions and field associations as a structured JSON export. The template formatting and e-sign audit trails do not have a direct GoHighLevel equivalent. Templates are delivered as a reconstruction guide with merge field mappings so the customer can rebuild them in GoHighLevel's form and document builder. Signed PDFs are exported as files for the customer to store externally.