Migrate from Ziggu to HighLevel

Ziggu's client contacts map 1:1 to HighLevel contacts. We preserve name, email, phone, address, and any custom contact properties. The contact's primary project association is preserved as a tag (e.g., Project-[Name]) and optionally linked to a HighLevel opportunity representing that project.

Ziggu partner and contractor company records map to HighLevel companies. Company name, domain/website, industry, and employee count migrate directly. Ziggu's partner portal visibility flag has no HighLevel equivalent — we flag this for manual review after migration and adjustment in the target system.

Each Ziggu project with active deals or sales tracking becomes a HighLevel opportunity. Project name maps to Opportunity name, project status maps to pipeline stage, and close date maps to the opportunity close date. Projects without a sales component map to custom objects instead.

Ziggu's Multi-unit Projects add-on creates individual unit records under a project. These map to a HighLevel Custom Object named 'Unit' linked to the parent opportunity via a lookup relationship. Each unit's status (available, reserved, sold) becomes a custom pick-list field on the Unit object.

Ziggu tasks linked to projects and contacts migrate as HighLevel tasks. Original due dates, assignees (resolved by email match to HighLevel users), and task status are preserved. Unassigned tasks are flagged for manual owner assignment before the full run. Post-migration review ensures accuracy.

Ziggu's structured conversations per project and unit become HighLevel notes on the linked contact or opportunity. Each conversation thread is consolidated into a single note with a timestamp header and threaded message content. Original message authors are preserved in the note body.

Ziggu documents are re-uploaded as HighLevel files attached to the relevant contact or opportunity. File size limits apply — documents exceeding HighLevel's attachment size are flagged for alternative storage (Google Drive link stored in a custom field). Version history is not preserved; the latest version is migrated.

Ziggu survey responses with custom questions become records in a HighLevel Custom Object. Survey metadata (name, creation date, respondent) is stored on the custom object; individual question-answer pairs map to custom fields on that object. Survey logic and conditional branching require manual rebuild in HighLevel's form builder.

Ziggu Financials add-on payment schedules map to a HighLevel Custom Object named 'Payment' linked to the opportunity. Individual invoices with amounts and due dates become Payment records. Paid amounts update the opportunity amount field to maintain financial accuracy on the CRM side.

Ziggu labels and tags on contacts and projects migrate as HighLevel tags. Tags are preserved on contact and opportunity records for segmentation and workflow triggers. Ziggu's project-level tags (e.g., Unit type, Deal status) are prepended with a namespace (Project-) to avoid collision with contact-level tags.

Ziggu team members are resolved by email match to HighLevel users. If a Ziggu user has no corresponding HighLevel account, their records are assigned to a fallback owner and flagged for admin review. Ziggu role/permission settings do not migrate — those are destination-side HighLevel configuration.

Ziggu's built-in approval workflows for document sign-offs and decision chains have no direct HighLevel equivalent. We export the approval definition (approver sequence, thresholds, conditions) as a reference document for your admin to rebuild using HighLevel's workflow builder and e-sign integrations.