Migrate from Ziggu to Nutshell

Ziggu Clients map directly to Nutshell People. Primary contact fields (name, email, phone, job title) transfer 1:1. Ziggu's multi-stakeholder-per-project model means some records may represent organizations rather than individuals—in those cases, we map to Nutshell Company instead and link the primary contact as a Person record.

Ziggu records where the 'client' is an organization (e.g., property developer company) rather than an individual contact map to Nutshell Company. We examine the contact fields: if no individual name is present, the record lands as a Company with the organization name in the Name field.

Ziggu Projects map to Nutshell Deals as the primary container for project-related work. Project phase and status values map to Nutshell Deal stage names via value mapping. Project name becomes Deal name; projected value (if present in Financials add-on) maps to Deal amount. The Deal's associated Person/Company carries the client relationship.

For projects where the client organization is tracked as the primary entity, we merge the Project record into the corresponding Nutshell Company record, preserving project metadata as custom fields on the Company. This handles Ziggu's model where Projects live under organizations.

Ziggu Units (the multi-unit add-on for property developers tracking individual apartments or lots within a project) do not have a direct Nutshell equivalent. Units migrate as a custom multi-value field or as a text blob listing unit IDs and statuses, attached to the parent Nutshell Deal. Admin decides whether units should appear as separate Deals or as a custom field.

Ziggu Conversation threads map to Nutshell Activities. Each thread's messages become individual Note records in Nutshell with the original timestamp, sender name, and linked Person. Approval requests within threads surface as flagged Notes requiring admin follow-up in Nutshell. This mapping preserves the chronological conversation history while flagging items that need team attention after migration, ensuring nothing falls through the cracks during the transition.

Ziggu Tasks map to Nutshell Tasks with subject, due date, assignee, and completion status preserved. Open tasks carry over as open Tasks; completed tasks migrate with their completion timestamp. Assignees are resolved by email match against Nutshell users. This direct mapping ensures your team's work queue continuity, with all pending and completed tasks visible in Nutshell's task management view immediately after migration.

Ziggu Documents attach to their parent Project and migrate as Attachments on the corresponding Nutshell Deal (or Company/Person). File versions are not natively preserved in Nutshell—we migrate the latest version. If document approval status is tracked, it migrates as a custom field.

Ziggu's Partner Portal gives suppliers and contractors portal access to project data. Nutshell has no portal feature for external stakeholders. This access model does not migrate; partners must be invited as Nutshell users (internal licensing applies) or managed outside the CRM.

Ziggu Survey responses (the Surveys add-on) map to Nutshell custom fields capturing response data, submitted date, and NPS or rating score. Survey definitions (question logic, branching) do not migrate and must be rebuilt in a dedicated survey tool or Nutshell's custom field setup.

Ziggu Financials (payment schedules, invoice tracking, balance visibility) migrate as custom fields on the Nutshell Deal. Payment schedule rows can be stored as a structured text field or in a linked custom object if the migration scope includes Nutshell custom objects. Actual invoice files attach to the Deal as documents.