Act-On to HubSpot migration
Moving from Act-On to HubSpot addresses a core complaint from Act-On users: the platform's limited CRM depth compared to HubSpot's integrated Sales, Marketing, and Service Hubs. FlitStack AI maps Act-On contacts, companies, opportunities, and custom fields into HubSpot's property model — preserving original create dates, stage history, and owner assignments while handling Act-On's secondary-contact and activity associations correctly in HubSpot's association graph.
FlitStack AI migrates contacts, companies, deals, engagements and custom properties from Act-On to HubSpot, 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: 48–72 hours for under 50,000 records.

What moves from Act-On to HubSpot?
Act-On positions itself as a marketing-automation-forward platform where CRM functionality sits alongside email campaigns, lead scoring, and nurture programs.
Read the full summary
HubSpot inverts that priority — its CRM core sits at the center, with optional Marketing, Sales, and Service Hubs layered around it. This architectural difference shapes every migration decision. FlitStack AI extracts Act-On data via its REST API, pulling contacts, companies, opportunities, activities (calls, emails, meetings, notes), and custom field schemas. We map Act-On's contact-first model to HubSpot's unified contact property system, translating Act-On opportunity stages into HubSpot deal pipeline stages and preserving any custom data objects as HubSpot custom properties. Owner resolution matches Act-On user emails to HubSpot user emails. Activity history — call logs, email records, meeting notes — migrates into HubSpot's engagement timeline with original timestamps and owners intact. What does not migrate: Act-On marketing automation workflows, email templates, lead scoring rules, and CRM configuration settings. Those are rebuilt in HubSpot using our exported definitions as reference. Reports and dashboards do not transfer — the underlying data does, but the reporting constructs are destination-side schema. Integrations to third-party tools must be reconnected manually after go-live.
Contact → Contact
Act-On contacts map directly to HubSpot contacts.
How it maps
The primary company association becomes HubSpot's primary company association. Act-On secondary contacts (assistants, business partners listed on a contact record) require HubSpot association labels — we create these as labeled associations on the contact record.
Company → Company
Act-On companies map directly to HubSpot companies.
How it maps
Standard fields such as address (street, city, state, postal code, country), industry, employee count, annual revenue, phone, and website transfer without transformation. Parent/child company hierarchies in Act-On are preserved by mapping the parent reference to HubSpot's parent company property, maintaining the same relational structure across the two platforms.
Opportunity → Deal
Act-On opportunities map to HubSpot deals.
How it maps
Each Act-On opportunity stage becomes a HubSpot deal pipeline stage. The deal amount, close date, owner, and associated contact(s) transfer directly. HubSpot supports multiple pipelines — each Act-On opportunity group can map to its own HubSpot pipeline.
Activity — Call → Engagement (Call logged)
Act-On call logs become HubSpot engagements of type call.
How it maps
The original call duration, direction (inbound/outbound), outcome (completed, missed, voicemail), notes, and timestamp are preserved as HubSpot call metadata on the contact's engagement timeline. HubSpot's call‑logging fields (hs_call_direction, hs_call_duration_milliseconds, hs_call_status) capture each data point, ensuring the full call record is intact after migration.
Activity — Email → Engagement (Email logged)
Act-On email records migrate as HubSpot email engagements on the contact record.
How it maps
Subject, body, and timestamp transfer. The email association to the contact record is preserved. Act-On email templates (used for sends) do not migrate — we export them as HTML for rebuild reference.
Activity — Meeting / Calendar → Engagement (Meeting logged)
Act-On meeting records are imported as HubSpot meeting engagements, preserving the start and end timestamps, title, location, and owner.
How it maps
The meeting notes, attendee list, and any linked resources become HubSpot meeting metadata (hs_meeting_title, hs_meeting_start_time, hs_meeting_end_time, hs_meeting_location, hs_meeting_outcome). Associated contacts are relinked using HubSpot's association graph, ensuring the meeting appears on the correct contact and company records.
- ContactContact1:1
- CompanyCompany1:1
- OpportunityDeal1:1
- Activity — CallEngagement1:1
- Activity — EmailEngagement1:1
- Activity — MeetingEngagement1:1
+ 4 more in the mapping below
How Act-On and HubSpot 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 | HubSpot |
|---|---|---|
| Contact model | Act-On stores contacts with a primary company link plus optional secondary contacts per record. | HubSpot uses a flat contact record with no concept of a primary/secondary distinction — all associations are label-keyed. |
| Deals / Opportunities | Act-On opportunities track stage, amount, close date, and owner. Pipeline stages are per-setup pick-list values. | HubSpot deals sit inside named pipelines with stages, amounts, close dates, and owners. Each pipeline is an independent object in HubSpot. |
| Marketing automation | Act-On includes built-in email campaigns, lead scoring, and nurture programs as core functionality. | HubSpot Marketing Hub handles campaigns separately from CRM contacts. Marketing-automation logic must be rebuilt post-migration. |
| Custom fields | Act-On custom data schemas use the API endpoint /custom-objects/v1/{accountId}/schema/{objectId}/field with field-level API naming. | HubSpot custom properties use a property-name string (e.g., custom_property) and do not require __c suffix — they coexist with standard properties. |
| Activity history | Act-On tracks activities (calls, emails, meetings, notes) linked to contacts or companies. Export includes timestamps and user IDs. | HubSpot engagement timeline stores each activity as a timestamped event on the contact record with type and owner metadata. |
| Pricing model | Act-On pricing is based on active contact count — scales with total contacts stored in the account. | HubSpot CRM is free at base tier; paid hubs (Sales, Marketing, Service) scale by feature tier and seat count, not total contact volume. |
Act-On to HubSpot field mapping
The 30 most-used fields of 37 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.
-
FirstNameContactfirstnameContact -
LastNameContactlastnameContact -
EmailContactemailContact -
PhoneContactphoneContact -
MobilePhoneContactmobilephoneContact
| Act-On field | HubSpot field | Mapping | Note |
|---|---|---|---|
Contact.FirstName | Contact.firstname | direct | |
Contact.LastName | Contact.lastname | direct | |
Contact.Email | Contact.email | direct | |
Contact.Phone | Contact.phone | direct | |
Contact.MobilePhone | Contact.mobilephone | direct | |
Contact.Title | Contact.jobtitle | direct | |
Contact.Address | Contact.address | direct | |
Contact.City | Contact.city | direct | |
Contact.State | Contact.state | direct | |
Contact.PostalCode | Contact.zip | direct | |
Contact.Country | Contact.country | direct | |
Contact.LeadSource | Contact.hs_analytics_source | transformed | Act-On lead source values map to HubSpot's analytics source property. Custom lead source values become custom property options in HubSpot. |
Contact.Status | Contact.lifecyclestage | value_mapping | Act-On prospect status (New, Working, Nurturing, Qualified, Converted) maps to HubSpot lifecycle stage via value-by-value mapping. Converted maps to customer. |
Contact.CreateDate | Contact.original_create_date__c | custom_field_required | HubSpot's createdate is set at import time. Original Act-On create date is preserved as a custom date property for reporting continuity. |
Contact.LastUpdatedDate | Contact.notes_last_updated | direct | |
Contact.PrimaryCompanyID | Contact.associatedcompanyid | transformed | Act-On's primary company reference requires the HubSpot company record to exist first. Companies are migrated before contacts to resolve this foreign key correctly. |
Company.CompanyName | Company.name | direct | |
Company.Website | Company.website | direct | |
Company.Industry | Company.industry | value_mapping | Industry pick-list values are mapped by exact name match. Act-On values with no HubSpot counterpart become custom property options. |
Company.NumberOfEmployees | Company.numberofemployees | direct | |
Company.AnnualRevenue | Company.annualrevenue | direct | |
Company.Phone | Company.phone | direct | |
Company.Address | Company.address | direct | |
Company.ParentCompanyID | Company.parent_id | transformed | Act-On parent/child company hierarchy maps to HubSpot's parent company field. Parent companies are migrated first to resolve the reference without circular dependency errors. |
Opportunity.OpportunityName | Deal.dealname | direct | |
Opportunity.Amount | Deal.amount | direct | |
Opportunity.Stage | Deal.dealstage | value_mapping | Act-On opportunity stage values map to HubSpot deal stage values by name. Each pipeline in Act-On maps to a corresponding HubSpot pipeline. Probability values are re-applied based on HubSpot stage settings. |
Opportunity.CloseDate | Deal.closedate | direct | |
Opportunity.OwnerID | Deal.hubspot_owner_id | transformed | Act-On opportunity owner is resolved by email match to a HubSpot user. Unmatched owners are flagged and assigned to a designated fallback owner before migration. |
Opportunity.Probability | Deal.hs_deal_stage_probability | direct |
What to watch for in a Act-On to HubSpot migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Act-On secondary-contact structure has no native HubSpot equivalent
Act-On lets you list secondary contacts — assistants, business partners, dependents — directly on a primary contact record.
How we handle it
HubSpot has no parallel structure; all contacts exist as independent records in the same contact database. FlitStack maps Act-On secondary contacts as separate HubSpot contact records and links them to the primary contact using HubSpot association labels. Your team should verify whether the secondary contact relationship needs to be visible in HubSpot's UI or whether it can be represented as a note.
Marketing automation and lead scoring do not transfer to HubSpot
Act-On's marketing automation workflows, lead scoring models, email sequences, and nurture programs are built inside Act-On's automation engine.
How we handle it
HubSpot's workflow automation lives in a separate module with different rule syntax, trigger conditions, and action types. FlitStack exports Act-On workflow definitions as structured documentation for your HubSpot admin to rebuild. The logic — trigger criteria, time delays, branch conditions — is preserved in text form, but the automation itself must be reconstructed in HubSpot's workflow builder.
Act-On's custom data schemas require manual HubSpot property creation
Act-On custom data schemas are defined via the /custom-objects/v1/{accountId}/schema/{objectId}/field API endpoint, allowing per-field type definitions including pick-lists, multi-select fields, and numeric ranges.
How we handle it
HubSpot custom properties must be created manually in HubSpot's property settings before import. FlitStack generates a property creation checklist based on the Act-On schema export, but HubSpot's property creation UI requires manual steps (naming, type selection, option list entry) that cannot be fully automated. Plan for a property-setup session before the migration run.
HubSpot's marketing contact billing model differs from Act-On's active-contact model
Act-On bills based on total active contacts stored in the account.
How we handle it
HubSpot Marketing Hub adds a separate marketing contact billing model where only contacts flagged as marketing contacts count toward billing in Marketing Hub tiers. FlitStack preserves Act-On contact records as standard HubSpot contacts — your HubSpot admin controls the marketing contact flag in HubSpot's settings. This is a billing configuration decision, not a migration data issue, but it is important to set correctly before scaling marketing campaigns in HubSpot.
Activity export volume can exceed HubSpot's engagement timeline display limits
Act-On accounts with long history accumulate high volumes of call logs, email records, and meeting notes per contact.
How we handle it
HubSpot's engagement timeline displays all logged activities in reverse chronological order. Accounts with more than 5 years of dense activity history per record may produce cluttered timelines in HubSpot. FlitStack offers an optional date-range filter for activity migration — for example, migrating the last 2 years of activity in full and archiving older records as a custom note on the contact.
How the migration runs
Audit Act-On data inventory and extract via API
FlitStack connects to your Act-On account via API (OAuth 2.0) to inventory all contacts, companies, opportunities, activities, and custom data schemas.
What this step covers
We document record counts, field names, custom schema definitions, and owner assignments before writing any migration plan. This step also identifies data quality issues — duplicate contacts, missing required fields, or malformed values — that need cleaning before import into HubSpot.
Design HubSpot property schema and create custom properties
Based on the Act-On inventory, FlitStack produces a HubSpot property creation checklist: standard fields that already exist in HubSpot, custom properties that need to be created, pick-list value mappings for status fields, and data type conversions (date formats, numeric precision).
What this step covers
Your HubSpot admin creates the properties from this checklist before migration data is loaded. We provide field-level instructions for each custom property including the exact name, type, and option values.
Resolve owner records and map pipeline stages
Act-On user emails are matched to HubSpot user emails for owner resolution.
What this step covers
Any Act-On owner without a HubSpot user account is flagged with the specific email address so your team can either invite the user to HubSpot or designate a fallback owner. Act-On opportunity pipeline stages are mapped to HubSpot deal pipeline stages, with stage probability values re-applied per HubSpot's pipeline configuration. If multiple Act-On pipelines exist, each maps to its own HubSpot pipeline.
Run sample migration with field-level diff
A representative subset — typically 100–500 records spanning contacts, companies, deals, and activities — migrates first.
What this step covers
FlitStack generates a field-level diff comparing source Act-On values against the migrated HubSpot records so you can verify that pick-list mappings, date formats, owner resolution, and association links are correct before the full run. You approve the sample before we commit to the full dataset.
Execute full migration with delta-pickup and rollback plan
The full migration runs against HubSpot's API, loading contacts, companies, deals, and activities in the correct sequence to resolve foreign keys.
What this step covers
A delta-pickup window of 24–48 hours captures any records created or modified in Act-On during the cutover period. FlitStack maintains an audit log of every record written. If reconciliation fails, one-click rollback reverts the HubSpot account to its pre-migration state so the migration can be re-run after corrections.
- 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
Act-On to HubSpot migrations price scales with three drivers: record volume (contacts, companies, opportunities), the number of Act-On custom data schemas and fields that need HubSpot custom property creation, and whether Act-On multi-company contact associations require HubSpot's secondary-association labeling. FlitStack AI provides a fixed quote after reviewing the Act-On account's field inventory and record counts. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Act-On to HubSpot →Why teams move from Act-On to HubSpot
- Act-On users consistently report that CRM depth lags behind HubSpot — particularly around contact property management, deal pipeline customization, and reporting visibility. Multiple G2 reviewers note that Act-On works well for marketing automation but leaves sales teams wanting more robust pipeline tracking, which HubSpot's Sales Hub delivers natively.
- Reddit threads from small SaaS companies that previously used ACT!-derived platforms (the same product family as Act‑On) describe outgrowing contact‑centric CRM models and needing HubSpot's association graph, deal pipelines, and reporting tools to support team growth beyond five to ten reps. These users highlight the friction of maintaining separate systems for contacts and sales activity.
- HubSpot's all-in-one platform appeal reduces the stack complexity that Act-On-only setups create. Teams moving from Act-On to HubSpot consolidate marketing emails, CRM, and sales engagement into one natively integrated environment rather than managing Act-On alongside separate CRM and email tools.
- Act-On's pricing model based on active contact count becomes expensive at scale, particularly for teams with large historical databases. HubSpot's free CRM base plus tiered hub pricing offers better cost predictability for growing teams, a theme echoed in Capterra reviews for Act-On competitors.
Questions, answered
Act-On to HubSpot migration questions
How long does an Act-On to HubSpot migration take?
Most Act-On to HubSpot migrations complete in 48–72 hours for accounts with fewer than 50,000 records. Accounts exceeding 500,000 records or containing complex multi-schema custom data extend the timeline to 5–10 days. The longest planning step is typically HubSpot custom property creation, which your admin handles before the migration run. Activity history volume (5+ years of dense call and email logs) also extends processing time.
Will my Act-On marketing automation workflows migrate to HubSpot?
No. Act-On workflows, lead scoring rules, email sequences, and nurture programs do not migrate — they must be rebuilt in HubSpot's workflow automation module. FlitStack exports your Act-On workflow definitions as structured documentation including trigger conditions, branch logic, and time-delay steps so your HubSpot admin has a rebuild reference. The automation logic is preserved in documentation form; the active rules themselves require manual reconstruction in HubSpot's workflow builder.
What happens to Act-On prospect status and lead scores in HubSpot?
Act-On prospect status values (New, Working, Nurturing, Qualified, Converted) map to HubSpot lifecycle stage via value-by-value mapping. Converted in Act-On becomes Customer in HubSpot. Any Act-On lead scoring model is not a native HubSpot concept — FlitStack migrates the numeric score as a custom property on the HubSpot contact record. Your team then decides whether to use HubSpot's built-in contact scoring or rebuild a custom model.
Can I migrate Act-On custom data schemas to HubSpot?
Yes. Act-On custom data schemas defined via the /custom-objects/v1/{accountId}/schema/{objectId}/field API endpoint map to HubSpot custom properties. Each Act-On schema field becomes a HubSpot property of the matching type. Before migration, your HubSpot admin must create these properties manually in HubSpot's property settings — FlitStack provides the exact property name, type, and option list for each field. Multi-select picklists in Act-On map to HubSpot multi-checkbox properties.
What happens to Act-On secondary contacts listed on a primary contact record?
Act-On allows you to attach secondary contacts (assistants, business partners) directly to a primary contact record. HubSpot has no native secondary-contact concept — all contacts exist as independent records. FlitStack creates separate HubSpot contact records for each Act-On secondary contact and links them to the primary contact using HubSpot association labels. You can view these relationships in HubSpot's contact record via the associations section. Verify whether visibility of this relationship is needed for your team's workflow.
Does the migration affect my Act-On account during cutover?
No. FlitStack uses read-only API access to your Act-On account — your team continues working in Act-On during the migration. A delta-pickup window of 24–48 hours captures any records created or modified in Act-On between the initial export and the go-live date. After the delta window closes, no new records are written to Act-On. The HubSpot account is the destination; Act-On remains fully operational until you choose to cancel the account.
Will my Act-On reports and dashboards transfer to HubSpot?
Reports and dashboards are destination-side schema and do not migrate. The underlying data — contact records, deal amounts, activity history — migrates completely, so your HubSpot reports can be rebuilt from the same data. Act-On report definitions and chart configurations are not exportable in a form that HubSpot can import. FlitStack documents the key metrics from your Act-On reports (record counts by stage, activity totals, pipeline values) so your HubSpot admin knows which numbers to replicate in HubSpot's reporting module.
Related migrations
HubSpot implementation
Set up HubSpot and migrate into it as one engagement.
See the service → HoneyBook to HubSpotMapping · history · rollbackfolk to HubSpotMapping · history · rollbackBitrix24 to HubSpotMapping · history · rollbackActiveCampaign to HubSpotMapping · history · rollbackGoldMine to HubSpotMapping · history · rollbackSugarcrm to HubSpotMapping · history · rollback Act-On to Zoho CRMMapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
- Understand property field types in HubSpot
- Associate records on CRM objects — HubSpot Knowledge Base
- Integration throughput and limits — HubSpot Knowledge Base
- HubSpot Cloud Infrastructure and Data Hosting FAQ
Get a quote
Moving from Act-On to HubSpot?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.
Get a quote