Act-On to Zoho CRM migration
We migrate Contacts, Companies, Deals, and Activity history from Act-On into Zoho CRM with engagement scores preserved as static custom fields, List membership mapped to Zoho Tags, and Custom Data schema fields translated to Zoho custom fields before any record is written to the destination.
FlitStack AI migrates contacts, accounts, deals, tags and blueprints from Act-On to Zoho CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Act-On to Zoho CRM?
Moving from Act-On to Zoho CRM is a migration from a marketing automation platform into a full CRM system, which means the data model shifts.
Read the full summary
Act-On organizes around Contacts, Companies, and automated Programs; Zoho CRM adds Leads, Accounts, Contacts, and Opportunities as separate modules with explicit relationship rules. We extract data from Act-On via its REST API using Bearer JWT authentication, export List membership and engagement score values as static properties, and write into Zoho via its CSV import with custom fields pre-provisioned for Act-On's custom data schema extensions. Programs (nurture workflows) and engagement score formulas do not export; we document Program structure as a reference blueprint and preserve score values numerically for Zoho admin to rebuild scoring logic. Activity history (email opens, clicks, form submissions) migrates as timestamped Activity records linked to the Contact.
Contact → Contact
Act-On Contacts map directly to Zoho CRM Contacts.
How it maps
Standard fields (first name, last name, email, phone, mobile) pass through cleanly. We preserve lifecycle stage in a custom field contact_lifecycle_stage__c and the original Act-On contact ID in a reference field acton_id__c for audit and re-sync purposes.
Company → Account
Act-On Companies map to Zoho CRM Accounts.
How it maps
Company name becomes Account Name; domain becomes Website. We use the Act-On Company record as the primary Account parent before importing Contacts so that the Account-Contact lookup is satisfied at the moment of Contact insert.
Deal → Deal
Act-On Deals map to Zoho CRM Deals if the destination Zoho instance has the Deals module enabled (available from Professional tier).
How it maps
Deal name, amount, stage, expected close date, and owner migrate directly. We configure the Zoho Deals pipeline with stage values matching the Act-On deal stages before migration.
List → Tag
Act-On Lists are audience segments used for campaign targeting.
How it maps
We preserve List membership as comma-separated Tag values on the Contact record. For List membership relevant to segmentation, we also create Zoho CRM Segments referencing the tag values so that reports and workflows can filter by the original List name. Dynamic vs static List logic does not transfer and is documented for the customer's marketing ops team to reconfigure in Zoho.
Program (Automated Workflow) → Blueprint (reference document)
Act-On Programs define multi-step nurture sequences stored server-side and inaccessible via API.
How it maps
We export Program membership data (which contacts entered each Program, entry date, branch taken, and exit status) as a reference log. We deliver a written Program Blueprint documenting the sequence steps, decision branches, and wait durations so the customer's Zoho admin rebuilds the logic using Zoho Workflow Rules, Blueprint, or a third-party marketing automation tool.
Email → Activity (Email)
Act-On email send history (subject, body, HTML, send date, open and click timestamps) migrates as Zoho CRM Activity records of type Email linked to the Contact.
How it maps
Email content migrates to the Activity notes or description field; open and click events migrate as separate activity records with a campaign reference. HTML templates do not migrate as reusable templates.
- ContactContact1:1
- CompanyAccount1:1
- DealDeal1:1
- ListTagtransformed
- ProgramBlueprintpartial
- EmailActivity1:1
+ 5 more in the mapping below
How Act-On and Zoho CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Act-On | Zoho CRM |
|---|---|---|
| Platform type | Marketing automation SaaS centred on Contacts, Companies, and Programs | Full CRM with Accounts, Contacts, Leads, Opportunities, and marketing modules |
| Contact-to-Company relationship | Contacts linked to a Company record; no separate Account object | Contacts linked to Accounts; separate Leads object for unqualified prospects |
| Engagement scoring | Native behavioural score calculated from opens, clicks, page visits, and form submissions | No native scoring; requires custom field plus Zoho Analytics or third-party add-on |
| Audience segmentation | Lists (dynamic or static) and Program membership for campaign targeting | Tags, Segments, and Zoho CRM's Blueprint for workflow state management |
| Custom objects | Custom Data Schema via API with user-defined field types | Custom fields on standard modules plus custom modules via the Extensions framework |
| Pricing model | Per-seat with tier-based contact volume caps that drive cost as lists grow | Per-user from $14/user/mo; includes workflow automation and AI (Zia) at all paid tiers |
| Built-in SMS | Native SMS integration without a third-party subscription | SMS via Zoho SMS Add-on or third-party integration; not bundled in standard CRM plans |
Act-On to Zoho CRM field mapping
The 30 most-used fields of 31 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
firstnameContactFirst NameContact -
lastnameContactLast NameContact -
emailContactEmailContact -
phoneContactPhoneContact -
mobilephoneContactMobileContact
| Act-On field | Zoho CRM field | Mapping | Note |
|---|---|---|---|
Contact.firstname | Contact.First Name | direct | Pass through; Zoho enforces 50 character limit on First Name. |
Contact.lastname | Contact.Last Name | direct | Required field; Zoho enforces 50 character limit. Trim whitespace. |
Contact.email | Contact.Email | direct | Lowercase and trim. Used as dedupe key in Zoho. Zoho enforces valid email format on import. |
Contact.phone | Contact.Phone | direct | Strip non-numeric characters if the destination Zoho instance uses E.164 formatting; otherwise pass through as-is. |
Contact.mobilephone | Contact.Mobile | direct | Phone format follows the same rule as Phone. |
Contact.jobtitle | Contact.Title | direct | Zoho Title field limit is 100 characters; truncate with audit flag if exceeded. |
Contact.acton_lifecycle_stage | Contact.contact_lifecycle_stage__c | transform | Act-On lifecycle stage values preserved verbatim in a custom field. No direct Zoho equivalent; this field is informational for the customer's marketing ops team. |
Contact.acton_engagement_score | Contact.acton_engagement_score__c | transform | Numeric score migrated as integer. Act-On scoring formula is not transferable; Zoho admin rebuilds scoring via Zia rules or Zoho Analytics post-migration. |
Contact.acton_created_date | Contact.acton_original_created_date__c | direct | Act-On record creation timestamp stored as a custom field because Zoho Contact Created Date is set by the system during import, not by the migrating record. |
Contact.emailoptout | Contact.Opted Out of Email (inverse) | transform | Act-On opt-in boolean is inverted: opt-in true maps to Zoho Opted Out of Email false. Opt-in false maps to Opted Out true. |
Contact.acton_owner_email | Contact.Contact Owner | lookup | Resolved by email match against Zoho CRM Users table. Unresolved owners parked for admin reconciliation before Contact import. |
Account.name | Account.Account Name | direct | Zoho Account Name limit is 150 characters. |
Account.domain | Account.Website | direct | Prefix https:// if the Act-On value lacks a scheme. Used as a secondary dedupe key alongside Account Name. |
Account.industry | Account.Industry | transform | Act-On freeform industry strings normalize to Zoho Industry picklist values where possible. Values without a picklist match route to Other and the original text moves to acton_industry_text__c. |
Account.numberofemployees | Account.Employees | direct | Integer; both fields support integer values. |
Account.annualrevenue | Account.Annual Revenue | direct | Currency field; confirm the source Act-On deal currency matches the Zoho org's default currency before migration. |
Account.billing_address_street | Account.Billing Street | direct | Act-On's single street field maps to Zoho's multi-line Billing Street. Line breaks preserved. |
Account.billing_address_city | Account.Billing City | direct | Pass through. |
Account.billing_address_state | Account.Billing State | direct | Validate against Zoho's State and Country picklists if enabled in the destination org. |
Account.billing_address_postal_code | Account.Billing Code | direct | Pass through; Zoho accepts alphanumeric postal codes. |
Account.billing_address_country | Account.Billing Country | direct | Country picklist validation applies if State and Country picklists are enabled in Zoho. |
Deal.dealname | Deal.Deal Name | direct | Zoho Deal Name limit is 100 characters. |
Deal.amount | Deal.Deal Value | direct | Currency field; ensure currency alignment with Zoho org default before import. |
Deal.dealstage | Deal.Stage | transform | Act-On deal stage names map to Zoho Deal Stage picklist values configured during schema setup. We align the stage name strings to the customer's approved Zoho pipeline stage matrix. |
Deal.expectedclosedate | Deal.Closing Date | direct | ISO date format; both systems use date fields without time components. |
Deal.acton_owner_email | Deal.Deal Owner | lookup | Resolved by email match against Zoho CRM Users table. |
Activity.activity_type | Activity.acton_event_type__c | direct | Email open, click, form submission, and page visit event types stored in a custom field so the customer's admin can segment activity by type in Zoho reports. |
Activity.activity_timestamp | Activity.Date | direct | Original Act-On timestamp preserved in the Zoho Activity Date field for timeline accuracy. |
Activity.subject | Activity.Subject | direct | For email-related activities, subject line passes through. For form submissions, a generated subject string including form name is created. |
Activity.body | Activity.Description | direct | Activity body text (email body, form field values) migrates to Zoho Activity Description. |
What to watch for in a Act-On to Zoho CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
ACT! desktop CRM and Act-On are different products
A common confusion in migration discussions conflates ACT!
How we handle it
(a desktop/cloud CRM by Swiftpage, now part of Sage) with Act-On (a separate marketing automation SaaS from Portland, Oregon). These have different data models, different APIs, and different export paths. Act-On exposes Contacts, Companies, Custom Objects, Programs, and engagement scores via REST API with Bearer JWT authentication; ACT! uses a proprietary .PAD file format or MS SQL database. We confirm the exact product name and subdomain during discovery. Mixing them up leads to a failed or corrupt migration. Pair evidence shows Zoho's own migration documentation targets ACT! CRM specifically, not Act-On, which confirms the distinction.
Act-On Program logic and engagement score formulas do not export
Act-On's Automated Programs define multi-step nurture sequences stored server-side with branching rules, wait durations, and CRM actions.
How we handle it
Neither the Program definitions nor the engagement score weighting formula are accessible via API. We export Program membership data (which contacts entered, entry date, branch taken, exit status) as a reference log and migrate engagement scores as static numeric values on each Contact. Zoho Blueprint and Workflow Rules must be used to rebuild Program logic post-migration, and scoring formulas must be reconfigured by the customer's Zoho admin.
Act-On Custom Data schema fields require manual field type mapping
Act-On's Custom Data schemas define user-created fields with types (text, number, date, picklist).
How we handle it
Zoho CRM custom fields must be pre-provisioned with equivalent types before any data loads, and picklist values in Act-On must be matched to Zoho picklist values or routed to a free-text custom field. We audit the Custom Data schema during discovery, recommend field type choices in Zoho, and provision the fields via Zoho's Setup before any Contact or Company import begins. Skipping this step results in type-mismatch rejections during import.
List membership as static tags does not preserve dynamic List logic
Act-On Lists can be dynamic (populated by filter rules) or static (manually added).
How we handle it
We migrate List membership as Zoho Tags on each Contact, which preserves the record of which lists a contact was in at migration time. Dynamic List filter rules do not transfer. The customer's Zoho admin must re-create dynamic segmentation logic using Zoho CRM's Filters, Segments, or a marketing automation tool. For contacts that should have been in a dynamic List based on their migrated field values, we deliver a reconciliation report listing contacts that meet the criteria so the admin can bulk-add them.
Zoho API has per-day record limits that affect large activity migrations
Zoho CRM's API enforces daily record creation limits that vary by edition (Standard tier: 10,000 records/day for the entire org).
How we handle it
Act-On accounts with large activity histories (email opens, clicks, form submissions spanning years) can exceed this quickly. We handle large activity sets by chunking by date range, batching requests, and applying exponential backoff on 429 responses. Large migrations with over 200,000 activity records extend the timeline accordingly but do not block completion.
How the migration runs
Discovery and schema audit
We audit the source Act-On instance across all enabled objects: Contact count, Company count, Deal count, List names and sizes, Custom Data schema definitions (field names, types, picklist values), Program names and member counts, and activity history volume by type and date range.
What this step covers
We identify records with missing required fields (contacts without last name, companies without name) and flag them for the customer's data owner to correct before migration. We also confirm that the destination Zoho CRM edition (Standard, Professional, Enterprise) supports the required custom fields and the Deals module.
Zoho schema provisioning and field mapping
We pre-provision all custom fields in Zoho CRM before any data loads.
What this step covers
This includes custom fields on Contact (acton_id__c, contact_lifecycle_stage__c, acton_engagement_score__c, acton_original_created_date__c), custom fields on Account (acton_industry_text__c, acton_id__c), and custom fields on Activity (acton_event_type__c). We configure Zoho picklists to match Act-On picklist values where possible and set up the Deals pipeline with stage values aligned to the customer's Act-On deal stages. Schema is provisioned in the destination Zoho instance before the migration begins.
Owner and Account-Contact dependency resolution
We extract every distinct Act-On owner referenced on Contact, Company, and Deal records and match by email against the Zoho CRM Users table.
What this step covers
Any Act-On owner without a matching Zoho User goes to a reconciliation queue for the customer's Zoho admin to provision. We build the Account-Contact dependency tree: every Act-On Company is inserted as a Zoho Account first, so that the Account-Contact lookup is satisfied when Contacts are imported. Contacts without a matching Company are inserted with a null Account-Contact lookup and flagged for the customer's admin to manually associate.
Sandbox import and reconciliation
We run a full migration into a Zoho Sandbox or staging environment using production-like data volume.
What this step covers
The customer's Zoho admin reconciles record counts (Accounts in, Contacts in, Deals in, Activities in), spot-checks 25-50 records against the Act-On source, and validates that custom field values arrived correctly. Any field mapping corrections are made in the transformation logic before production migration. Activity volume is validated against Act-On export totals.
Production migration in dependency order
We run production migration in dependency order: Accounts (from Act-On Companies) first, then Contacts with Account-Contact lookups resolved, then Deals, then Activity records chunked by date range.
What this step covers
List membership is applied as Tags after Contacts are inserted. Custom Data schema field values are loaded in the same phase as their parent object. Each phase emits a row-count reconciliation report before the next phase begins. We apply exponential backoff on Zoho API 429 responses and retry failed records up to three times before flagging for manual review.
Cutover, validation, and Program rebuild handoff
We freeze Act-On writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho CRM as the system of record.
What this step covers
We deliver the Program Blueprint document (Program names, sequence steps, branch logic, and wait durations extracted from Act-On), the engagement score reference values list, and the dynamic List reconciliation report. We do not rebuild Act-On Programs as Zoho Blueprint or Workflow Rules inside the migration scope; that is a separate engagement or an internal admin task. We support a one-week hypercare window for reconciliation issues raised by the customer's team.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and the volume of activity history to chunk and load. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Act-On to Zoho CRM →Why teams move from Act-On to Zoho CRM
- Teams moving from Act-On need pipeline management that a marketing automation platform does not provide. Act-On centres on Contacts, Companies, and Programs but has no native Opportunity, Deal, or forecasting module. Zoho CRM delivers Accounts, Contacts, Leads, Opportunities with stage-based pipelines, quote generation, and sales forecasting out of the box, replacing the patchwork of spreadsheets and third-party CRMs that Act-On users typically layer on as companies scale.
- Act-On pricing becomes difficult to justify as contact volumes grow and tier limitations bite. Reviewers on G2 and Capterra cite pricing as a driver for leaving Act-On. Zoho CRM's per-user model at $14-$23/user/mo is more predictable for sales and marketing teams, and Zoho One ($54/user/mo for 50+ applications) bundles CRM, email marketing, projects, and analytics under a single subscription, reducing the total stack cost for teams previously paying for Act-On plus a separate CRM.
- Companies outgrow Act-On's reporting depth. Multi-touch attribution, revenue reporting by pipeline stage, and territory-based analysis require tooling beyond Act-On's built-in dashboards. Zoho CRM's native analytics, combined with Zoho Analytics ($12/row/month), delivers pipeline reports, sales forecasting, and custom dashboards without exporting to a data warehouse. Reviewers moving from comparable mid-market marketing tools to Zoho cite reporting as a primary driver.
- Act-On's Programs (multi-step nurture sequences) and engagement score formulas do not export, which limits continuity for marketing-ops teams relying on automated nurture. Zoho's Blueprint and Workflow Rules provide native automation at all paid tiers, and while Program logic must be rebuilt, the existing Act-On Program data (which contacts entered, when, what branch they took) migrates as a reference blueprint for the rebuild.
- Mid-market teams consolidate onto Zoho One to eliminate tool sprawl. Act-On teams typically pair it with a separate CRM, a separate project tool, and separate analytics. Zoho One at $54/user/mo includes CRM, email campaigns, projects, Desk (support), Forms, and Analytics, replacing four to six separate subscriptions. MondoCRM notes Zoho's ecosystem integration as a structural advantage over older Act-tier platforms that require third-party add-ons for equivalent coverage.
Questions, answered
Act-On to Zoho CRM migration questions
How long does an Act-On to Zoho CRM migration take?
Basic migrations under 10,000 Contacts with no Custom Data schema extensions complete in three to five weeks. Migrations with extensive custom fields, large activity histories (over 200,000 event records), or List membership across hundreds of segments extend to six to nine weeks because of schema pre-provisioning, sandbox validation, and activity chunking. Act-On does not expose a bulk export endpoint, so large dataset extraction adds time relative to platforms with dedicated bulk APIs.
Do Act-On Programs, Workflows, and engagement score formulas migrate to Zoho?
No. Act-On Programs (multi-step nurture sequences) and the engagement score weighting formula are not accessible via API and cannot be exported. We export Program membership data (which contacts entered each Program, when, and what branch they took) as a reference log and migrate engagement scores as static numeric values in a custom field on each Contact. We deliver a written Program Blueprint documenting the sequence steps, branches, and wait durations so your Zoho admin rebuilds the logic using Zoho Workflow Rules and Blueprint. Engagement score recalculation requires a new Zia rule or Zoho Analytics scoring model, which your Zoho admin configures post-migration.
Can we migrate historical engagement data like email opens and clicks from Act-On?
Yes, we migrate Act-On engagement history as Zoho CRM Activity records linked to the Contact. Email opens, clicks, form submissions, and page visits migrate as timestamped Activities with the event type stored in a custom field. The volume of activity history can be significant; we chunk by date range and process in batches to stay within Zoho's API daily limits. Note that the original Act-On engagement score formula does not apply to the migrated history, so the raw event data represents what happened but not how Act-On weighted it.
How does List membership transfer to Zoho CRM?
Act-On List membership migrates as Zoho CRM Tags on each Contact record. For contacts in multiple Lists, we create multiple Tags. Dynamic List logic (rules that auto-populate a List based on contact properties) does not transfer; we deliver a reconciliation report listing all contacts that meet each dynamic List's criteria so your Zoho admin can re-create the segmentation using Zoho Filters or Segments. Static Lists transfer as Tags with no additional reconfiguration required.
What happens to Act-On Forms after migration?
Act-On web form definitions (field labels, field types, conditional logic) and form submission data migrate to Zoho CRM. The Act-On embed code does not transfer and must be re-implemented using Zoho Forms or an embedded Zoho Experience Builder form. Form field definitions map to Zoho custom fields on the Contact module; submission data appears as field values on the individual Contact records. If you already have an Act-On-Zoho integration capturing form submissions, we reconcile migrated records against the integration data to prevent duplicates.
Do we lose any data migrating from Act-On to Zoho CRM?
Record-level data (Contacts, Companies, Deals, Activities, Custom Data) migrates without loss when the Act-On source data is clean and the migration is executed in dependency order. What does not transfer: Program workflow definitions (rebuilt using the blueprint we deliver), engagement score weighting formulas (scores migrate as numbers, formula logic does not), and dynamic List rules (List membership migrates as Tags, rules require manual rebuild). We run pre-migration validation to identify records with missing required fields and flag them for correction before the migration begins, preventing data loss from incomplete records.
What Zoho CRM edition do we need for this migration?
Standard tier ($14/user/mo) covers Contacts, Accounts, Leads, Deals, custom fields, and basic Workflow Rules. Professional ($23/user/mo) is recommended if the migration includes the Deals module with pipeline stages, Blueprint for process automation, or advanced reporting. Enterprise adds territory management, Zoho AI (Zia) for scoring and anomaly detection, and larger API rate limits. We confirm the appropriate edition during discovery based on the migration scope and advise on upgrading if the scope expands post-migration.
Related migrations
Zoho CRM implementation
Set up Zoho CRM and migrate into it as one engagement.
See the service → Attio to Zoho CRMMapping · history · rollbackHomesnap Pro to Zoho CRMMapping · history · rollbackSugarcrm to Zoho CRMMapping · history · rollbackHoneyBook to Zoho CRMMapping · history · rollbackZendesk Sell to Zoho CRMMapping · history · rollbackJobber to Zoho CRMMapping · history · rollback Act-On to HubSpotMapping · history · rollbackGet a quote
Moving from Act-On to Zoho CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Zoho CRM setup with you, then send a quote.
Get a quote