Migrate from Jubilee to HighLevel

Jubilee Clients map directly to HighLevel Contacts. The client's name, email, phone, address, and any custom client-level properties migrate as Contact fields. A Company record is also created from the client's company name if present. This dual mapping ensures that both individual contact details and organizational context are transferred, maintaining relationships across the CRM.

When a Jubilee client record contains an organization name, FlitStack AI creates a corresponding HighLevel Company record and links the Contact to it via the primary CompanyId lookup. Secondary organizations are added as Company associations on the contact. This transformation preserves the hierarchical relationship between the contact and its organization, enabling accurate reporting by company in HighLevel.

Jubilee Matters map to HighLevel Opportunities. The Matter name becomes the Opportunity name, the estimated value maps to Amount, and the matter status maps to an Opportunity Stage. A custom matter-type field preserves the original case classification. This mapping also retains the original create date in a custom field to support historical reporting and timeline analysis.

Jubilee matter statuses (e.g., Filed, Pending Trustee, Discharged) are mapped value-by-value to HighLevel pipeline stages. Each stage in HighLevel requires a corresponding Pipeline to be set up before the mapping applies. The mapping includes probability percentages for each stage, allowing deal forecasting to reflect typical case progression timelines.

Jubilee custom matter properties (e.g., Chapter type, Filing date, Case number, Trustee name) do not have native equivalents in HighLevel. Each custom property requires a corresponding custom field to be created in HighLevel before migration. FlitStack delivers a custom-field creation plan as part of the pre-migration schema setup.

Jubilee documents attached to Matters are re-uploaded to HighLevel as Files linked to the corresponding Opportunity record. The original file name, content type, and uploaded date are preserved. Filing metadata (e.g., document category) is stored in a custom text field on the file or opportunity.

Jubilee calendar events tied to Matter records map to HighLevel Calendar Events with the original start/end time, invitees, and location preserved. Events are linked to the migrated Contact or Opportunity. Recurring events maintain their recurrence pattern, and any attachments such as agenda files are also linked to the event record.

Matter-linked tasks in Jubilee migrate as HighLevel Tasks with original due dates, assignees resolved by email match to HighLevel users, and status preserved as a custom pick-list if it does not map to a standard HighLevel task status. Tasks that include subtasks are also transferred, with the parent-child hierarchy reflected in HighLevel's task grouping.

Notes created on Jubilee Matters or Clients migrate as HighLevel Notes attached to the corresponding Contact or Opportunity. Original create date is preserved in a custom datetime field since HighLevel's CreatedDate reflects the migration timestamp. Rich text formatting, if present, is retained where possible, ensuring that detailed notes maintain their readability after migration.

Jubilee tags applied to Clients or Matters migrate as HighLevel Tags on the corresponding Contact or Opportunity record. Tags are preserved as-is with no value transformation. If tags include hierarchical categories, they can be represented using tag prefixes or custom fields to preserve the original grouping logic.

Jubilee user accounts (attorneys, paralegals, admins) are matched to HighLevel users by email address. Unmatched users are flagged before migration. Each user must have a HighLevel account provisioned with an appropriate role (Admin, Manager, or Agent) before the migration runs.

Jubilee intake workflows and matter-status automations have no equivalent in HighLevel's Workflow Builder. These must be rebuilt manually in HighLevel after migration. FlitStack exports the workflow definitions as a reference document for the rebuild process. The exported file includes trigger conditions, action steps, and any conditional logic, providing a clear blueprint for rebuilding the workflows in HighLevel's visual editor.

Jubilee billing and invoice records are financial records with no direct equivalent in HighLevel's CRM model. If billing history must be preserved, it can be stored as a custom object in HighLevel or exported as a reference CSV. HighLevel's built-in payments feature can replace billing workflows post-migration.