Migrate your Ziggu data

Projects are the top-level organizing entity and the billing unit in Ziggu. Each project has a status (active or deactivated), and when deactivated it transitions to read-only — only Conversations remain open. We import active projects as-is and flag any records targeting a deactivated project for pre-migration resolution.

Client records are tied to a project and represent the buyers or end-customers with portal access. We import client email addresses, names, and portal invitation status. Client records carry no standalone billing fields — costs are attributed to the parent project.

Units are sub-entities under a Project, used in multi-unit developments. Each unit tracks its own status, selections, and balance. The Multi-unit Projects add-on gates bulk-edit and bulk-share features per unit. We map units as child records of the parent project and preserve unit-level status fields.

Conversations are the threaded message inbox linked to a project and optionally to a specific unit or topic. This is the one area that remains writable even on deactivated projects. We import full message threads including timestamps, sender, and topic linkage.

Documents are versioned files attached to a project or unit. Ziggu tracks latest-version status per document. We import documents preserving version history where exposed, but binary file sizes are subject to Ziggu's storage limits on each tier — we flag oversized imports for tier-upgrade consideration before committing.

Tasks track action items within a project. On deactivated projects, tasks become read-only and no new tasks can be created. We import open tasks and map assignee IDs, due dates, and status labels to the destination's task schema.

Approvals are structured decision records — client confirmations on selections or milestones. We import approval records with their status (pending/approved/rejected) and timestamp. The approval workflow rules themselves are not exported via API and must be reconfigured in the destination.

Surveys in Ziggu collect NPS and custom multi-question feedback at defined project milestones. Survey definitions and response sets are distinct objects. We import survey templates and response aggregates; individual per-respondent response rows require field-level mapping to the destination's survey object.

Partners (suppliers and contractors) are invited to the Partner Portal as a separate access tier. Partner contact records are distinct from client records and are gated by the Partner Portal add-on. We import partner contacts and portal access status, but access permissions must be re-established on the destination platform.

Financials is an add-on covering payment schedules and invoice records per unit. This module is not available on all tiers and requires an active add-on subscription. We import payment schedule entries and invoice metadata, but invoice PDF attachments are subject to the same storage considerations as general documents.

The Sales add-on tracks leads, reservations, and contracts across units. These are pipeline-stage records that do not map directly to standard CRM Deal objects in most destinations. We import reservation and contract records as custom objects, preserving status and linked unit references.

Tags and labels in Ziggu are applied to projects, units, and documents for filtering. We import tag names and associations as flat key-value metadata attached to the relevant parent object.

Project Experience is a portal customization add-on controlling logo, colors, and layout per project portal. These are purely presentational settings with no structured data payload. We do not migrate these — they are reconfigured manually in the destination platform.