Migrate from Ziggu to HubSpot

Ziggu client portal users map directly to HubSpot Contacts. We preserve name, email, phone, job title, and company association. Original contact create date migrates to a custom datetime field since HubSpot's CreatedDate reflects the migration timestamp. Owner resolution uses email matching against HubSpot users.

Ziggu companies (developer firms, contractor firms) map to HubSpot Companies. We transfer company name, website, industry, employee count, and address fields. Ziggu's company hierarchy (parent/child) maps to HubSpot's Parent Company field. Multi-company associations per contact collapse to the primary CompanyId lookup.

Ziggu projects map to HubSpot Deals by default. Each project becomes one Deal with the project name as the Deal name, project value as the Amount, and project stage mapped to Deal stage via value mapping. If Ziggu's multi-unit add-on is active and units need individual tracking, we recommend a custom Unit object in HubSpot instead — your admin chooses before migration runs.

Ziggu units (apartments, lots, floors) can split into HubSpot Deal line items or a custom Unit object. Line items preserve the unit price and quantity per deal. If a custom object is used, units link to the parent Deal via a lookup field. The choice affects HubSpot reporting — line items aggregate naturally into deal revenue; custom objects require custom reporting.

Ziggu documents and file attachments re-upload to HubSpot Files. Each file is attached to the parent Project (Deal) or Unit record. File size limits per HubSpot apply (default 25MB per file). Inline images in Ziggu notes download and rehost as HubSpot file attachments. Version history is simplified to the latest approved version.

Ziggu's structured client conversations map to HubSpot Engagements — logged as Notes with timestamps on the contact or deal record. Each message thread becomes a Note entry with the sender, timestamp, and message body. Real-time threading structure is simplified; the chronological narrative per contact or project is preserved.

Ziggu tasks map directly to HubSpot Tasks. We transfer task subject, due date, completion status, assigned owner (via email match), and association to the parent Project (Deal). Completed tasks preserve the completion timestamp. Open tasks import as open HubSpot tasks.

Ziggu approval workflows (design selections, financial approvals, document sign-offs) have no HubSpot equivalent. We preserve the approval status (Approved/Rejected/Pending) as a custom property on the Deal or Unit record. The approval workflow logic must be rebuilt in HubSpot's Workflows tool or a third-party approval app.

Ziggu's NPS scores and survey responses migrate as custom number properties on the Contact record. We create a ZNPS_Score__c custom property and a ZSurvey_Response__c text property for multi-question responses. Survey logic (when to send, which questions) must be rebuilt in HubSpot Forms or a third-party survey tool.

Ziggu payment schedules and invoice records map to HubSpot Deal line items (for payment amounts and due dates) and custom fields (for invoice status). The financial workflow (payment tracking, balance due) is simplified — HubSpot has no native billing engine. Recurring payment logic must be rebuilt or handled via a finance integration.

Ziggu's Partner Portal contacts split into HubSpot Company records (for the firm) and Contact records (for individual contacts at that firm). The firm's portal access and role map to a custom Partner_Type__c property on the Contact. Partner-specific documents attach to the company or deal as appropriate.

Ziggu portal owners and users resolve to HubSpot Users by email address match. Unmatched owners are flagged before migration — your team either invites them to HubSpot first or assigns their records to a fallback owner. Ziggu's role permissions (Admin, Team Member, Client) do not map to HubSpot roles and must be reconfigured in HubSpot's settings.

Ziggu's Project Experience add-on white-labels the client portal per project with custom colors, logos, and layout. HubSpot's portal branding is scoped to HubSpot's own tools (meetings portal, customer portal, quotes). Client-facing project portals require a separate web build or HubSpot's CMS. We preserve the branding settings as a reference document for your web team.

Ziggu's internal tags and labels on projects, units, or clients migrate as HubSpot custom properties — a multi-select picklist or single-line text depending on volume. Tags used for segmentation in Ziggu translate to HubSpot contact or deal properties for use in lists and workflows.

Any Ziggu custom fields beyond the standard set require HubSpot custom properties created before migration. We deliver a custom property creation plan based on Ziggu's property list. Property types map: text → single-line text, number → number, date → date/datetime, dropdown → dropdown select, multi-select → multi-checkbox.