Migrate from Clientjoy to Pipedrive

Clientjoy Leads map to Pipedrive People (Person object). Standard Lead fields including name, email, phone, company, address, and status migrate directly. Pipeline stage assignment from Clientjoy is preserved as a custom field or mapped to a Pipedrive Activity note. Any custom fields defined on the Lead object in Clientjoy (Agency plan and above) are recreated in Pipedrive via the Pipedrive API as Person custom fields before data import begins.

Clientjoy Customer records split into Pipedrive Person (contact details) and Organization (company information). The customer's company name maps to the Organization name field, and contact details map to the Person. This mirrors how Pipedrive structures person-company relationships natively and allows deal associations to attach to Organizations rather than People.

Clientjoy pipeline definitions and stage names export via the API. Each Clientjoy pipeline becomes a Pipedrive Pipeline with stages recreated using Pipedrive's stage API. Stage ordering and probability percentages are preserved from Clientjoy and mapped to Pipedrive's stage_probability field. Customers with multiple Clientjoy pipelines create multiple Pipedrive pipelines, which Pipedrive supports from the Essential tier onward.

Clientjoy Deals map to Pipedrive Deals. The Clientjoy deal stage maps to a Pipedrive Stage within the corresponding Pipeline. Deal title, value (in original currency), expected close date, owner, and associated Lead or Customer all migrate. Pipedrive's monetary value field accepts decimal values with currency metadata stored separately, so multi-currency deal values from Clientjoy migrate as raw values with a currency field annotation for the customer's admin to finalize in Pipedrive settings.

Pipedrive has no native invoice object. We export Clientjoy invoice headers (invoice number, date, due date, status), line items (description, quantity, unit price, tax rate), total amount, and currency as a structured text block or set of custom fields on the related Deal or Person record. Recurring invoice schedules are preserved as a custom field with the recurrence pattern. Customers who need full invoice functionality post-migration configure a billing integration (Stripe, QuickBooks, or Xero) connected to Pipedrive.

Clientjoy custom fields (gated to Agency plan and above) are exported with their field definitions: field type, label, and picklist options if applicable. We recreate each custom field in Pipedrive via the Pipedrive API using the corresponding Pipedrive field type (text, varchar, numeric, date, double, enum for picklists, boolean for checkboxes). Custom fields are deployed to the correct Pipedrive object (Person, Organization, or Deal) before data import. Starter plan users who never had access to custom fields have no custom field definitions to migrate.

Clientjoy Email Sequences are automation objects tied to trigger conditions and pipeline stages. Pipedrive's Campaigns feature provides a comparable cadence model but with different trigger mechanics. We export the sequence steps, timing rules, and trigger conditions as a written inventory that the customer's admin uses to configure Pipedrive Campaigns or a third-party sales engagement tool post-migration. Automated sends tied to Clientjoy pipeline stages are documented with their equivalent Pipedrive workflow trigger recommendations.

Clientjoy document templates use merge fields tied to Lead, Customer, and Invoice objects. We export template content and field associations as a structured document. Pipedrive does not host document templates natively; customers who need template-based documents post-migration integrate a third-party tool such as PandaDoc, DocuSign, or Quent. We provide a field-mapping reference linking Clientjoy merge field names to their Pipedrive custom field equivalents so the integration connects correctly.

Clientjoy Client Portal configurations including white-label settings, custom domain, CSS styling, and embedded widgets are exportable as configuration data. Pipedrive does not have a native client portal; customers requiring client-facing workspaces use a third-party portal tool (Clientjoy's successor, a custom Experience Cloud build, or a dedicated portal product). We deliver a configuration export of the portal settings and a written handoff noting which settings require manual recreation in the chosen replacement tool.

Clientjoy appointment records migrate to Pipedrive Activities with date, time, invitee, status (confirmed, cancelled, completed), and location preserved. Booking page configurations are exportable but require recreation in a calendar integration tool (Calendly, Cal.com, or Pipedrive's own Scheduler). We export appointment field data as a structured block and flag that the booking workflow needs a separate tools configuration.

Clientjoy Owners map to Pipedrive Users. We resolve owners by email match against the destination Pipedrive account's user list. Any Clientjoy Owner without a matching Pipedrive User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Clientjoy users are mapped to inactive Pipedrive users to preserve assignment history without licensing impact.

Clientjoy engagement records (emails, calls, meetings, notes) merge into Pipedrive Activity records. Emails map to Note activities with the email body as the content; calls map to Phone Call activities with duration and disposition; meetings map to Task activities with date and location; notes map to Note records linked to the Person or Deal. Activity timestamps are preserved to maintain the chronological timeline in Pipedrive's activity feed.