Migrate from Zymplify to Freshsales

Zymplify Contact records include standard fields (name, email, phone, job title, company association) plus enrichment provenance from intent data sources. We map these to Freshsales Contact with typed fields preserved directly. Any intent signal metadata attached at the contact level (contact-level intent scores from Bombora) is carried as a custom Contact field for reference but does not activate any Freshsales automation. Enrichment source attribution migrates as a text field on the Contact record.

Company records are Zymplify's primary anchor for intent data. All 20+ intent signals (Bombora intent spikes, G2 Buyer Intent, website visit intent) attach to the Company record. We map Zymplify Companies to Freshsales Accounts 1:1, with intent signal metadata carried as custom Account fields. Bombora intent scores, G2 intent signal sources, and intent spike timestamps are preserved as custom fields on the Account so enrichment provenance is available for manual prioritization even though Freshsales does not natively surface this data.

Zymplify Deals map to Freshsales Deal with a 1:1 stage mapping. Zymplify's customisable pipeline stages are preserved as-is in Freshsales Deal Stage values. Deal value, expected close date, and owner assignment migrate directly. We recommend creating Freshsales Deal custom fields for Zymplify's Closed-Lost reason and Closed-Won reason if those custom properties exist in the source schema.

Zymplify Sales Cadences are outreach sequences combining email steps, delays, and task actions. Freshsales Sequences (available at Growth and Pro tier) provide email sequence functionality but do not natively support the full cadence model with task integration that Zymplify uses. We export cadence structure as a sequence definition document listing every step, delay, condition, and action, then create equivalent Freshsales Sequences where the tier supports it. Any cadence step that references Zymplify-specific triggers (intent-based activation) is flagged for manual rebuild as a Freshsales Automation.

Zymplify Marketing Workflows are automation builders with triggers, conditions, and actions across the Marketing Hub. Freshsales Automations (Pro and above) provide record-triggered and time-based automations but use a different trigger-action model. We do not migrate workflows as code. We document every active Zymplify workflow with its trigger type, conditions, action sequence, and intended outcome as a requirements specification, so the customer's admin can rebuild equivalents in Freshsales Automations. Any workflow that relies on Bombora or G2 intent data as a trigger is flagged as requiring a manual redesign.

Zymplify's Research Quadrant segments accounts into four phases (Initial, Interested, Active, In-Depth) representing where each account is in the buying journey. Freshsales has no native equivalent. We create a Research_Quadrant__c picklist field on the Account object with the four Zymplify values and carry the current stage for each account. This field does not trigger any Freshsales automation natively; the customer's admin can use it for manual prioritisation or add it as a filter in Freshsales Views and Reports.

Zymplify's customer health scores and churn risk indicators are Zymplify-native calculations combining engagement, product usage, and support ticket signals. Freshsales does not have a dedicated CS module. We extract the raw health signals (engagement frequency, support interaction count, contract health indicators) as custom fields on the Account record and flag that the scoring model itself does not migrate. If the customer also uses Freshdesk, we can scope a parallel engagement to connect Freshdesk ticket data to the Account as an enrichment source for manual health assessment.

Zymplify custom fields exist across all object types but the export schema is not publicly documented. We discover the full custom field inventory during the discovery phase, including field types and picklist values, then create equivalent custom fields in Freshsales before migration. Tags applied to Contacts and Companies are exported as a comma-separated custom field on the respective object, with a recommendation to rebuild the tagging taxonomy using Freshsales Labels and Views rather than relying on a flat tag string for filtering.