Migrate from Atollon Lagoon CRM to HighLevel

Atollon Folders with client, potential client, partner, or other classification columns map to GoHighLevel Contacts. The Folder's custom classification column maps to a Contact tag or custom field in GoHighLevel depending on whether the classification is a simple label or a structured value. Folder-level custom forms attached via formID and formvalue records are parsed individually; each formvalue field is mapped to a GoHighLevel Contact custom field with the field type resolved from the form schema. The migration resolves Folder-to-Firm parentage before import so that the contact's company association is set correctly.

Atollon Firms map to GoHighLevel Companies. The Firm's custom classification column (client, potential client, partner) maps to a GoHighLevel Company tag or custom field. Firm address data maps to GoHighLevel's address fields (street, city, state, postal_code, country). Any custom form data attached to the Firm via formvalue records is parsed against the formID and mapped to Company custom fields.

Atollon Projects span at least four subtypes — Contracts, Business cases, Service contracts, and Consultations — each using different templates with potentially different custom field sets. We classify each project by its template origin, then apply the correct mapping schema. Projects with a generic template default to a generic mapping. In GoHighLevel, projects map to Opportunities using the pipeline stage to represent project status, with subtype recorded in a custom Opportunity field. If the customer has more than four project subtypes with materially different schemas, we discuss creating GoHighLevel custom objects for each subtype rather than forcing all project data into the Opportunity object.

Atollon Activities (calls, emails, meetings, tasks) linked to Folders or Firms map to GoHighLevel Tasks. Email activities land as Tasks with the email body preserved; call activities land as Tasks with TaskSubtype=Call and duration preserved; meeting activities land as Tasks with meeting type noted. Activity timestamps and owner references migrate directly. We resolve the Activity's parent Folder or Firm reference to the corresponding GoHighLevel Contact or Company lookup.

Atollon Milestones track timeline checkpoints within Projects or Activities. They may carry custom form data via formvalue records. We map Milestones preserving their order, due date, and any custom field values. Milestones with simple date and status map to GoHighLevel Tasks; Milestones with complex custom form data map to Task custom fields. Parent-project lookup is resolved to the corresponding GoHighLevel Opportunity at migration time.

Atollon custom form values are stored in formvalue records linked to the parent object by formID and context. The relationship between form and formvalue is not always 1:1 — one parent record may have multiple formvalues from different form schemas. We parse each formvalue record individually, resolve the field schema via formID, and map field-level values to GoHighLevel custom fields of the corresponding type. This normalization step is required for every custom form attached to Folders, Firms, Projects, Activities, and Milestones, and adds processing time proportional to the number of formvalue records in the dataset.

Atollon service and support module manages ticket-like records. We map these to GoHighLevel Tickets, preserving status, priority, assigned agent, and linked Firm and Project references. Ticket thread history migrates as a linked activity log or note on the Ticket record. The service agent assignment resolves against the GoHighLevel User table by email match.

Atollon invoices linked to Projects or Firms migrate as Invoice records. We map invoice header data, line items, amounts, and status. Detailed financial history migration depends on the GoHighLevel plan tier and whether invoices are handled via a native integration (QuickBooks, Stripe) or as custom objects. The customer chooses the invoice strategy during scoping. Invoice PDFs are not migratable as attachments in the standard scope; we document the invoice record count and field set for manual handoff.