Migrate from ZeyOS to HighLevel

ZeyOS Accounts map to GoHighLevel Contacts with the company name stored in the Contact's Company field and a GoHighLevel Location record created for address and phone data. The Location record preserves the ZeyOS account's primary address, billing address, and contact phone numbers. We use the account's external ID from ZeyOS as a custom GoHighLevel field for reconciliation after import.

ZeyOS Contacts map directly to GoHighLevel Contacts with name, email, phone, and the parent Account link preserved via the Company field. The ZeyOS extdata fields (nickname, custom address fields) migrate as GoHighLevel custom properties with type inference from the ZeyOS fields table schema. Any ZeyOS Contacts without an email are flagged for manual review because GoHighLevel's import process requires an email or phone for deduplication.

ZeyOS Leads are a distinct object from Contacts and carry lead-specific status fields. We map ZeyOS Leads to GoHighLevel Contacts and apply a migration-specific tag (e.g., 'migrated-lead') plus the original ZeyOS lead status as a custom property. The customer decides during scoping whether to keep migrated Leads as GoHighLevel Contacts or use GoHighLevel's pipeline/opportunity model for lead-stage tracking.

ZeyOS Items (inventory and product catalog with barcode, model, and custom fields) map to GoHighLevel Products. Stock quantities from ZeyOS's automated inventory system do not migrate because GoHighLevel has no native inventory management. We store the last known stock quantity as a custom Product property and flag the absence of live inventory sync for the customer's admin to address via Zapier or a dedicated inventory integration.

ZeyOS Projects with Tasks, subtasks, and time entries require restructuring in GoHighLevel. For service businesses, we map Projects to GoHighLevel Opportunities with a custom Project Name field and Tasks as GoHighLevel Tasks linked to the Contact. For project-management-heavy teams, we pre-create a GoHighLevel Custom Object named 'Project' with lookups to Contact and custom fields for project status, budget, and dates. The customer selects the model during scoping.

ZeyOS Tasks belonging to Projects map to GoHighLevel Tasks with assignee, due date, and status preserved. Parent-Project linkage is maintained by adding the GoHighLevel Opportunity or Custom Project ID as a custom Task field since GoHighLevel Tasks do not have a native Project lookup. ZeyOS custom workflow flags on Tasks migrate as GoHighLevel Tags or custom task properties.

ZeyOS Tickets (Helpdesk with email integration and subject-line ticket numbering) map to GoHighLevel as either a separate pipeline stage within the Opportunities object or as a GoHighLevel Custom Object named 'Ticket' with Status, Priority, and linked Contact. We recommend the Custom Object approach if the customer needs a separate support queue from their sales pipeline.

ZeyOS Contracts (subscription or service agreements tied to Accounts) map to a GoHighLevel Custom Object named 'Contract' with Account lookup, start/end dates, and contract value. Contract terms and renewal rules require manual rebuild in GoHighLevel; we deliver the contract metadata and a written recommendation for renewal reminder workflows using GoHighLevel's automation builder.

ZeyOS Users (team members who own records and create files) map to GoHighLevel Users by email match. We resolve ZeyOS user_id to GoHighLevel User ID for owner assignments on Contacts, Opportunities, and Tasks. Inactive ZeyOS users are flagged for deactivation review in GoHighLevel before migration begins.

ZeyOS's five financial objects (Quotes, Orders, Deliveries, Invoices) form a billing pipeline that GoHighLevel does not natively replicate. We create GoHighLevel Custom Objects for each financial type with line items, totals, dates, and status. Audit-locked ZeyOS invoices are sequenced in strict chronological order before import and flagged if any are out of sequence, because locked records cannot be modified or deleted via the ZeyOS API after booking.

ZeyOS Activities (engagements linked to Accounts or Contacts) map to GoHighLevel Contacts with timeline entries. Calls migrate as GoHighLevel call log entries; emails as activity notes; meetings as calendar events with the Contact linked. We use GoHighLevel's REST API to insert activities in chronological order to preserve the timeline sequence. Note attachments migrate as GoHighLevel documents linked to the Contact.

ZeyOS Time Entries (billable or non-billable hours against Projects, Tasks, or Tickets) map to a GoHighLevel Custom Object named 'TimeEntry' with linked Contact, Project reference, date, hours, and description. If the customer uses GoHighLevel's built-in task tracking, time entries attach as custom fields on the relevant Task.

ZeyOS files stored in the files table with binary blobs in the binfile column are downloaded individually via the ZeyOS REST API and re-uploaded to GoHighLevel Documents linked to the parent Contact, Opportunity, or Project record. Files exceeding 25MB are flagged for customer review before import because GoHighLevel has documented upload size limits. We validate MIME types and convert non-standard formats as needed.

ZeyOS custom fields exposed via the fields table and extdata JSON pattern in the REST API are read as field definitions and mapped to GoHighLevel custom properties with equivalent data types. Multi-select, date, number, and text field types map directly; ZeyOS-specific types are inferred from the extdata structure. We create the GoHighLevel custom properties before any data import so that the destination fields exist during record insertion.