Migrate from Kinabase to HighLevel

Each Kinabase Collection is a distinct entity type with its own field schema. We map every Collection to the most semantically appropriate GoHighLevel object: a 'Clients' Collection maps to Contact and Company; a 'Projects' Collection maps to Custom CRM Object or Opportunity; a standalone 'Tasks' Collection maps to Task. Collections with no clear CRM analog become GoHighLevel Custom CRM Objects (available on Unlimited plan or CRM Pro add-on). The mapping is designed during discovery and validated against GoHighLevel's sub-account structure.

Individual Records within a Kinabase Collection map 1:1 to the equivalent GoHighLevel record. All field values — text, number, date, dropdown, and boolean — transfer directly. Multi-select dropdowns map to GoHighLevel multi-select custom fields. We preserve the Kinabase record ID as a text custom field for audit traceability.

Kinabase linked-collection fields (e.g., a 'Client' field in a 'Projects' Collection pointing to a 'Clients' Collection record) create cross-collection references. We export linked records in dependency order — parent records first — and resolve the destination ID at load time. Where GoHighLevel Custom CRM Objects support lookup fields, we create the lookup relationship. For Collections mapped to standard GoHighLevel objects that lack the lookup target, we write the referenced record ID as a text field and flag it for manual relationship confirmation post-migration.

Kinabase Computed Fields are evaluated dynamically by a formula at display time — the formula definition is not stored data. We evaluate each formula at migration time and write the resulting value as a static custom field in GoHighLevel. The formula logic does not transfer; only the computed result is preserved. We flag every Computed Field in the pre-migration audit and confirm with the customer which computed results are business-critical before including them in the migration scope.

Kinabase activities tracked against Records migrate as GoHighLevel engagements. Email activities map to GoHighLevel email records; call logs map to GoHighLevel call records with duration preserved; meeting records map to GoHighLevel calendar entries with date and duration. We resolve the activity owner by email match against GoHighLevel Users and link each engagement to the target Contact, Company, or Custom CRM Object record.

Kinabase standalone Tasks map directly to GoHighLevel Tasks. Assignee, due date, status, priority, and linked record association transfer directly. Tasks without an assignable GoHighLevel User are flagged in the reconciliation report for the customer's admin to resolve before import resumes.

Kinabase documents attached to Records are exported by filename and source URL reference. We map file associations to GoHighLevel's document management or the relevant record attachment. Actual file content transfer depends on whether GoHighLevel's storage supports the file type and size; we flag files that require direct re-upload rather than programmatic migration.

Kinabase stage values within a Collection (e.g., Draft, In Progress, Approved) migrate as categorical custom field values in GoHighLevel. If the destination Collection maps to GoHighLevel Opportunity, stage values map to GoHighLevel pipeline stage names that the customer configures in their pipeline builder before migration.

Kinabase workflows define stage progression, trigger-based automations, and role-based permission gates. GoHighLevel's Workflow Builder uses a different automation model with visual nodes, trigger conditions, and CRM actions that do not accept Kinabase workflow definitions as input. We do not migrate workflows as code. We audit every Kinabase workflow, document its trigger conditions and actions, and deliver a written handoff map for the customer's admin or GoHighLevel implementation partner to rebuild in the Workflow Builder.

Kinabase integrations with Microsoft 365 (Outlook activity capture, SharePoint folder organisation, Entra ID SSO) are connection-level configurations specific to the Kinabase tenant. These cannot be replicated in GoHighLevel. We document each active integration as a prerequisite for the customer's IT team to configure separately in GoHighLevel's settings post-migration.