Migrate from BlueCamroo to HighLevel

BlueCamroo Organizations are the parent 'shoebox' records that anchor all sub-records. We export Organizations first in every migration and preserve the generated BlueCamroo Account ID as a reference key. In GoHighLevel, we create Contact records with the company name populated in the business name field and store the BlueCamroo Organization ID in a custom field for reconciliation. If the customer uses GoHighLevel Locations (for multi-branch setups), we create one Location per BlueCamroo Organization and link Contacts to it.

BlueCamroo People records live as sub-records under Organizations. We export People second, after Organizations, and apply the BlueCamroo Organization ID lookup to resolve each Contact to its parent Account in GoHighLevel. Standard fields (name, email, phone, address) map directly. Any People records without a pre-existing Organization are held in a reconciliation queue during export scoping — BlueCamroo allows standalone People records that GoHighLevel cannot accept without a parent reference.

BlueCamroo Opportunities map to GoHighLevel Opportunities with BlueCamroo pipeline stages mapped to GoHighLevel pipeline stage values. The Opportunity amount, probability, and close date transfer directly. We resolve the Opportunity's Organization (Account) reference before import so that the GoHighLevel Opportunity is linked to the correct Contact's company. BlueCamroo deal custom fields map to GoHighLevel Opportunity custom fields created during schema design.

BlueCamroo Cases (support tickets) map to GoHighLevel Cases. BlueCamroo Case status values (Open, In Progress, Closed, Re-Opened) map to GoHighLevel Case status values, and the priority field transfers directly. The Organization reference resolves to the Case's contact or company in GoHighLevel. Email-to-ticket routing — which is a Workflow Rule in BlueCamroo — is flagged separately and must be rebuilt as a GoHighLevel Workflow trigger (inbound email creates Case) documented in the rebuild guide.

BlueCamroo Projects are work records with stages, tasks, time entries, and budget tracking. GoHighLevel has no native project object, so we split BlueCamroo Projects into an Opportunity record (carrying the project name, budget, and stage as custom fields) plus individual Task records for each BlueCamroo task with the project-linked Opportunity as the WhatId. Billable hour totals and budget fields migrate as custom numeric fields on the Opportunity. BlueCamroo project templates export as structural metadata and are documented for manual recreation as Opportunity templates in GoHighLevel.

BlueCamroo Products and Services map to GoHighLevel Products. We export the product catalog first so that Price Book entries and Opportunity line items can reference the correct product IDs during import. Product pricing, SKUs, and descriptions transfer directly. GoHighLevel products support custom fields for additional product metadata.

BlueCamroo Price Books with per-account pricing tiers map to GoHighLevel Opportunity line items with custom pricing fields. We export Price Book entries with their linked Products and the account-specific discount or price override, then apply those values as custom fields on GoHighLevel Opportunity line items during the Opportunity import phase.

BlueCamroo standalone Tasks and project-subtask hierarchy map to GoHighLevel Tasks with the parent-Project (now Opportunity) linked via the WhatId. Due dates, priority, status, and assignees transfer directly. BlueCamroo subtask nesting does not map to GoHighLevel's flat task structure — we import subtasks as individual Tasks with a custom field referencing the parent Task ID for manual grouping post-import.

BlueCamroo Time Entries log hours against Projects with billable/unbillable flags. We export time entries and merge them into GoHighLevel Tasks linked to the same parent Opportunity. Billable hours, total duration, and time entry notes become custom fields on the Task. The time entry owner maps to the Task assignee via email matching.

BlueCamroo Invoices generated from project costs, stage percentages, or fixed dates include payment status and line-item details. We import open invoices as GoHighLevel Opportunities with invoice number, total amount, balance due, and payment status as custom fields. Closed or voided invoices migrate as historical records for reporting continuity. GoHighLevel does not have a native invoice object — if the customer requires invoice generation post-migration, we recommend connecting GoHighLevel to Stripe or QuickBooks via a native integration.

BlueCamroo renamed Extra Data Objects to Custom Forms in version 8.3.10 (2022). We query both API endpoints during discovery to capture all custom data containers regardless of naming. Each Custom Form's fields map to GoHighLevel custom fields on the relevant object (Contact, Opportunity, Case, or the linked Account/Location). If the custom form represents a distinct entity type with its own relationships, we create a GoHighLevel Custom Object with equivalent fields. We preserve the original BlueCamroo Extra Data Object name in a custom field for audit continuity.

BlueCamroo's per-module subscription assigns each user a role determining which extensions they access. We extract user role assignments and map them to GoHighLevel Teams or role-based access permissions. BlueCamroo roles do not have direct GoHighLevel equivalents, so we document the role mapping matrix (e.g., BlueCamroo Complete user maps to GoHighLevel Admin, BlueCamroo Sales-only maps to GoHighLevel Standard User) for the customer admin to apply post-migration.