This guide maps each component and automation type from the current version to its closest match in Zoho Campaigns 3.0, and notes where behavior differs.
These components exist in Workflows built in the current version and are migrated into the Zoho Campaigns 3.0 builder.
Purchase Follow-up and Abandoned Cart triggers are migrated as they are. In 3.0 both support product selection and additional criteria.
Field Update Trigger is migrated as it is. In 3.0, it supports Deals and Accounts fields.
Three-way Split becomes Multi-way Split, which supports more than three branches.
A/B Test stops being a standalone component. Use Send Email with A/B Testing enabled instead, so what was a component becomes an email-level setting.
Webhook is mostly migrated as it is. A webhook using GET alone is skipped for now.
Starting with version 3.0, the GET webhook component is deprecated; while it will continue to function, only POST, PUT, and DELETE options will be available for editing, and switching to these methods will make reverting to GET impossible.
All seven autoresponder types are deprecated. Each one is migrated and opens in the older version in a new tab, where it stays editable. To continue developing one, rebuild it as a 3.0 Workflow using the structure below.
Sign-up: Rebuild as an Added to List trigger with Send Mail and Time Delay components. Converted into a Workflow structure with no change in behavior.
Date-field: Rebuild as a Date Field trigger with Send Mail and Time Delay components. Converted into a Workflow structure with no change in behavior.
Closed Group: Rebuild as an Added to List trigger with the existing contact option, plus Send Mail and Time Delay components. Map the existing contact handling across yourself, because it does not translate directly.
Email Action: Rebuild as an Email Action trigger with Check Email Activity and the configured emails. Follow-up actions are modeled through activity checks rather than as their own step.
Calendar and Cyclic: Rebuild as several Workflows, using Date-based triggers for Calendar and Cyclic triggers for Cyclic. An autoresponder containing multiple series becomes as a separate workflow for each series, so reporting is split across them. A single report covering the whole sequence is no longer available, so plan how you will measure performance before rebuilding.
Smart Series: No equivalent yet. It opens in the older version with a banner. Archive link support needs further analysis.
Conditional Workflows behave differently depending on the type.
Activity-based is the only type migrated automatically as a 3.0 Workflow. The activity condition becomes the matching 3.0 trigger, built as an Open trigger with the configured actions.
Instant and Time-based are not migrated as Workflows. They open in the older version for backward compatibility and keep running there, so rebuild them only if you want to keep developing them. Rebuild an Instant Workflow using segment or list targeting with the configured actions, which turns criteria-based targeting into a reusable segment. Rebuild a Time-based Workflow using a Date Field trigger with the configured actions, which handles date, time, and any additional conditions inside the trigger.
Workflows using score components: These may be paused after migration depending on the license. Check each one and reactivate where needed.
Workflows using deprecated contact fields: A Workflow built on list added time, opt in type, consent status, last sent on, or average amount spent is paused after migration. You can edit the workflow and replace the component if needed.
Workflows connected to signup forms: A contact who signed up while the Workflow was mid-migration may not have received the campaign it would normally trigger. Check the entries and retarget those contacts with a different campaign or Workflow if needed.