CRM migration
Field-level mapping, validation, and rollback between Ziggu and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Ziggu
Source
Freshsales
Destination
Compatibility
10 of 10
objects map 1:1 between Ziggu and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
Ziggu organizes property development communication — client portals, document sharing, selections tracking, and multi-unit project management — across projects and stakeholders. Freshsales organizes sales activity around Leads, Contacts, Accounts, and Opportunities with built-in lifecycle stages, deal scoring, and sales sequences. These are structurally different models, so migration requires careful object translation rather than a direct field-for-field copy. FlitStack AI maps Ziggu contacts to Freshsales Contacts, Ziggu organizations to Freshsales Accounts, and Ziggu deals to Freshsales Opportunities. Ziggu custom fields — unit_number, development_name, selection_status — migrate as Freshsales custom fields on the corresponding objects. Address components from Ziggu consolidate into Freshsales Address custom fields. Owner resolution happens via email match against Freshsales users; unmatched owners are flagged before migration commits. The migration runs against Freshsales' REST API within plan-rate limits (1,000 req/hr Growth, 2,000 req/hr Pro, 5,000 req/hr Enterprise). Email templates, workflows, automations, and Freshsales-specific features like Freddy AI contact scoring do not migrate and must be rebuilt post-migration. File attachments re-upload to Freshsales Files. A delta-pickup window captures records modified during cutover before final reconciliation.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Ziggu object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Ziggu
Contact / Stakeholder
Freshsales
Contact
1:1Ziggu contacts (homebuyers, partners, contractors) map directly to Freshsales Contacts. Name, email, phone, job title, and address fields transfer as-is without transformation. Owner resolution uses email match against Freshsales users; unmatched owners are flagged before migration commits. All contact custom fields including selection preferences and project associations are preserved during migration.
Ziggu
Organization / Company
Freshsales
Account
1:1Ziggu organizations map to Freshsales Accounts. Account Name, Website, Industry, Number of Employees, and Annual Revenue transfer directly. Ziggu parent-child organization relationships map to Freshsales Parent Account hierarchy where applicable. Organization-level custom fields are preserved and mapped to corresponding Freshsales custom fields on the Account object.
Ziggu
Deal / Project Deal
Freshsales
Opportunity
1:1Ziggu deals map to Freshsales Opportunities. Deal name becomes Opportunity Name, amount maps to Amount, and close date maps to CloseDate. The Ziggu pipeline and stage status map to a Freshsales custom picklist field since Freshsales uses stage probabilities rather than project-phase labels.
Ziggu
Custom Field: selection_status
Freshsales
Custom Field on Contact/Account
1:1Ziggu tracks client selection status (e.g., kitchen style, flooring choice) as a custom field per contact or unit. These migrate as Freshsales custom picklist fields (Selection_Status__c) so the data is queryable and reportable in Freshsales reports and dashboards. The picklist values are preserved as-is to maintain selection consistency across systems.
Ziggu
Custom Field: unit_number
Freshsales
Custom Field on Account/Contact
1:1Multi-unit project data (unit number, floor, block) from Ziggu migrates as Freshsales custom text fields (Unit_Number__c) on the Account or Contact. This preserves the unit association for development teams managing multiple properties per client. Unit-level custom fields are mapped to ensure property-specific information remains accessible in Freshsales.
Ziggu
Custom Field: development_name
Freshsales
Custom Field on Account/Opportunity
1:1The development or project name from Ziggu migrates as a Freshsales custom text field (Development_Name__c) so teams can filter deals and accounts by the specific property development without relying on account name alone. This field enables cross-property reporting and segmentation in Freshsales.
Ziggu
Address fields (street, city, postcode)
Freshsales
Account/Contact Address + Custom Fields
1:1Ziggu stores address components separately (street, city, state, postcode). Freshsales Account and Contact have structured address fields (Street, City, State, Zip). We concatenate components into Freshsales address fields and preserve the original structured values in custom fields for reference. Address validation ensures data integrity during migration.
Ziggu
Task / Email / Call
Freshsales
Task / Event
1:1Ziggu communication history — emails, calls, meetings — migrates as Freshsales Tasks (for emails and calls) and Events (for meetings). Original timestamps, task subjects, and owner attribution are preserved. The parent record link (contact or account) is re-established during migration.
Ziggu
File / Document attachment
Freshsales
Salesforce Files / Attachment
1:1Ziggu file attachments on contacts, organizations, or deals re-upload to Freshsales Files and attach to the corresponding record. Freshsales file size limits (25MB per file) apply; files exceeding this threshold are flagged for manual handling before migration runs. File metadata including creation date and author information is preserved.
Ziggu
Workflow / Automation
Freshsales
Workflow (Freshsales) / Not migrated
1:1Ziggu workflows and automated sequences do not migrate to Freshsales. They require manual reconstruction in Freshsales' workflow builder. We export Ziggu workflow definitions as a structured reference document to support your admin's rebuild effort. The exported document includes trigger conditions, actions, and execution logs for rebuilding.
| Ziggu | Freshsales | Compatibility | |
|---|---|---|---|
| Contact / Stakeholder | Contact1:1 | Fully supported | |
| Organization / Company | Account1:1 | Fully supported | |
| Deal / Project Deal | Opportunity1:1 | Fully supported | |
| Custom Field: selection_status | Custom Field on Contact/Account1:1 | Fully supported | |
| Custom Field: unit_number | Custom Field on Account/Contact1:1 | Fully supported | |
| Custom Field: development_name | Custom Field on Account/Opportunity1:1 | Fully supported | |
| Address fields (street, city, postcode) | Account/Contact Address + Custom Fields1:1 | Fully supported | |
| Task / Email / Call | Task / Event1:1 | Fully supported | |
| File / Document attachment | Salesforce Files / Attachment1:1 | Fully supported | |
| Workflow / Automation | Workflow (Freshsales) / Not migrated1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Ziggu gotchas
Deactivated projects lock tasks and files but keep conversations open
Per-active-project pricing creates a minimum portfolio cost
Add-ons scale per active unit, not per project
No public API means migration runs through manual export workflows
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Audit Ziggu data and build the migration schema plan
We connect to Ziggu via read-only API access (or CSV export where API is unavailable) and enumerate every object, field, and custom property in your account. We identify all custom fields — unit_number, development_name, selection_status, and others — and map each to a Freshsales custom field on the correct object (Contact, Account, or Opportunity). We deliver a Migration Schema Plan listing every field, its destination, the mapping type, and any transformation logic required before you commit to the migration run.
Create Freshsales custom fields and validate owner resolution
Before data moves, your Freshsales admin (or our team) creates the custom fields identified in the schema plan — Unit_Number__c, Development_Name__c, Selection_Status__c, and Source_System_ID__c on the appropriate objects. Simultaneously, we validate owner resolution by matching Ziggu owner email addresses against Freshsales user emails. Unmatched owners are flagged with a recommendation: invite them to Freshsales first, or assign their records to a fallback owner. No record migrates without a confirmed Freshsales owner.
Run a sample migration and generate a field-level diff
A representative slice — typically 100–300 records spanning contacts, accounts, deals, and a few tasks — migrates into Freshsales first. We generate a field-level diff comparing source and destination values for every mapped field so you can verify custom field mapping, owner resolution, and address consolidation before the full run. Any mapping errors surface here and get corrected in the migration engine before the full migration commits. This step typically completes within 24 hours of your approval.
Execute full migration with delta-pickup window and reconciliation
The full migration runs against Freshsales' REST API, paced to respect plan-based rate limits. A delta-pickup window (24–48 hours after initial load) captures any records modified in Ziggu during the cutover. We run a record-count reconciliation across all objects and verify that custom field values, owner assignments, and attachment file links match expectations. Audit logs capture every operation. One-click rollback is available if reconciliation reveals unexpected discrepancies.
Platform deep dives
Ziggu
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Ziggu and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Ziggu: Not publicly published — Ziggu states limits are tuned to integration use cases and confirmed during onboarding.
Data volume sensitivity
Ziggu doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Ziggu to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Ziggu to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Ziggu
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.