Migrate from Ziggu to Zoho CRM

Ziggu clients (individuals) map directly to Zoho Contacts. Email, phone, and address fields transfer directly. The Contact's primary Account link is set if the client is associated with a company in Ziggu. If duplicate contacts exist, we apply a deduplication rule based on email uniqueness to prevent redundancy.

Ziggu clients recorded as companies map to Zoho Accounts. Company name, domain, industry, and employee count fields align with Zoho's standard Account fields. Multiple contacts per account are supported via Contact-Account relationships. During migration, we preserve the original company ID in a custom field for future synchronization and audit trails.

Each Ziggu project becomes a Zoho Deal. Project name maps to Deal Name; project description maps to Deal Notes; project stage (Active, Completed, On Hold) maps to Zoho Deal Stage. Development details like address, completion date, and unit count migrate as custom fields on the Deal.

Ziggu units within a project map to Zoho Line Items attached to the parent Deal. Unit number, type (apartment, villa, retail), size, price, and status fields transfer as Line Item fields. Each unit's buyer information links to the associated Contact.

Ziggu project documents (floor plans, contracts, selections) migrate as file attachments on the corresponding Zoho Deal. Files under 25MB migrate directly; larger files are split or linked. Document metadata (name, upload date, uploader) preserved as attachment properties. We also validate file integrity after migration to ensure no corruption occurs.

Ziggu tasks linked to projects and clients map to Zoho Tasks with the appropriate parent record (Deal or Contact). Due dates, assignees, and completion status transfer. Open tasks appear as pending; completed tasks preserve their closure timestamp. Task dependencies are captured in the description field for manual reconstruction if needed.

Ziggu approvals (client sign-offs, document reviews) cannot replicate as native workflows in Zoho. We migrate approval records as Tasks with a custom 'Approval_Type__c' field and 'Approval_Status__c' field. Zoho Blueprint should be configured to re-implement approval routing. Your admin can then set up email notifications and conditional logic within Blueprint to mirror the original flow.

Ziggu survey responses (NPS scores, post-handover feedback) need a custom module in Zoho CRM — 'Survey_Response__c'. Each response links to the original Contact and Deal. Survey questions map to custom fields within the module. We also migrate historical response dates and open-text answers for trend analysis.

Individual survey submissions migrate as records in the custom Survey_Response module. NPS score, response date, survey type, and free-text answers map to corresponding custom fields. Response is linked to the Contact who submitted it. We preserve the original submission timestamp to maintain longitudinal reporting accuracy.

Ziggu financials (payment schedules, invoice tracking) map to a custom 'Development_Finance__c' module linked to the Deal. Fields include total project value, amounts paid, pending amounts, and next payment due date. Payment history records link to individual Line Items. We also capture currency and payment method for comprehensive financial reporting.

Ziggu partners (contractors, suppliers) map to Zoho Accounts with Contact records for individual points of contact. Partner type (contractor, supplier, consultant) stores as a custom pick-list on the Account. Documents from partners attach to the associated Deal or Account. We preserve partner IDs in a custom field for future sync and audit.

Ziggu project conversations merge into Zoho Notes on the parent Deal and Activity records on the Contact. Key client decisions and approvals surface in Notes; general updates become Task descriptions. Original timestamps and participant information preserved. We also tag conversation categories to enable filtering and reporting within Zoho.