Act! to Salesforce migration
We migrate Contacts, Companies, Opportunities, and the full Activity + History timeline from Act! into Salesforce Sales Cloud — using the Act! Web API or direct SQL extraction at the source, Salesforce Bulk API 2.0 at the destination, and explicit Lead vs Contact split design before any record moves.
FlitStack AI migrates contacts, leads, accounts, opportunities and opportunitylineitems from Act! to Salesforce, 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: 4-6 weeks.

What moves from Act! to Salesforce?
Moving from Act! to Salesforce Sales Cloud is a fidelity exercise: Act!'s contact-first model collapses into Salesforce's Account → Contact → Opportunity hierarchy, with a deliberate Lead-vs-Contact split decided up front.
Read the full summary
Act! treats every record as a Contact regardless of qualification state; Salesforce splits unqualified prospects into Leads and qualified buyers into Contacts attached to Accounts. We resolve that split during scoping by applying a rule the customer signs off on (e.g., Contacts with no Opportunity history → Lead, Contacts with at least one closed-won Opportunity → Contact + Account). Activities and History migrate through Salesforce's Bulk API 2.0 with chunking and parent-record resolution so the full Act! timeline lands against the correct Contact/Account/Opportunity. Act! Groups translate to Salesforce Campaigns when the membership is engagement-driven, or to Reports + List Views when the membership is segmentation-driven — we make that call during scoping. Custom Tables map to Salesforce Custom Objects (available from Professional tier with no add-on cost) — a structural advantage over HubSpot, where Custom Objects are Enterprise-only.
Contact (qualified) → Contact (linked to Account)
Act! Contacts with a closed-won Opportunity (or matching a customer-defined qualification rule) migrate as Salesforce Contacts attached to an Account.
How it maps
We resolve the Account first (creating it from Act! Company or deriving from Contact.Company) then create Contacts with explicit AccountId.
Contact (unqualified) → Lead
Act! Contacts that don't meet the customer's qualification rule migrate as Salesforce Leads.
How it maps
We preserve the original Act! ID/Status as the Lead Status field and the original creation date as Lead CreatedDate via the Bulk API's data-preserve mode.
Company → Account
Act! Companies map to Salesforce Accounts.
How it maps
Where Act! Company is missing, we derive an Account from Contact.Company_Name with deduplication on normalized name. Parent-child account hierarchy is preserved if Act! tenants used the Company → Sub-Company convention.
Opportunity → Opportunity
Act! Opportunities map to Salesforce Opportunities linked to the resolved Account.
How it maps
Stage names map via a translation table aligned to the customer's Salesforce Sales Process. Weighted forecast preserves via Probability; close date and status carry over.
Opportunity Product → OpportunityLineItem
Act! Opportunity Products map to Salesforce OpportunityLineItem records.
How it maps
We pre-create matching Salesforce Products and PricebookEntries during setup, then attach line items with the standard Pricebook association.
Activity (scheduled) → Task / Event
Act! Calls and To-dos → Salesforce Tasks.
How it maps
Meetings → Salesforce Events. Attendees, location, and description preserve. Recurring Activity Series expand within an agreed active window and the rule stores as a custom field.
- ContactContact1:1
- ContactLead1:1
- CompanyAccount1:1
- OpportunityOpportunity1:1
- Opportunity ProductOpportunityLineItem1:1
- ActivityTasktransformed
+ 6 more in the mapping below
How Act! and Salesforce 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! | Salesforce |
|---|---|---|
| Prospect model | Single Contact object with ID/Status field | Separate Lead and Contact objects with explicit Convert action |
| Hierarchy | Contact-centric; Company optional | Account → Contact → Opportunity strictly enforced |
| Custom objects | Custom Tables in Premium v18+ (tenant-defined) | Custom Objects from Professional tier with no add-on cost |
| Deployment | Cloud SaaS or on-premise (Desktop) | Cloud-only SaaS |
| Pricing | ~$30/user/mo Cloud or ~$370/user perpetual | $25–$300/user/mo by tier; storage chargeable above 10 GB org-wide |
| Automation | Act! Workflow add-on or none | Salesforce Flow (record-triggered, scheduled, screen flows) |
| App ecosystem | Low double-digit integrations | AppExchange with 9,000+ listings |
Act! to Salesforce field mapping
The 18 most-used fields of 18 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.
-
ContactContactFirstName + LastNameContact -
TitleContactTitleContact -
E-mailContactEmailContact -
Phone (Business)ContactPhoneContact -
Mobile PhoneContactMobilePhoneContact
| Act! field | Salesforce field | Mapping | Note |
|---|---|---|---|
Contact.Contact | Contact.FirstName + LastName | split | Single Act! field splits at last whitespace; suffixes (Jr., III) attach to LastName. |
Contact.Title | Contact.Title | direct | Pass through. |
Contact.E-mail | Contact.Email | direct | Lowercase; Salesforce dedupe rules apply via Duplicate Management. |
Contact.Phone (Business) | Contact.Phone | direct | Normalize to E.164 where feasible. |
Contact.Mobile Phone | Contact.MobilePhone | direct | Pass through. |
Contact.Address fields | Contact.MailingStreet / City / State / PostalCode / Country | direct | Multi-line Act! address concatenates with newline into MailingStreet. |
Contact.ID/Status | Lead.Status | mapping | Translation table to Salesforce Lead Status picklist values (Open, Working, Qualified, etc.). |
Contact.Last Edit Date | Contact.LastModifiedDate | direct | Requires Bulk API 2.0 audit-field preservation enabled on the destination org. |
Company.Company | Account.Name | direct | Required; dedupe via Salesforce Account Matching Rules. |
Company.Web Site | Account.Website | direct | Normalize and use as secondary dedupe key. |
Opportunity.Name | Opportunity.Name | direct | 120-character limit; truncate with audit log. |
Opportunity.Total | Opportunity.Amount | direct | Currency conversion applies if Act! tenant uses multi-currency. |
Opportunity.Stage | Opportunity.StageName | mapping | Mapped via Salesforce Sales Process. Stage probability inferred from Sales Process default if not set explicitly. |
Opportunity.Estimated Close Date | Opportunity.CloseDate | direct | Required; defaults to today + 30 days if Act! field is null. |
Activity (Meeting).Date / Time / Duration | Event.StartDateTime / DurationInMinutes | direct | Time-zone normalized to org default. |
Activity (Task).Date | Task.ActivityDate | direct | Date-only; time-of-day is dropped on Tasks (Salesforce Task doesn't support time). |
Activity.Subject | Task / Event.Subject | direct | 255-character limit; truncate with audit log. |
Note.Note Text | ContentNote.Content | direct | Encoded as base64 per Salesforce ContentNote requirements. |
What to watch for in a Act! to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Lead-vs-Contact split must be decided before extraction
Act! treats every record as a Contact regardless of qualification.
How we handle it
Salesforce requires every record to land as either a Lead (unqualified prospect) or a Contact attached to an Account (qualified buyer). We need a clear rule before extraction — typically based on Opportunity history, ID/Status field values, or last interaction date. Trying to migrate everything as Contacts works mechanically but defeats the purpose of moving to Salesforce in the first place.
Activity history requires Bulk API 2.0 with audit-field preservation
Salesforce by default stamps the import user as the Activity owner and the import timestamp as the CreatedDate.
How we handle it
For the Act! Activity + History timeline to render correctly in Salesforce, we need org-level audit-field preservation enabled and the records loaded via Bulk API 2.0 with explicit CreatedDate and OwnerId values. The customer's Salesforce admin must enable 'Set Audit Fields upon Record Creation' before extraction begins.
Custom Tables require Salesforce Custom Object pre-creation
Act! Custom Table schemas vary per tenant.
How we handle it
The Salesforce Custom Object definitions need to be deployed before record load — including all custom fields, page layouts, list views, and any record-type assignments. We capture the Custom Table metadata during scoping and ship a Salesforce metadata package (.zip with object/field XML) that the customer's admin reviews and deploys.
Storage charges apply above 10 GB org-wide
Salesforce includes 10 GB of file storage at the org level (regardless of seat count) and charges for additional storage in 50 GB increments.
How we handle it
Act! installations with large Document libraries can exceed this allotment on the first migration. We pre-calculate the post-migration storage footprint during scoping and surface any storage upgrade requirement to the customer before load begins.
Act! Group dynamic-query translation requires customer review
Act! Dynamic Group query operators (contains-any-of, regex, complex date math) don't all map cleanly to Salesforce Report filter criteria.
How we handle it
We translate the supported subset and rewrite the rest with the customer's sign-off — usually by breaking one Act! Group into multiple Salesforce Reports or relaxing a filter and noting the original query in the Report description.
How the migration runs
Discovery + Lead/Contact split rule
We confirm Act! deployment model (Cloud vs Desktop), capture credentials, inventory Contact custom fields, Group definitions, Custom Tables, Document volume, and User roster.
What this step covers
The output is a scope document plus the agreed Lead-vs-Contact qualification rule.
Salesforce pre-flight + metadata deployment
We deploy Custom Objects for Act!
What this step covers
Custom Tables, custom fields on Contact/Account/Opportunity for every populated Act! custom field, Sales Process with stage mapping, Lead Status picklist, and Duplicate Management rules. Audit-field preservation gets enabled before extraction.
Sample migration + customer review
We migrate ~200 Contacts (mix of Lead and Contact per the rule), 50 Accounts, 30 Opportunities with Line Items, 100 Activities, and 500 History items spanning two reps.
What this step covers
Customer reviews mapping fidelity, Lead-vs-Contact distribution, and stage translation before full run.
Full extraction + Document download
Bulk Act! extraction with chunking, staged in the migration database.
What this step covers
Document library downloads in parallel and pre-stages to Salesforce Files via the ContentVersion API for batch attachment during load.
Full load via Bulk API 2.0
Bulk load Accounts first, then Contacts/Leads, then Opportunities + OpportunityLineItems, then Tasks/Events/EmailMessages, then ContentDocumentLinks for Documents.
What this step covers
After load, field-level hash diff between Act! and Salesforce, with any miss surfaced for review.
Cutover + Act! decommission
On cutover day, delta sync captures records modified since bulk load.
What this step covers
Sales reps switch to Salesforce. Act! remains read-only for an agreed safety window (30–90 days) before decommission — for Desktop tenants this includes SQL Server backup archival and license return.
- 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 Lead-vs-Contact split complexity, Custom Table count, and Activity History volume. A straightforward Act! Migrations involving on-premise Act! Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Act! to Salesforce →Why teams move from Act! to Salesforce
- Act! teams move to Salesforce when the business outgrows contact-first sales and needs account-based selling — Salesforce's Account → Contact → Opportunity hierarchy is the industry standard for B2B sales orgs with multi-stakeholder buying committees, named-account targeting, and complex deal structures that don't fit Act!'s single-record-per-Contact model.
- AppExchange depth (9,000+ apps including CPQ, ERP, marketing automation, finance, HR) is the structural draw for teams whose IT roadmap requires their CRM to be the system of record across the customer lifecycle. Act!'s integration count is in the low double-digits — a meaningful gap for enterprise stacks.
- Salesforce Flow's record-triggered, scheduled, and screen flow variants replace the manual workflow execution that's typical in Act! installations. Sales ops teams that have outgrown Act!'s automation footprint adopt Salesforce specifically for declarative automation at scale without writing code.
- Salesforce Reports + Dashboards (and Tableau CRM Analytics at Enterprise+) bring live BI inside the CRM — replacing the 'export from Act! to Excel and pivot' cycle that defines reporting in most Act! installations. Sales managers expecting live pipeline coverage, deal velocity, and rep activity metrics adopt Salesforce for the analytics layer alone.
- Custom Objects are available from Salesforce Professional tier ($80/user/month) at no add-on cost, while Act! Custom Tables require Premium v18+ and HubSpot Custom Objects require Enterprise. For Act! tenants with Custom Tables (Policies, Properties, Cases, Loans), Salesforce is the lowest-friction destination for preserving the tenant-defined schema as queryable, reportable records.
Questions, answered
Act! to Salesforce migration questions
How do you decide what becomes a Salesforce Lead vs a Contact?
We agree the rule during scoping. The most common rule is: Act! Contacts with at least one closed-won Opportunity migrate as Salesforce Contacts on the relevant Account; Contacts without Opportunity history (or with only closed-lost) migrate as Leads. Some teams use the Act! ID/Status field instead. Once the rule is set, we apply it consistently and reconcile counts so you know exactly how the migrated population splits.
Will my Act! Activity and History data preserve its original timestamps in Salesforce?
Yes, but it requires a Salesforce org setting: 'Set Audit Fields upon Record Creation' enabled by your Salesforce admin. With that enabled, we load Activities, Tasks, and Events via Bulk API 2.0 with explicit CreatedDate values so the Salesforce timeline reads in correct chronological order. Without that setting, Salesforce stamps the import user/date and the timeline loses chronology.
Are Act! Custom Tables supported?
Yes — they map 1:1 to Salesforce Custom Objects. Salesforce Custom Objects are available from Professional tier ($80/user/month) at no add-on cost, making Salesforce the lowest-friction destination for Act! tenants with Custom Tables (Policies, Properties, Cases, Loans). We capture the Custom Table metadata during scoping and deploy matching Custom Objects before load.
What happens to my Act! Marketing Automation campaign data?
AMA campaign data lives in a separate database. We extract via the AMA API and roll up engagement signals (last open, last click, total sends, bounce status) as custom Contact properties in Salesforce. Per-send historical detail is archived as CSV rather than re-created as live Salesforce records. If you're moving marketing automation to Pardot (Marketing Cloud Account Engagement), we deliver a parallel integration plan during scoping.
How are Act! Documents stored in Salesforce?
As Salesforce Files (ContentDocument/ContentVersion) attached to the parent Contact, Account, or Opportunity via ContentDocumentLink. Storage counts against your Salesforce file-storage allotment (10 GB at org level + additional 50 GB increments purchasable). For large Document libraries, we calculate the post-migration footprint during scoping so you know whether storage tier upgrades are needed before load.
Can Act! continue running during the Salesforce migration?
Yes. Extraction is read-only (Web API for Cloud, read-only SQL for Desktop). Sales reps continue working in Act! through cutover. On cutover day, delta sync picks up anything modified since the bulk load and we formally switch the team to Salesforce. Act! stays read-only for 30–90 days as a safety net before formal decommission.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → GoldMine to SalesforceMapping · history · rollbackPipedrive to SalesforceMapping · history · rollbackAttio to SalesforceMapping · history · rollbackZoho CRM to SalesforceMapping · history · rollbackMailchimp to SalesforceMapping · history · rollbackHubSpot to SalesforceMapping · history · rollback Act! to Zoho CRMMapping · history · rollbackAct! to HubSpotMapping · history · rollbackAct! to Odoo CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Act! to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote