CRM migration
Field-level mapping, validation, and rollback between Act! and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Act!
Source
Freshsales
Destination
Compatibility
12 of 14
objects map 1:1 between Act! and Freshsales.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Freshsales is Freshworks' CRM, often paired with Freshdesk and Freshcaller for a full customer-platform suite. The migration path from Act! is well-trodden because both products target SMB-to-mid-market and have similar object models: Contacts → Contacts, Companies → Accounts, Opportunities → Deals, Activities → Tasks/Meetings/Calls. The interesting work is around Freddy AI configuration and Sales Sequences. Freddy AI scores leads and predicts deal outcomes based on engagement signals — Act! migration provides the engagement-history rollups (last open, last click, total touches) that bootstrap Freddy's scoring model. Sales Sequences (Freshsales' email cadence feature) replaces Act! Marketing Automation drip campaigns for outbound sales motion; we capture AMA workflow definitions during migration for re-creation in Freshsales.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Act! object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Act!
Contact
Freshsales
Contact
1:1Act! Contacts map to Freshsales Contacts. Email is dedupe key. Account_id resolves to the Freshsales Account.
Act!
Contact (unqualified)
Freshsales
Lead (optional)
1:1Optional: Freshsales supports a separate Lead object. Act! Contacts without Opportunity history can migrate as Leads if customer uses the Lead → Contact conversion workflow.
Act!
Company
Freshsales
Account
1:1Act! Companies map to Freshsales Accounts. Parent-child hierarchy preserved.
Act!
Opportunity
Freshsales
Deal
1:1Act! Opportunities map to Freshsales Deals. Pipeline + Stage from translation table. Probability preserved.
Act!
Opportunity Product
Freshsales
Product (in Deal Products)
1:1Pre-create Products as a master catalog; attach to Deals via Deal Products.
Act!
Activity (Meeting)
Freshsales
Appointment
1:1Start/end times, location, attendees preserved.
Act!
Activity (Call)
Freshsales
Phone Call
1:1Duration and direction preserved.
Act!
Activity (To-do)
Freshsales
Task
1:1Due date and priority preserved.
Act!
History
Freshsales
Activity (closed) or Note
1:1Completed History items map to closed Activities or Notes with original timestamp preserved via Freshsales API audit-bypass.
Act!
Group (Static)
Freshsales
List / Tag
1:1Static Groups map to Freshsales Lists (segmentation) or Tags (cross-cutting attributes) depending on use.
Act!
Group (Dynamic)
Freshsales
Smart View / Saved Filter
lossyDynamic Groups translate to Smart Views with filter criteria.
Act!
Custom Table
Freshsales
Custom Module (Enterprise)
lossyAct! Custom Tables map to Freshsales Custom Modules. Available from Enterprise tier ($59/user/month). Lower tiers receive Custom Table data as JSON notes.
Act!
Document
Freshsales
Attachment
1:1Documents upload as Freshsales Attachments on parent records.
Act!
AMA Audience / Workflow
Freshsales
Sales Sequence
1:1Act! Marketing Automation drip workflows re-create as Freshsales Sales Sequences during cutover. Audience definitions become Sequence target lists.
| Act! | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Contact (unqualified) | Lead (optional)1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Opportunity Product | Product (in Deal Products)1:1 | Fully supported | |
| Activity (Meeting) | Appointment1:1 | Fully supported | |
| Activity (Call) | Phone Call1:1 | Fully supported | |
| Activity (To-do) | Task1:1 | Fully supported | |
| History | Activity (closed) or Note1:1 | Fully supported | |
| Group (Static) | List / Tag1:1 | Fully supported | |
| Group (Dynamic) | Smart View / Saved Filterlossy | Fully supported | |
| Custom Table | Custom Module (Enterprise)lossy | Fully supported | |
| Document | Attachment1:1 | Fully supported | |
| AMA Audience / Workflow | Sales Sequence1:1 | Fully supported |
Gotchas + challenges
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! gotchas
Act! Premium Desktop and Cloud use different export paths and cannot share a single migration script
Act! Custom Tables (v18+) have no standardized schema across customers
Activity Series (recurring activities) explode into thousands of occurrences
Act! Marketing Automation campaign history is in a separate database
Act! contact layouts can hide fields without dropping them from the schema
Document attachments in Act! Desktop are file-system pointers, not blobs
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Discovery + tier + Sequences plan
Confirm Act! deployment, Freshsales tier (Growth/Pro/Enterprise), Lead-vs-Contact split if used, AMA workflows to re-create as Sales Sequences. Inventory custom fields/Groups/Custom Tables.
Freshsales pre-flight
Deploy Pipelines + Stages, Custom Modules (Enterprise) or note structure for Custom Tables, custom fields, Sales Sequence templates, Freddy AI baseline configuration.
Sample + customer review
200 Contacts, 50 Accounts, 30 Deals + Products, 100 Activities, 500 History items. Customer reviews mapping fidelity and Sales Sequence draft.
Full extraction + Document download
Bulk Act! extraction. Documents prepared. AMA workflows captured for rebuild.
Full load via Freshsales API
Accounts → Contacts → Deals + Products → Activities → Notes → Documents → Custom Module records. Field-level diff.
Sales Sequence rebuild + cutover
Sales Sequences built from AMA workflow definitions. Delta sync on cutover. Reps switch to Freshsales. Act! read-only for safety window.
Platform deep dives
Act!
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Act! and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Act!: Not publicly documented for Cloud; Desktop is limited only by the customer's SQL Server and IIS capacity.
Data volume sensitivity
Act! doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Act! to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Act! to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Act!
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
