Migrate from Clientjoy to Nutshell

Clientjoy Leads map directly to Nutshell Leads. The Lead's name, email, phone, source, status, and assigned pipeline stage migrate as standard Nutshell Lead fields. Any custom fields defined on the Lead object in Clientjoy (gated to Agency plan on source) map to Nutshell Lead custom fields, which we pre-create using the same field label and type (text, date, currency, dropdown). Clientjoy pipeline stage assignments become Nutshell Lead status values. Owner assignment migrates by email match against Nutshell Users.

Clientjoy Customers represent the converted state of a prospect. We split Clientjoy Customers into two migration targets: the person-level data (contact name, email, phone, address) maps to Nutshell Person, and any company-level data (company name, industry, size) maps to Nutshell Company. If Clientjoy stored a company name on the Customer record but no separate Company record existed, we create a Nutshell Company first, then link the Person to it via the accountId reference. Tags on the Clientjoy Customer migrate as plain-text tags on the Nutshell Person.

Clientjoy pipeline definitions and custom stage names are exported via API (Agency plan) or extracted from CSV exports. Each Clientjoy pipeline becomes a Nutshell Pipeline with stages mapped to Nutshell stage names. Nutshell Foundation and Growth support one pipeline; Nutshell Pro supports up to 5 pipelines; Nutshell Business and Enterprise support unlimited. We configure pipelines before data import and map Clientjoy stage probability percentages to Nutshell stage probabilities.

Clientjoy Invoices (one-time and recurring) have no direct Nutshell equivalent, as Nutshell does not include a native invoice object. We export invoice headers, line items, tax rates, payment status, currency, and recurring schedule as a structured JSON metadata record. This metadata is attached as a Note on the related Nutshell Person or Company record. The customer should plan to use a third-party billing integration (QuickBooks, Wave, Zoho Invoice) post-migration for invoice generation, or evaluate Nutshell's Quoting tool on Sales Growth and above as a proposal-to-quote replacement.

Document templates use merge fields tied to Lead, Customer, and Invoice objects in Clientjoy. We extract the raw document content as HTML or plain text and the template field associations as a JSON mapping table. Formatted document content migrates as Nutshell Files attached to the related Person or Company. We do not preserve Clientjoy's document builder layout or e-sign audit trails, which are platform-specific. Signed PDFs should be downloaded from Clientjoy before migration cutover if legal documentation retention is required.

Custom fields on Clientjoy Leads and Customers (available on Agency plan and above) map to Nutshell custom fields on Lead, Person, and Company respectively. We pre-create the destination custom fields in Nutshell before data import, matching field types (text, long text, currency, date, dropdown). Starter plan users on Clientjoy who created no custom fields have no source custom field definitions to migrate. Any custom field values present on a Starter plan account should be treated as plain fields migrated under the standard field mapping.

Clientjoy Email Sequences are automation objects tied to specific trigger conditions and cadence steps. We export sequence name, step count, timing rules, and trigger configuration as a JSON inventory document. We do not migrate sequences as functional code into Nutshell because Nutshell's Sales Pro and above support personal email sequences with a different data model. The inventory document serves as the handoff artifact for the customer's admin to configure equivalent sequences in Nutshell or a dedicated sales engagement tool post-migration.

Clientjoy Client Portal configurations including white-label settings, custom domain, CSS styling, and portal widget embeddings are exportable as configuration data. Portal content and uploaded files are exported separately. Nutshell does not include a client portal feature, so portal configuration migrates as a written inventory noting each setting, URL, and CSS block for manual reconfiguration in a third-party portal tool (Client Portal, HubSpot CMS, or a custom build) post-migration.