Skip to content
Get a quote

Act! to HubSpot migration

We migrate Contacts, Companies, Groups, Opportunities, and the full Activity + History timeline from Act! into HubSpot — using the Act! Web API for Cloud tenants or direct SQL Server extraction for Desktop installs, and re-creating Act! Groups as static or active HubSpot Lists before cutover.

Short answer

FlitStack AI migrates contacts, companies, static lists, active lists and deals from Act! 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: 3-5 weeks.

By

Source Act!
DestinationHubSpot
ContactCompanyStatic ListActive ListDeal
Mapped field by field · sample run · one-click rollback

What moves from Act! to HubSpot?

Moving from Act! to HubSpot is a deployment-model decision before it's a data-model one.

Read the full summary

Act! Premium Cloud and Act! Premium Desktop are sold under the same brand but expose data through different paths — Cloud uses the Act! Web API (OAuth 2.0, REST), Desktop typically uses direct SQL Server SELECT against the Act! database. We identify the deployment model during scoping, then extract Contacts (Act!'s primary record) into HubSpot Contacts, attach Companies as Organization parents, and re-create Act! Groups as HubSpot Lists (static groups → static lists, dynamic groups → active lists with translated filter criteria). Opportunities and their Products map to HubSpot Deals with Line Items. The Activity + History timeline — every call, meeting, to-do, and logged interaction since the customer first opened Act! — migrates into HubSpot's engagement timeline so the salesperson opens HubSpot on day one with a contact's history intact. Act! Custom Tables (v18+) require HubSpot Enterprise to map cleanly as Custom Objects; on Professional, they migrate as serialized JSON notes attached to the parent Contact.

1:1

Contact → Contact

Act! Contact records map 1:1 to HubSpot Contacts.

How it maps

We preserve standard fields (Name, Title, Email, Phone, Address) and migrate every populated custom field — including the long tail of legacy fields accumulated across Act! versions. Email is the HubSpot dedupe key; Act! records without an email go to a reconciliation queue and either migrate as no-email Contacts or get merged into the destination's parent Company record per customer decision.

1:1

Company → Company

Act! Company records map to HubSpot Companies.

How it maps

Act! tenants that skipped Companies (very common in small-firm Act! installations) get derived Companies created from Contact.Company_Name fields, with deduplication on normalized domain. The Contact → Company association migrates explicitly so HubSpot's Account Manager view renders correctly.

1:1

Secondary Contact → Contact (with primary-contact custom property)

Act! Secondary Contacts (assistants, spouses, alternative decision-makers linked to a primary Contact) migrate as standalone HubSpot Contacts with a 'Primary Contact' custom property pointing back to the parent Contact's HubSpot record ID.

How it maps

This preserves the relationship without duplicating engagement history.

1:1

Group (Static) → Static List

Act! Static Groups (manually maintained membership) map to HubSpot Static Lists.

How it maps

We export the Group's contact membership set and create the destination List with matching members resolved by email. Group descriptions migrate as the List description.

configuration

Group (Dynamic) → Active List

Act! Dynamic Groups use rule-based criteria (e.g., 'all Contacts where Industry = Manufacturing').

How it maps

We capture the Act! query and translate to HubSpot Active List filter criteria. Some Act! query operators (regex, complex date math) don't translate 1:1; those rules get rewritten with the customer's sign-off and the original query saved as a description for audit.

1:1

Opportunity → Deal

Act! Opportunities map to HubSpot Deals.

How it maps

Standard fields (name, value, stage, weighted forecast, close date, status) map directly. Stage names are Act!-tenant-specific and require a stage mapping table built during scoping — typically customers want to consolidate or rename Act! stages while migrating, so we treat stage mapping as a deliberate decision rather than an auto-translation.

What moves13 objects
Act!HubSpot
  • ContactContact1:1
  • CompanyCompany1:1
  • Secondary ContactContact1:1
  • GroupStatic List1:1
  • GroupActive Listtransformed
  • OpportunityDeal1:1

+ 7 more in the mapping below

How Act! 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.

DimensionAct!HubSpot
Deployment modelCloud SaaS or on-premise Windows/SQL Server (Desktop)Cloud-only SaaS — no on-prem option
Primary recordContact is the center of the universe; Company optionalContact + Company are both first-class, with HubSpot Account Manager linking them
SegmentationStatic and Dynamic Groups defined per tenantStatic Lists and Active Lists with re-usable filter criteria
Custom objectsCustom Tables available in Premium v18+, schema-free per tenantEnterprise tier ($150/seat/mo + onboarding) gates Custom Objects
Marketing automationAct! Marketing Automation as paid add-on (~$79/mo+)Marketing Hub as a separate tier with Marketing Contacts pricing
Pricing modelPer-user (~$30/mo Cloud) or perpetual license (Desktop)Per-seat with Marketing Contacts metering on the marketing layer
Integration ecosystemLow double-digit native integrationsApp Marketplace with ~1,700 listings

Act! to HubSpot field mapping

The 19 most-used fields of 19 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.

Field mapping5 shown
Act!HubSpot
  1. ContactContact firstname + lastnameContact
  2. CompanyContact companyContact
  3. TitleContact jobtitleContact
  4. E-mailContact emailContact
  5. Phone (Business / Mobile / Home)Contact phone / mobilephone / homephoneContact
Act! fieldHubSpot fieldMappingNote
Contact.ContactContact.firstname + lastnamesplitAct! stores Contact as a single field. We split on the last space character into firstname/lastname; suffixes (Jr., III) move to lastname.
Contact.CompanyContact.companydirectPass through and use as the dedupe key for the implicit Company association.
Contact.TitleContact.jobtitledirectPass through.
Contact.E-mailContact.emaildirectLowercase; HubSpot's primary dedupe key. Records with missing email route to reconciliation.
Contact.Phone (Business / Mobile / Home)Contact.phone / mobilephone / homephonedirectEach Act! phone field maps to its HubSpot counterpart. Numbers are normalized to E.164 where possible.
Contact.Address (1/2/3) + City + State + ZIP + CountryContact.address + city + state + zip + countrydirectMulti-line Act! address concatenates with comma separation into HubSpot's single address field.
Contact.ID/StatusContact.lifecyclestagemappingAct! tenant-specific ID/Status values map to HubSpot Lifecycle Stage via a translation table built during scoping (e.g., Prospect → subscriber, Active Customer → customer).
Contact.Referred ByContact.hs_analytics_sourcedirectPreserved as the analytics source label.
Contact.Last Edited / Edit DateContact.lastmodifieddatedirectCarries over; HubSpot also stamps its own modification date on import.
Company.CompanyCompany.namedirectRequired. Used with normalized website domain as dedupe key.
Company.Web SiteCompany.domaindirectNormalized — strip protocol and trailing slash. Primary dedupe key for HubSpot Companies.
Opportunity.NameDeal.dealnamedirectPass through; 256-character limit applies.
Opportunity.Total / Weighted TotalDeal.amountdirectTotal maps to amount; weighted total preserved as a custom property if the customer uses Act!'s probability-weighted forecasting.
Opportunity.StageDeal.dealstagemappingAct! stage names → HubSpot pipeline stage internal IDs via a translation table. Stage probability also maps if the customer wants HubSpot's forecast view to match Act!.
Opportunity.Estimated Close DateDeal.closedatedirectISO date pass-through.
Activity.Date / Time / DurationEngagement.hs_timestamp / hs_meeting_start_time / hs_meeting_durationdirectType-dependent: Calls use hs_call_duration, Meetings use start/end times, Tasks use due date.
Activity.SubjectEngagement.hs_meeting_title / hs_call_title / hs_task_subjectdirectEngagement-type-specific title field.
Activity.DetailsEngagement.hs_meeting_body / hs_call_body / hs_task_bodydirectRich-text content; RTF converted to HTML for HubSpot engagement bodies.
Note.Note Date / Note Text / Created ByNote (engagement).hs_timestamp / hs_note_body / hubspot_owner_iddirectOwner resolves via email match against HubSpot Users; falls back to the migration service user if unmatched.

What to watch for in a Act! to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Act! Desktop and Cloud need different extraction paths

Act! Premium Desktop databases live on the customer's Windows + SQL Server and the Web API is optional (and often not installed in older deployments).

How we handle it

Act! Premium Cloud is API-only. We confirm the deployment model during scoping and either get database read access for Desktop or OAuth credentials for Cloud — the migration playbook is genuinely different. Customers running both (typical of teams that bought Cloud as an evaluation) require two extraction passes that we reconcile against a single target HubSpot portal.

high

Custom Tables only map cleanly to HubSpot Enterprise

Act! Custom Tables (v18+) are tenant-defined object types — Policies, Properties, Cases, Loans — with arbitrary fields.

How we handle it

They map 1:1 to HubSpot Custom Objects, which are gated to HubSpot Enterprise ($150/seat/month plus ~$3,500 onboarding). On HubSpot Professional or below, Custom Table rows serialize as JSON notes attached to the parent Contact, which preserves data but loses queryability. We surface this tier-implication during scoping so customers can decide whether the Custom Table data justifies the Enterprise tier upgrade.

medium

Recurring Activity Series explode without an active window

Act! Activity Series (e.g., a weekly 1:1 scheduled for the past 5 years) expand to thousands of occurrences when materialized.

How we handle it

HubSpot doesn't have a native recurring-task primitive that matches Act!'s, so we either expand the series within an agreed active window (next 12 months + last 24 months historical) or migrate the rule as a single custom property and let HubSpot Calendar re-create the series. Skipping this conversation produces a migration where one rep has 8,000 historical Tasks and HubSpot lookups slow to a crawl.

medium

Act! Group dynamic-query operators don't all translate to HubSpot Lists

Act! Dynamic Groups support query operators (regex, complex date math, contains-any-of-list) that HubSpot Active Lists don't all support natively.

How we handle it

We translate the supported subset cleanly and rewrite the rest with the customer's sign-off — usually breaking one Act! Group into multiple HubSpot Lists, or substituting a less-strict filter with the original query saved as the list description for audit.

medium

Act! Marketing Automation engagement history lives in a separate database

Act! Marketing Automation (AMA) is a separate hosted product with its own database — email opens, clicks, and bounce records do not live in the main Act! database.

How we handle it

If the customer wants HubSpot to inherit AMA engagement history (last_open, last_click, total_sends), we extract from the AMA API and map these as custom HubSpot Contact properties. Without this step, HubSpot starts engagement scoring from zero on day one.

How the migration runs

  1. Discovery + deployment confirmation

    We identify Act! Cloud vs Desktop, capture the SQL Server connection (Desktop) or OAuth credentials (Cloud), inventory the Contact custom fields actually populated, list all Group definitions (static + dynamic), enumerate Custom Tables (if any), and measure the Document library size.

    What this step covers

    The output is a written scope with record counts per object and a deployment-specific extraction plan.

  2. HubSpot pre-flight

    We pre-create the HubSpot pipeline, deal stages, Lifecycle Stage values, custom properties for every populated Act! custom field, Custom Objects (Enterprise) or note-template structure (Professional) for Act!

    What this step covers

    Custom Tables, and a Product catalog matching the Act! Opportunity Product master list. Owners get pre-provisioned so deals and contacts land on the right rep at import.

  3. Sample migration + customer review

    We migrate a representative slice — typically 200 Contacts, 50 Companies, 30 Opportunities with Line Items, 100 Activities, and 500 History items spanning two reps.

    What this step covers

    The customer reviews mapping fidelity, stage translation accuracy, and ownership assignment before we commit to the full run.

  4. Full extraction

    Bulk extraction from Act! (API paginated or SQL chunked), staged in our migration database.

    What this step covers

    We download Documents in parallel, expand Activity Series into the agreed active window, and pre-compute Group memberships for List re-creation.

  5. Full load + validation

    Bulk load into HubSpot via the Batch API for Contacts, Companies, Deals, and Engagements.

    What this step covers

    Documents upload to Files API and link to parents. After load completes, we run a field-level hash diff between source and destination and surface any miss to the customer for review before declaring cutover.

  6. Cutover + Act! decommission plan

    On the agreed cutover date, we re-extract any records modified since the bulk load (delta sync), close the source migration user, and hand the customer a decommission checklist for Act! — covering license cancellation, SQL Server backup archival (Desktop), and AMA subscription wind-down.

Act! HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
8-12 weeksLarge or heavily customised accounts

Pricing depends on the deployment model (Cloud vs Desktop), Custom Table presence, and document volume. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Act! to HubSpot →

Why teams move from Act! to HubSpot

  • Act! teams move to HubSpot to escape on-premise IT overhead. Act! Premium Desktop's Windows Server, SQL Server, and IIS stack requires customer-managed patching, backups, and disaster recovery — costs that quietly compound year over year. HubSpot eliminates the entire infrastructure surface and bundles uptime, security, and upgrades into the subscription, freeing the IT team to do work that's not 'keep the CRM server alive'.
  • Marketing-driven sales teams find Act!'s integration ecosystem too narrow. Act! ships with around a dozen native integrations and a thin Zapier surface, while HubSpot's App Marketplace lists roughly 1,700 connectors covering Slack, Zoom, Stripe, Shopify, and every common SaaS tool. Teams that want their CRM plugged into their broader stack switch to HubSpot for the integration breadth alone.
  • Built-in HubSpot reporting and the Reports Library replace Act!'s 'export to Excel and pivot' workflow. Modern sales managers expect interactive dashboards with deal velocity, pipeline coverage, and rep activity rolled up live — HubSpot ships these out of the box where Act! treats reporting as a static template engine.
  • Teams adopting HubSpot for the freemium entry point find it pulls double duty as both the CRM and the marketing automation tool, replacing both Act! and Act! Marketing Automation. A small business running Act! Premium Cloud + Act! Marketing Automation pays roughly $110/user/month combined; HubSpot Starter Bundle costs $20–$30/user/month with comparable feature coverage for SMB workflows.
  • HubSpot's modern UI and mobile experience reduce onboarding friction for new hires. Act!'s interface has a long, dated lineage; sales reps new to a company report ramping faster on HubSpot because the metaphors (deal pipeline, contact timeline, task queue) are now industry-standard and the help docs reflect a current product, not a decade of accumulated UI generations.

Questions, answered

Act! to HubSpot migration questions

Do you support both Act! Premium Cloud and Act! Premium Desktop?

Yes. Cloud uses the Act! Web API; Desktop typically uses direct SQL Server read access against the Act! database. We confirm which deployment you're on during the scoping call and adjust the extraction approach. Customers running both (e.g., Cloud for sales reps, Desktop for power-user admins) get a two-pass extraction reconciled into one HubSpot portal.

Will my Act! Custom Tables migrate to HubSpot?

Yes, but the destination depends on your HubSpot tier. On HubSpot Enterprise, Custom Tables map 1:1 to HubSpot Custom Objects. On Professional and below, Custom Object support isn't available, so we serialize Custom Table rows as JSON notes attached to the parent Contact — data is preserved but not queryable. We surface this trade-off during scoping so you can decide whether the data justifies Enterprise tier.

What happens to recurring Activities (e.g., weekly client check-ins)?

We expand the Activity Series within an active window you choose — typically the next 12 months forward plus the last 24 months historical — and store the underlying recurrence rule as a custom property on the parent record. HubSpot doesn't have a native recurring-task primitive that matches Act!'s, so any future-dated recurrence beyond the active window gets re-created in HubSpot Calendar manually if you want it.

Will my Act! Marketing Automation campaign history migrate?

Campaign performance data lives in a separate AMA database. We extract via the AMA API and roll up engagement signals (last open, last click, total sends, bounce status) as HubSpot Contact properties so your HubSpot scoring starts from a known baseline rather than zero. Per-send detail is exported as a CSV archive rather than re-created as live records in HubSpot.

How are Act! Groups mapped to HubSpot?

Static Groups (manual membership) → HubSpot Static Lists. Dynamic Groups (rule-based) → HubSpot Active Lists with the Act! query translated to HubSpot filter criteria. Some Act! query operators (regex, complex date math) don't translate 1:1 and get rewritten with your sign-off — typically by splitting one Act! Group into multiple HubSpot Lists or relaxing a filter and noting the original query in the list description.

Can I keep Act! running during the migration window?

Yes. We extract via read-only API calls (Cloud) or read-only SQL queries (Desktop) so production Act! operations are unaffected. Sales reps continue working in Act! through cutover. On the cutover date we run a delta sync to capture anything modified since the bulk extraction, then formally switch the team to HubSpot. Act! stays online in read-only mode for a customer-defined period (typically 30–90 days) as a safety net.

Get a quote

Moving from Act! 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