CRM migration

Migrate from Act! to Nutshell

Field-level mapping, validation, and rollback between Act! and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Act! logo

Act!

Source

Nutshell

Destination

Nutshell logo

Compatibility

85%

11 of 13

objects map 1:1 between Act! and Nutshell.

Complexity

BStandard

Timeline

3-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Nutshell is a no-nonsense SMB CRM designed as a Pipedrive/Insightly alternative — straightforward pipelines, contact-centric data model, and email-tracking core. The migration from Act! is one of the smoother routes because Nutshell's data model maps almost directly: Act! Contacts → Nutshell People, Companies → Nutshell Companies, Opportunities → Nutshell Leads (Nutshell uses the term 'Lead' for both qualified opportunities and unqualified prospects), Activities → Nutshell Activities. The interesting work is around Nutshell's Pipeline model — Pipelines in Nutshell are top-level constructs with their own stage sets, so Act! tenants with multiple Opportunity types map to multiple Nutshell Pipelines designed during scoping. Custom fields, tags, and Activity types pre-create before record load. Activity History migrates to Nutshell Activities (closed status) with timestamp preservation via Nutshell's API audit-bypass flag.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Act! logo

Act!

What's pushing teams away

  • Dated UI and on-premise legacy feel — long-time Act! Desktop users describe the experience as 'Office 2007-era' compared to modern cloud CRMs, and the upgrade path between major versions historically requires reinstalling and re-syncing data.
  • Limited modern integration ecosystem — Act!'s Zapier and native integration count is in the low double digits, where HubSpot, Salesforce, and Pipedrive all measure integrations in the thousands.
  • Act! Premium Desktop's reliance on SQL Server, IIS, and Windows Server makes IT maintenance an ongoing cost — patching, backups, and disaster recovery fall on the customer's IT team rather than the vendor.
  • Team collaboration features lag modern CRMs — Act!'s historical strength is the individual contact owner, and shared pipelines, real-time activity feeds, and built-in chat are weaker than HubSpot, Pipedrive, or monday.
  • Reporting is functional but inflexible — most users export to Excel rather than build inside Act!, where modern CRMs ship dashboards, pivot charts, and embedded BI as core features.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Act! objects map to Nutshell

Each row shows how a Act! object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Act!

Contact

maps to

Nutshell

Person

1:1
Fully supported

Act! Contacts map to Nutshell People. Email is the dedupe key.

Act!

Company

maps to

Nutshell

Company

1:1
Fully supported

Act! Companies map to Nutshell Companies with Person → Company association preserved.

Act!

Opportunity

maps to

Nutshell

Lead

1:1
Fully supported

Act! Opportunities map to Nutshell Leads. Pipeline assignment based on tenant's Opportunity type. Stage values from translation table.

Act!

Opportunity Product

maps to

Nutshell

Lead Product

1:1
Fully supported

Act! Opportunity line items map to Nutshell Lead Products with quantity, unit price, and discount preserved.

Act!

Activity (Meeting)

maps to

Nutshell

Activity (type: Meeting)

1:1
Fully supported

Nutshell Activity type set during pre-flight per tenant Activity classification.

Act!

Activity (Call)

maps to

Nutshell

Activity (type: Phone Call)

1:1
Fully supported

Direction (inbound/outbound) and duration preserved.

Act!

Activity (To-do)

maps to

Nutshell

Activity (type: Task)

1:1
Fully supported

Due date, assignee, status preserved.

Act!

History

maps to

Nutshell

Activity (closed)

1:1
Fully supported

Completed History items map to closed Nutshell Activities with original timestamp preserved via audit-bypass flag.

Act!

Note

maps to

Nutshell

Note

1:1
Fully supported

Act! Notes attach to People/Companies/Leads with original author and timestamp preserved.

Act!

Group (Static)

maps to

Nutshell

Tag

1:1
Fully supported

Act! Static Groups become Nutshell Tags applied to member People/Companies.

Act!

Group (Dynamic)

maps to

Nutshell

Saved Filter

lossy
Fully supported

Dynamic Group criteria translate to Nutshell Saved Filters with condition rewrites where Act! operators don't have Nutshell equivalents.

Act!

Custom Table

maps to

Nutshell

Custom fields on People/Companies or JSON note

lossy
Fully supported

Nutshell doesn't have Custom Objects. Custom Table data migrates as additional custom fields on the parent People/Companies record (for small-cardinality tables) or as JSON notes (for higher-volume tables).

Act!

Document

maps to

Nutshell

Attachment

1:1
Fully supported

Act! Documents upload as Nutshell attachments on the parent record. Storage included in subscription for typical Act!-migration volumes.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Act! logo

Act! gotchas

High

Act! Premium Desktop and Cloud use different export paths and cannot share a single migration script

High

Act! Custom Tables (v18+) have no standardized schema across customers

Medium

Activity Series (recurring activities) explode into thousands of occurrences

Medium

Act! Marketing Automation campaign history is in a separate database

Low

Act! contact layouts can hide fields without dropping them from the schema

Low

Document attachments in Act! Desktop are file-system pointers, not blobs

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Nutshell has no native Custom Objects

    Act! Custom Tables don't have a direct Nutshell equivalent. We migrate Custom Table data as additional custom fields on the parent People/Companies record (for small tables with low cardinality) or as JSON notes (for larger tables). Customers with significant Custom Table usage should consider a destination with native Custom Object support (Zoho, HubSpot Enterprise, Salesforce).

  • Multiple Pipelines need to be designed before load

    Nutshell Pipelines are top-level constructs with their own stage sets. Act! tenants running multiple Opportunity types (e.g., New Business vs Renewals) typically want each as a separate Pipeline. Pipeline structure and stage values designed during pre-flight.

  • Lead terminology overload

    Nutshell uses 'Lead' for both unqualified prospects and qualified opportunities (unlike Salesforce/Dynamics where these are separate objects). Act! Opportunities map to Nutshell Leads, not to a separate object. We confirm the terminology during scoping to avoid confusion.

  • Activity timestamps require audit-bypass on insert

    By default Nutshell stamps the import time. To preserve Act!'s original Activity timestamps, we use Nutshell's API audit-bypass flag (or admin-level import mode) so the destination timeline reads correctly.

  • Deployment model selection

    Cloud (Web API) vs Desktop (SQL Server) — same as all Act! migrations.

Migration approach

Six steps for a successful Act! to Nutshell data migration

  1. Discovery + Pipeline design

    Confirm deployment, inventory custom fields/Groups/Custom Tables/Documents, design Nutshell Pipeline + Stage structure per Act! Opportunity types.

  2. Nutshell pre-flight

    Create Pipelines + Stages, Activity Types, Tags for Act! Groups, custom fields on People/Companies. Pre-create Products for Lead Products.

  3. Sample + customer review

    200 People, 50 Companies, 30 Leads with Products, 100 Activities, 500 History items. Customer reviews mapping fidelity.

  4. Full extraction + Document download

    Bulk Act! extraction. Documents prepared.

  5. Full load via Nutshell REST API

    Companies → People → Leads + Products → Activities → Notes → Documents. Field-level diff.

  6. Cutover + decommission

    Delta sync on cutover. Reps switch to Nutshell. Act! read-only for safety window.

Platform deep dives

Context on both ends of the pair

Act! logo

Act!

Source

Strengths

  • Deep, mature contact-management feature set: layouts, custom fields, secondary contacts, and relationship-tracking refined over 35+ years of releases.
  • Available as on-premise (Act! Premium Desktop) for teams that require local data residency — most modern CRMs are cloud-only.
  • Per-user pricing is predictable and competitive with mid-market CRMs for SMB use cases without integration complexity.
  • Strong fit for relationship-driven verticals: financial advisors, accountants, insurance brokers, real-estate, legal — workflows where the contact record is the center of the universe.
  • Built-in Act! Marketing Automation add-on covers basic email marketing without needing a separate Mailchimp/Constant Contact subscription.

Weaknesses

  • Dated UI and on-premise legacy architecture — the look and feel hasn't kept pace with modern cloud CRMs.
  • Small integration ecosystem (low double digits of pre-built integrations) versus thousands on HubSpot/Salesforce/Pipedrive.
  • Act! Premium Desktop requires customer-managed Windows Server, SQL Server, and IIS — ongoing IT overhead.
  • Team-collaboration and real-time-feed features lag behind modern collaborative CRMs.
  • Reporting is rigid — most teams export to Excel rather than build dashboards inside Act!
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Act! and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Act!: Not publicly documented for Cloud; Desktop is limited only by the customer's SQL Server and IIS capacity.

  • Data volume sensitivity

    B

    Act! doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Act! to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Act! to Nutshell data migrations

Answers to the questions buyers ask most during Act! to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Act! to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Nutshell doesn't have native Custom Objects, so Custom Table data migrates either as additional custom fields on the parent People/Companies record (small tables, low cardinality) or as JSON notes (higher-volume tables). If Custom Tables are central to your Act! workflow, consider Zoho CRM, HubSpot Enterprise, or Salesforce — those have native Custom Object support.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Act!.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day