Migrate from Knack to HighLevel

Knack Tables storing individual person records map to GoHighLevel Contact. We inspect each Table's field inventory and identify which ones represent person-centric data (name fields, email, phone, address, relationship fields). If the Knack Table has Connection fields pointing to other Tables, we resolve those as GoHighLevel lookup relationships (Contact-to-Company via the Company lookup field, or Contact-to-Custom Object via custom lookup fields we pre-create in GoHighLevel). Email addresses serve as the dedupe key during import.

Knack Tables storing company or organization records map to GoHighLevel Company. The Table's name field becomes the Company name; domain or website fields map to the Company Website field. If the Knack Table is referenced by Contact-role Tables via Connection fields, we create the Company first during migration so that the Contact-to-Company relationship is satisfied at insert time.

Knack Tables tracking deal value, project status, or transaction records map to GoHighLevel Opportunity. The Table's stage-like fields (status, phase, milestone) map to GoHighLevel pipeline stages. We create a Custom Pipeline in GoHighLevel that mirrors the Knack Table's stage values before migration so that stage assignment is valid on insert. The Table's monetary or value fields map to Opportunity Amount.

Knack Connection fields are foreign keys between Tables (one-to-many or many-to-many). We translate each Connection field into a GoHighLevel lookup field. If the connection points from Contact-role Table to Organization-role Table, the lookup becomes the native Contact-to-Company relationship. If the connection points to a custom object, we pre-create the lookup field in GoHighLevel and resolve the referenced record ID during migration using the Knack-to-GoHighLevel ID mapping built in earlier phases.

Knack file fields store documents, images, and PDFs accessible via authenticated URL. We download each file from Knack, preserve the original filename and MIME type, and re-upload to GoHighLevel as a Contact or Opportunity attachment using the GoHighLevel API. File-to-record linkage is preserved by matching the Knack record ID to the migrated GoHighLevel record ID via the ID mapping table.

Knack supports 15+ field types. Standard types (text, number, currency, date, yes/no) map directly to equivalent GoHighLevel field types. Knack Equation fields (computed values) do not have a GoHighLevel equivalent; we export the computed result as a read-only custom field and document the formula for the customer to rebuild as a GoHighLevel Workflow formula field if needed. We pre-create all custom fields in GoHighLevel before the record import phase.

Knack Views are saved filtered or sorted record subsets defined by the builder. They are a Knack UI concept with no direct GoHighLevel equivalent. We export the full list of Views and their filter conditions as a written reference document. The customer recreates the equivalent saved views in GoHighLevel using the filter builder on Contact and Opportunity list views. This is out of scope for data migration but is explicitly documented in the handoff.

Knack roles control Page and record access. We export role names and their permission scope as metadata. GoHighLevel uses a Team model for permission assignment. We map Knack roles to the closest GoHighLevel Team configuration and flag any Knack role permissions that require manual configuration in GoHighLevel (sub-account access, reporting permissions, pipeline visibility). Active user count in Knack maps to the GoHighLevel user count for subscription planning.