Migrate from OctopusPro to HighLevel

OctopusPro Customers map to both a GoHighLevel Company (Account) record and a Contact record. The customer's primary address and business details populate the Account; personal contact fields (name, email, phone) populate the Contact. If the OctopusPro customer has multiple service locations, each location becomes a separate Account linked to the primary Contact. Custom fields on the OctopusPro customer profile migrate to custom fields on the GoHighLevel Contact or to a linked Custom Object if the schema is complex.

OctopusPro Bookings are the central appointment object — linking a Customer, one or more Field Workers, a Service, time slot, status, and an associated Invoice. We map Bookings to GoHighLevel Opportunities using the Pipeline builder, with booking status mapped to Opportunity stage values. If the customer uses GoHighLevel's appointment scheduling module (Calendar, Pipeline, Opportunities), the Booking date, time, and assigned worker fields migrate into custom Opportunity fields. Field Worker assignments migrate as Opportunity Team Members or into a custom lookup field.

OctopusPro Jobs are detailed work records attached to a Booking, often containing line items, job-specific notes, photos, and checklist data. Jobs map to a GoHighLevel Custom Object named 'Job' with custom fields for job description, status, and pricing pulled from the OctopusPro job record. We link the Job Custom Object to the originating Contact and Opportunity via lookup fields during migration.

OctopusPro Field Worker records (name, role, contact details, pay rates, GPS tracking preferences) map to GoHighLevel User accounts. Field workers who will use GoHighLevel's mobile app and scheduling features receive active User accounts; administrative-only workers receive either active or inactive accounts based on the customer's user-seat planning.

OctopusPro Invoices (line items, tax, totals, payment status) tied to Bookings migrate into GoHighLevel Opportunities as custom invoice fields (total amount, amount paid, balance due, invoice number) or into a dedicated Invoice Custom Object if the customer's workflow requires invoice record tracking. We preserve the invoice-to-booking relationship by linking the destination Opportunity to the Booking.

OctopusPro Payment records (amount, method, date, status) migrate as payment transaction fields on the related GoHighLevel Opportunity or as records in a Transaction Custom Object. Partial payments and refund scenarios are flagged during scoping and resolved with custom fields tracking outstanding balance and refund status.

OctopusPro Quotes (pre-booking documents with line items, validity dates, and accept/reject status) migrate to GoHighLevel Opportunities with custom fields for quote amount, expiry date, and status. Accepted quotes migrate with status set to Closed Won; declined quotes set to Closed Lost.

OctopusPro Service definitions (name, description, pricing rules, duration, service-area constraints) migrate to GoHighLevel Product2 records or a Service Custom Object depending on whether the customer uses GoHighLevel's product and quote features. Service pricing and duration migrate as custom fields for use in Opportunity line items and workflow triggers.

OctopusPro Forms and Checklists capture structured field data — job photos, tags, custom intake information — with schema varying by service type. We map available form fields to GoHighLevel Form fields or to custom fields on the linked Custom Object. Intake forms that must be reconfigured at the destination are documented in the migration scope for manual rebuild as GoHighLevel native Forms.

OctopusPro tenant-specific custom fields on customer profiles and bookings are discovered during scoping by reviewing the support-assisted export. We pre-create equivalent GoHighLevel custom fields or Custom Object schema before migration begins, flagging any field-type incompatibilities (e.g., OctopusPro list fields that have no direct GoHighLevel multi-select equivalent). The custom field inventory is part of the migration scope deliverable.

The OctopusPro Customer Portal is a configuration layer controlling online booking display, invoice visibility, FAQ access, and payment links. These settings are not independent data objects and do not migrate. We migrate the underlying customer records, bookings, and invoices that the portal surfaces. Portal display preferences, permission flags, and branded theme settings must be reconfigured manually in GoHighLevel's Customer Portal or Membership site settings.