Migrate from Clientjoy to HubSpot

Clientjoy leads that have not reached a converted status become HubSpot Contacts with no lifecycle stage set. HubSpot stores them as Contacts (or optionally as HubSpot Leads) and sets lifecycle_stage to null or Subscriber. Their original createdate migrates as a custom reference field since HubSpot's CreatedDate is stamped at migration time.

Clientjoy leads that are paying customers map to HubSpot Contacts with lifecycle_stage set to 'Customer'. FlitStack inspects the Clientjoy lead's status, invoice history, or a 'converted' flag to determine which routing applies. Original create date, last modified date, and owner are all preserved on the HubSpot Contact record.

Clientjoy companies map to HubSpot Companies. If Clientjoy stores a company on a lead record without a separate Companies object, FlitStack creates a HubSpot Company from that embedded data. Clientjoy does not support parent-child hierarchies, so all companies land as standalone records in HubSpot regardless of any implicit relationships in the source data.

Clientjoy deal pipeline and stage are stored as two separate fields on the deal. These map to HubSpot's Deal pipeline and dealstage fields directly. If the Clientjoy pipeline name does not exist in HubSpot yet, we create it during the migration plan phase so stage values land in the correct pipeline on first import.

Each Clientjoy pipeline-stage name maps to a HubSpot Deal stage value. The mapping is value-by-value: Prospect maps to Prospect, Qualification to Qualified, Closed Won to Closed Won, and so on. If a Clientjoy stage has no HubSpot equivalent, we create a matching stage in the target pipeline before migration runs.

HubSpot has no native invoice object, so Clientjoy invoices migrate as a custom object. We create a Clientjoy_Invoices__c object with fields for invoice number, date, amount, status, client name (as a contact lookup), and line items as a text area or custom product lookup. Payment transaction history and tax calculations are stored as custom fields or noted for manual re-entry because Clientjoy's invoice model does not map 1:1 to any HubSpot construct.

Clientjoy document attachments and uploaded files are downloaded from Clientjoy's storage and re-uploaded to HubSpot Files. Each file is associated with the relevant Contact, Company, or Deal record in HubSpot using the file-to-record linking. File metadata (original filename, upload date, uploader) is preserved in HubSpot's file properties.

Clientjoy custom fields on leads become HubSpot Contact custom properties. Users (or our team) create the custom properties in HubSpot before migration using the same label and field type, and FlitStack then populates them during the import. Multi-select pick-list fields in Clientjoy map to HubSpot checkbox or multi-checkbox properties, which users verify post-migration.

Clientjoy email sequences store automation logic including step order, delay timing, and email body templates. This data does not exist in HubSpot as a migratable object. We export a structured JSON reference of your sequence definitions (step order, delays, templates, subject lines) that your HubSpot admin uses to rebuild the sequences inside HubSpot Sequences.

Clientjoy workflow definitions (triggers, conditions, and actions) cannot transfer to HubSpot because HubSpot Workflows operate on a different event model. FlitStack exports the Clientjoy workflow definitions as a rebuild reference document, and our team can connect your HubSpot admin to the HubSpot Workflow builder to recreate each automation.

Clientjoy email templates (subject lines, body copy, merge fields) are exported as HTML text files. HubSpot Marketing Email templates require recreation inside HubSpot's template editor. We deliver the exported HTML and a merge-field mapping table so your team can paste content into HubSpot templates without losing formatting.

Clientjoy owner assignments on leads, customers, and deals resolve to HubSpot users by email match. If a Clientjoy owner email does not find a matching HubSpot user, the record is flagged before migration. You can invite the user to HubSpot first or assign their records to a fallback HubSpot owner before the full run starts.