Migrate from Workbooks to HighLevel

Workbooks Organisations are first-class company records. GoHighLevel does not have a native Account object; company data is stored in Contact fields or Custom Objects. We create a GoHighLevel Custom Object named Company (or use Contact-level address and custom fields) as the destination for Organisation data, preserving Organisation name as company name, industry, classification, and address fields. The Custom Object is created before any Person import so that the lookup relationship is satisfied at Contact insert time.

Workbooks People map directly to GoHighLevel Contacts. We preserve the Organisation link by setting the Custom Object (Company) reference on each Contact during import. Email, phone, job title, and all standard Person fields migrate to typed Contact fields. Custom fields on the Person record migrate to GoHighLevel Contact custom fields by name and type. If the destination is a GoHighLevel sub-account without a pre-created Custom Object, we fall back to address-field grouping by organisation name to preserve account context.

Workbooks Opportunities map to GoHighLevel Opportunities. Pipeline stage names and probability percentages transfer to GoHighLevel pipeline columns and stage weights. We resolve the Organisation (Company) reference at migration time so that each Opportunity is linked to the correct parent company record. Expected close date and owner assignment transfer directly.

Workbooks pipelines are replicated as GoHighLevel Pipelines. Each pipeline becomes a GoHighLevel pipeline with stage columns. We configure stage order, probability weights, and any custom fields scoped to a pipeline during the schema design phase before record import begins.

Workbooks Cases map to GoHighLevel Tickets. Case status, priority, assigned user, related Organisation, and description transfer to the corresponding Ticket fields. Open and resolved cases migrate with their status intact. Case activities that are logged as separate engagement records migrate via the Tasks endpoint linked to the Ticket.

Workbooks Activities by type map to GoHighLevel equivalents: call activities become GoHighLevel Calls with duration and disposition; emails become Tasks with notes content; meetings become Calendar Events; standalone tasks become Tasks. Activity links to Organisation and Person are resolved at migration time using the pre-imported Custom Object and Contact records so that the timeline is complete against the correct parent records.

Workbooks Quotations (available on Business tier) contain a header and line items. GoHighLevel has no native quotation object. We map quotation header data to a GoHighLevel Custom Object named Quotation (or Proposal), with line items stored as child Custom Object records or as JSON text in a long-text field. If the customer has PDF exports of signed quotations, we upload them as attachments to the related Opportunity. Workbooks quotation templates do not migrate; we document the template structure for manual recreation in GoHighLevel.

Workbooks Invoices (Business tier) do not have a native GoHighLevel equivalent. We map invoice header data, line items, payment status, and credit note associations to a Custom Object named Invoice. Invoice PDFs are downloaded and uploaded as Opportunity or Contact attachments. We flag any outstanding invoice balances as a reconciliation item for the customer's finance team post-migration. Recurring invoice schedules do not migrate and are documented for manual configuration in GoHighLevel.

Workbooks custom fields vary by deployment. We enumerate every custom field per record type during scoping by accessing a read-only Workbooks login. Text, number, date, dropdown, and checkbox fields map to typed GoHighLevel custom fields. File-upload fields require separate binary extraction and upload to GoHighLevel attachments. iFrame custom fields export as URL strings and are mapped as text fields in GoHighLevel; the embedded content does not carry over.

Workbooks Campaigns track marketing initiatives and associated memberships. We extract campaign name, status, start and end dates, and associated contact memberships as custom field data on the migrated Contacts. GoHighLevel Campaigns replicate this with tags and pipeline stages; we document the campaign membership mapping for the customer's marketing team to reassign post-migration.