CRM migration
Field-level mapping, validation, and rollback between Zixflow Marketing Automation and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Zixflow Marketing Automation
Source
Freshsales
Destination
Compatibility
9 of 10
objects map 1:1 between Zixflow Marketing Automation and Freshsales.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Zixflow Marketing Automation to Freshsales restructures how contacts, lists, and messaging fit into your CRM. Zixflow stores contacts in a single flat object with Collections serving as list groupings and Flows handling automation; Freshsales uses the Lead-Contact-Account model with separate List objects and a Workflows add-on. We map Contacts to either Lead or Contact based on qualification status, preserve Collection membership as Freshsales Lists, and transfer custom AI enrichment fields as typed custom fields. WhatsApp, SMS, and RCS conversation threads migrate as activity log entries, but delivery status tracking does not carry over. Flows (automation logic) cannot migrate; we deliver a written inventory of each Flow for your team to rebuild in Freshsales Workflows. Reports, dashboards, Forms, and wallet-based messaging credits are excluded from migration scope.
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 Zixflow Marketing Automation 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.
Zixflow Marketing Automation
Contact
Freshsales
Lead or Contact (qualification split required)
1:manyZixflow Contacts are a single flat object where qualification status is implied by custom properties. Freshsales uses separate Lead (unqualified) and Contact (qualified, tied to an Account) objects. We apply a qualification rule during migration scoping: contacts with an active Deal or a Collection membership that implies a sales pipeline stage map to Freshsales Contact under a mapped Account; contacts without Deals or with only marketing list memberships map to Freshsales Lead. Original Zixflow contact IDs and any AI enrichment data are preserved in custom fields for audit.
Zixflow Marketing Automation
Company
Freshsales
Account
1:1Zixflow Companies map directly to Freshsales Accounts. Company domain and address fields transfer to the Account Website and Address fields. Account is created before Contact import so that the Account-Contact Lookup is satisfied at insert time. Deduplication is performed on Company name plus domain to prevent duplicate Accounts when multiple Zixflow Companies share a domain.
Zixflow Marketing Automation
Collections
Freshsales
List
1:1Zixflow Collections are named groupings that function as lists and segments. Each Collection becomes a Freshsales List with the same name. Contact membership maps via Freshsales List Membership records. Zixflow contacts belonging to multiple Collections generate multiple List Membership records. We export the Collection-to-Contact membership as a lookup table before migration so that list membership resolves correctly after the Contact-to-Lead split.
Zixflow Marketing Automation
Flows (Automations)
Freshsales
Workflow (not migrated)
1:1Zixflow Flows are automation logic built in a proprietary visual builder with no documented export or migration path. Flows do not transfer in bulk data exports. We export the Flow name, trigger type, step summary, and action list as a written document that your admin uses to rebuild each Flow in Freshsales Workflows. Note that Freshsales Workflows are a priced add-on ($5 for 10 workflows on Growth plan).
Zixflow Marketing Automation
Forms
Freshsales
Contact Custom Fields
1:1Zixflow Forms capture leads and feed data into Contacts and Collections. Form field definitions export as a field inventory. Each form submission migrates as a Contact record with the form name stored in a custom field form_source__c and the submitted field values mapped to matching Freshsales custom fields by name and type. Submission timestamps and UTM parameters migrate as additional custom fields on the Contact record.
Zixflow Marketing Automation
Custom Properties
Freshsales
Custom Fields
1:1Zixflow custom contact properties including AI-generated enrichment fields export as flat key-value pairs. We audit every custom property, classify by data type (text, number, date, picklist, multi-select, phone), and create equivalent Freshsales custom fields before data import. AI enrichment values that have no exact Freshsales equivalent (such as custom scoring fields or confidence scores) are stored as Number or Text fields with the original field name preserved in the label for audit clarity.
Zixflow Marketing Automation
Inbox (Conversations)
Freshsales
Activity Log
1:1Zixflow Inbox aggregates multichannel conversations from WhatsApp, SMS, Email, and RCS. Message threads and timestamps export via API and migrate as Notes attached to the related Freshsales Contact or Lead. Thread metadata (channel, direction, timestamp) is preserved. We flag that WhatsApp and RCS delivery status (sent/delivered/read) is Zixflow-internal tracking and does not map to Freshsales native delivery analytics; WhatsApp delivery status does not transfer.
Zixflow Marketing Automation
Subscribers (WhatsApp)
Freshsales
Contact Custom Fields
1:1WhatsApp Subscriber opt-in records export with contact association and subscriber status. Opt-in date, status (active/inactive), and any subscriber tags migrate as custom fields on the Freshsales Contact. The Zixflow default subscriber cap of 500 per workspace has no Freshsales equivalent, but WhatsApp Business audience management in Freshsales Suite requires separate configuration of the WhatsApp Business channel. Subscriber count does not carry a billing implication in Freshsales.
Zixflow Marketing Automation
Deal
Freshsales
Deal
1:1Zixflow Deals map directly to Freshsales Deals. Deal name, amount, stage, owner, and expected close date transfer to matching Freshsales Deal fields. The Zixflow deal stage names map to Freshsales Deal stage values, and the deal pipeline assignment maps to a Freshsales Sales Process. Closed-Lost and Closed-Won reasons from Zixflow custom fields migrate as Freshsales Loss Reason and Won Reason fields if configured.
Zixflow Marketing Automation
Automation Credits / Wallet Balance
Freshsales
Not migrated
1:1Flow automation credits and Zixflow Wallet messaging credit balances are billing metrics, not customer data records. They do not migrate. We note the current Flow credit balance and Wallet balance as reference figures for the customer to plan account closure. Remaining messaging credits in the Zixflow Wallet are forfeited or drained before the account is closed, per Zixflow account terms.
| Zixflow Marketing Automation | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Lead or Contact (qualification split required)1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Collections | List1:1 | Mapping required | |
| Flows (Automations) | Workflow (not migrated)1:1 | Not supported | |
| Forms | Contact Custom Fields1:1 | Mapping required | |
| Custom Properties | Custom Fields1:1 | Mapping required | |
| Inbox (Conversations) | Activity Log1:1 | Fully supported | |
| Subscribers (WhatsApp) | Contact Custom Fields1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Automation Credits / Wallet Balance | 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.
Zixflow Marketing Automation gotchas
Flow automation logic is non-transferable
API fair usage caps at 200 POST/PATCH per second per workspace
CSV import limit of 100,000 records and 50MB per file
Subscribers have a default cap of 500 WhatsApp contacts
Messaging and automation credits are separate billing systems
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
Discovery and scope audit
We audit the Zixflow workspace across Contacts, Companies, Collections, Flows, Forms, Subscribers, Deals, and custom properties. We record total record counts per object, the number of active Flows, Collection membership volumes, custom property names and sample values for type classification, and any message history volumes. The discovery output is a written migration scope confirming object-level coverage, a preliminary field mapping table, and the Flow inventory request.
Schema design and Freshsales setup
We design the destination schema in Freshsales. This includes creating custom fields for every Zixflow custom property (with type-mapped Freshsales field types), designing the Lead-Contact qualification split rule based on Deal presence and Collection membership, creating Freshsales Lists corresponding to each Zixflow Collection, and configuring Deal stage names to match the Zixflow dealstage values. We deploy the schema to a Freshsales Sandbox for validation before production migration begins.
Flow documentation and workflow inventory
We extract every active Zixflow Flow with its trigger type, condition branches, actions, and expected outcomes. This inventory is formatted as a written handoff document for the customer's admin team to use when rebuilding Flows as Freshsales Workflows. Flows are not executed or imported during migration; they are documented for manual rebuild post-migration. We flag any Flows that reference Zixflow-specific objects (wallet credits, subscriber tags) so the admin knows which actions require fresh configuration in Freshsales.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Zixflow Companies), Contacts and Leads (with the qualification split applied), Deals (with resolved AccountId and OwnerId), Custom fields on all records, Collection-to-List membership via the lookup table, Subscribers (WhatsApp opt-in data) as Contact custom fields, and Inbox conversation history as Notes on Contact and Lead records. Each phase emits a row-count reconciliation report before the next phase begins.
Collection-to-List membership resolution
We export the full Collection-to-Contact membership as a lookup table before migration begins. After the Contact-to-Lead split is applied and all Contact and Lead IDs are resolved in Freshsales, we map the original Zixflow Collection memberships to Freshsales List Membership records using the resolved Freshsales IDs. Contacts belonging to multiple Collections generate multiple List Membership records. Contacts without email addresses cannot be assigned to Lists via standard import and are flagged for manual review.
Cutover, delta sync, and post-migration handoff
We freeze Zixflow writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver the Flow inventory document, the Collection-to-List mapping reference, and a record-count reconciliation report showing counts per object in both systems. We support a one-week post-migration window for reconciliation issues. We do not rebuild Zixflow Flows as Freshsales Workflows within migration scope; that is a separate engagement for the customer's admin team.
Platform deep dives
Zixflow Marketing Automation
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Zixflow Marketing Automation and Freshsales.
Object compatibility
3 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
Zixflow Marketing Automation: 150 requests per second across the workspace; exceeding it returns a 'Too many requests, try again later!' error and requires backoff before retry.
Data volume sensitivity
Zixflow Marketing Automation 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 Zixflow Marketing Automation to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Zixflow Marketing Automation 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 Zixflow Marketing Automation
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.