Some features no longer exist in Zoho Campaigns 3.0. This article lists them by what happens to your past data when you move from the current version, which Zoho calls Zoho Campaigns 2.0. It is based on Zoho's "What's changed and what's deprecated" guide, updated on 16 October 2026 with clarifications from Zoho on scoring, syncs, and campaign types. For features that still exist but behave differently, read What's Changed in Zoho Campaigns 3.0, and for the migration steps read Prerequisites for Migrating to Zoho Campaigns 3.0.
| Status | What it means |
|---|---|
| Deprecated | No longer available in 3.0. Past data is migrated. |
| Deprecated, past data not migrated | No longer available, and nothing is migrated. |
| Partially migrated | Some of it is migrated and some is not. |
Zoho Campaigns has three types of scoring, and the migration behaviour differs for each. Record your current configuration before migrating.
| Scoring type | What happens, as Zoho has confirmed |
|---|---|
| Engagement scoring | Existing engagement scores migrate seamlessly. |
| Custom scoring (custom rules) | Rules with multiple conditions using AND or OR operators are not migrated. Rules with a single condition can be migrated. You can build similar rules in Channel Based Scoring. |
| Field-based scoring | Existing field-based scoring migrates as Fit Score. |
| Campaign-based scoring | Deprecated in the Email Campaigns module. Use the Response Action component to assign additional scores based on responses to specific campaigns. |
New archive campaigns cannot be created. Existing archive code keeps running, so a public archive already embedded on a website continues to work.
Zoho has confirmed that 3.0 supports two campaign types, Regular and RSS. These were separate campaign types in the older version and are not types in 3.0: Zoho Meeting, GoToWebinar, Eventbrite, SurveyMonkey, Zoho Survey, Zoho Backstage, Ecommerce, Zoho Forms, and Child campaigns. Past campaigns of these types are migrated and listed as Regular campaigns. Find them by filtering on the component each one used. The same use cases are handled inside a regular email campaign with merge tags for survey links, event links, and other contextual information.
Existing dormant campaigns are migrated as Regular campaigns. New ones cannot be created.
Three automation types are deprecated:
All three are brought into 3.0 and appear under their own tabs within Workflows. Selecting one opens it in the older version in a new tab, where it stays editable. They cannot be cloned, and you cannot create new ones of these types. You can rebuild an autoresponder or classic workflow as a 3.0 Workflow, with behavioural changes. Zoho's guide to workflow equivalents gives the closest match for each component and automation type.
Both are still shown after migration under Settings, then Integrations, then Webhooks, tagged Old Version beside the date they were created and who created them. They keep working. Two things differ if you recreate one in 3.0:
A webhook already set to GET is migrated and keeps working, listed as Active with GET in the Request Method column. GET is not available when creating a new webhook, so the supported methods going forward are POST, PUT, and DELETE.
The Google Analytics integration is not available in 3.0. Campaign traffic is tracked with UTM parameters instead. In the new Settings, under Tracking and Sending Limits, you can switch on UTM parameter tracking so UTM parameters are appended automatically to links in email, WhatsApp, and SMS campaigns.
These three integrations do not exist in 3.0 and nothing replaces them. Export whatever you need from the source app before migrating.
Zoho has confirmed that only syncs built on a custom view in a connected app are removed during migration. Data syncs for modules such as Contacts, Leads, and custom modules migrate seamlessly. A custom view sync's configuration cannot be read afterwards, so note what each one pulls before migrating, then rebuild it using the Import from Custom View option or a segment.
New bulk segments cannot be created in 3.0. Existing ones are migrated with the parent condition only. Child conditions are not migrated, so a migrated bulk segment returns more contacts than it used to.
Example from Zoho. A bulk segment based on the field Country, with Additional Criteria of Company Name is Zylker, produced one child segment per country in the older version, each filtered to Zylker. After migration it becomes a single segment with two criteria groups: Group 1 is Country isn't empty, Group 2 is Company Name is equal to any of Zylker, joined as G1 AND G2. The Additional Criteria are kept as Group 2, but the per-country split is lost. There is now one segment covering every contact with any country, which is why it reaches a wider audience.
To narrow it back down, exclude values you do not want at send time. While configuring the campaign, choose the bulk segment as recipients, open Exclude Contacts, select the Advanced tab, and build a group such as Country is not equal to any of Sri Lanka. That removes those contacts and leaves the rest as the audience.
There is no Coupon campaign creation flow in 3.0 and no equivalent campaign type. Sent campaigns are migrated and listed in the list view. Drafts are not migrated, so save their content first. A migrated coupon campaign can be cloned, and the clone is a Regular campaign whose content and details can be edited, but with no option to configure coupons.
Sent campaigns are migrated as Regular campaigns. Drafts are not migrated. The forms-embedded configuration does not carry over and has to be set up again.
Drafts containing the ICS component are migrated and their content can be edited. The component itself cannot be edited or copied manually, though the draft can be cloned, and no new email campaign can be created with the component. To include a calendar invite in a new campaign, attach the ICS file to the email.