Migrate from Clientjoy to Microsoft Dynamics 365 Sales

Clientjoy Leads map directly to Microsoft Dynamics 365 Sales Lead. Standard lead fields (name, email, phone, company, source) migrate with source attribution preserved in a custom field cj_lead_source__c. Pipeline stage assignment from Clientjoy migrates to a custom picklist field cj_pipeline_stage__c on Lead for audit and reporting continuity.

Clientjoy Customers carry both individual contact data and company affiliation. We split these into Dynamics 365 Contact (individual) and Account (company/organization) records. If the Customer's company name field is populated, we create an Account first, then link the Contact to it. If no company is recorded, the Contact stands alone with no Account parent. Tags and lifecycle status from Clientjoy migrate to custom fields on Contact.

Clientjoy Pipeline definitions and stage names export via the API and map to Dynamics 365 Opportunity with a Sales Process and Record Type per pipeline. Stage names and ordering migrate to stage values in the Sales Process. Stage probability percentages map to StageProbability on each stage definition. Closed-Lost and Closed-Won statuses from Clientjoy align with Dynamics 365's standard close values.

Clientjoy invoices (one-time and recurring) map to the Invoice object if the destination Dynamics 365 org includes the Sales Invoice module. Line items, tax rates, currency, payment status, and recurring schedule metadata migrate as Invoice Detail rows. If the destination org does not include the Finance module, invoices migrate as a custom Invoice entity with a manual PDF attachment for each record. Currency and multi-currency configurations from Clientjoy map to Dynamics 365 Finance currency settings.

Clientjoy document templates use merge fields tied to Lead, Customer, and Invoice objects. We extract template definitions and their field associations as a written specification document, but template formatting and merge field bindings do not transfer automatically. The customer's admin rebuilds templates as Dynamics 365 Word templates or Power Automate document-generation flows post-migration. Signed PDF copies export as file attachments linked to the corresponding Contact or Account record.

Clientjoy Email Sequences store automation steps and timing rules tied to pipeline stage triggers. We export sequence step definitions, timing delays, and step content as a written inventory document. Sequences do not migrate as automation code because Microsoft Dynamics 365 Sales has no equivalent native cadence feature at the Sales Professional tier. The customer's admin rebuilds sequences using Sales Engagement tools (Sales Hub Enterprise or a third-party sales engagement platform) or Power Automate flows.

Clientjoy Client Portal configurations (white-label settings, custom domain, CSS styling, embedded widgets) export as a configuration specification document. Portal content and uploaded files migrate separately as file assets. The customer's admin rebuilds the client-facing experience using Dynamics 365 Customer Portal (built on Power Pages) or a SharePoint-based extranet with Dynamics 365 integration.

Custom fields created on Clientjoy Leads and Customers (gated to Agency plan) map to Dynamics 365 custom fields on Lead and Contact. Field type mapping: text to Single Line of Text, dropdown to Picklist, date to Date Only, checkbox to Two Options. Custom field API names from Clientjoy carry over as the basis for Dynamics 365 custom field names. Starter-plan users with no custom fields are confirmed during scoping and do not have a custom field export step.

Clientjoy appointment records migrate to Dynamics 365 Appointment with date, time, invitee, location, and status preserved. If the customer uses Outlook calendar integration post-migration, appointments sync bidirectionally via the Dynamics 365 Outlook add-in. Booking page configurations export as a written specification for recreation in Dynamics 365 Scheduler or a Power Automate booking flow.

Clientjoy web form definitions and field mappings export with form-to-Lead field associations preserved in our mapping table. Form submissions post-migration route to Dynamics 365 via a rebuilt Web-to-Lead form or Power Pages form, configured by the customer's admin using the field mapping inventory we deliver.