Migrate your Act! data

Contacts are Act!'s primary record. Full export via the Act! Web API (/api/contacts) for Cloud tenants and direct SQL Server SELECT on tbl_Contact for Desktop deployments. We preserve every standard and custom field including the long-tail of legacy fields that accumulated across Act! versions (Personal, Home, Spouse, Children, Assistant). Secondary Contact records linked to a primary Contact migrate as additional Contact records with a relationship custom field pointing back to the primary.

Companies in Act! are optional — many small-business installations skip them and put company info on the Contact record. We detect this pattern during scoping and either map Companies → Organization records in the destination, or roll up Contact.Company_Name into a derived Organization. Custom Company fields export via the Web API or tbl_Company table.

Act! Groups are a flexible categorization mechanism used for segmentation, mailing lists, and sub-organization. Static Groups (manually maintained membership) map to Lists/Tags/Static Segments in the destination. Dynamic Groups (rule-based) require rule translation — we capture the Act! query criteria and re-build equivalent filters as Smart Lists or Saved Views in the destination.

Opportunities export from /api/opportunities (Cloud) or tbl_Opportunity (Desktop). Standard fields (name, value, stage, weighted forecast, close date, probability, status) map directly to Deal/Opportunity in destination CRMs. Stage names are Act!-tenant-specific (e.g., 'Initial Communication', 'Quote Sent', 'Closed Won') and require a stage mapping table built during scoping.

Opportunity line items (Products) export from the Opportunity Products sub-object. Each line carries SKU, name, quantity, unit price, discount, and extended price. We pre-create Products in the destination as a master list, then attach line items to Opportunities via the destination's deal-products endpoint where supported (HubSpot, Pipedrive, Salesforce). Destinations without a native deal-product object receive line items as a JSON note on the Deal.

Act! Activities (Calls, Meetings, To-dos, Personal Activities) export with scheduled date, duration, subject, attendees, location, and Series identifier for recurring activities. We expand recurring series into individual occurrences (capped at the active window the customer specifies — typically the next 12 months and the last 2 years of history) and map to the destination's Task/Activity/Event objects. Pre-scheduled activities in the future migrate first so the salesperson's calendar continues uninterrupted.

History items are Act!'s completed-activity audit log — every call logged, email sent, meeting held, and note created. These are read-heavy and high-volume (often the largest table in the database). We chunk by date range during export to avoid timing out the API or SQL query, and map each history item to a Note/Task/Activity in the destination tagged with the original timestamp so the timeline reads correctly.

Notes attached to Contacts, Companies, Groups, or Opportunities export with author, timestamp, and rich-text body. We strip Act!-proprietary RTF formatting and convert to HTML or plain text depending on what the destination's Note object accepts. Note attachments (where Act! stores them inline) extract to a temp folder and re-upload as Attachments on the destination record.

Documents attached to Contacts and Opportunities are stored in Act!'s Supplemental Files folder (Desktop) or the Web API attachment endpoint (Cloud). We download each file individually and re-upload to the destination, preserving filename, mime type, and the parent record link. Very large document libraries (>50 GB) typically take a dedicated migration window. Documents stored as links rather than embedded files migrate as URL references.

Act! Premium v18 and later support Custom Tables — tenant-defined object types beyond the standard schema (e.g., Policies for an insurance agency, Properties for a real estate firm). These map to the destination's Custom Objects where supported (HubSpot Enterprise, Salesforce Professional+, Zoho Ultimate, Pipedrive). Destinations without custom-object support receive Custom Table data as a related Contact note with the structured fields serialized as a JSON block.

Secondary Contacts are Act!'s mechanism for tracking assistants, spouses, or alternative decision-makers linked to a primary Contact. We migrate each as a standalone Contact in the destination with a custom field 'Primary Contact' pointing back to the parent record so the relationship is preserved without duplicating engagement history.

Act! User records (name, email, role) export from the Users table and map to Users in the destination. We match by email. Inactive Act! users are excluded by default unless they own records that must retain provenance; in that case we either re-activate them in the destination as service accounts or re-assign their records to a designated 'Legacy Migrations' user.

Act! Marketing Automation Audiences (segments used for email campaigns) export via the AMA add-on API. We map them to Lists, Tags, or Audience Segments in the destination depending on what the destination's marketing layer supports (HubSpot Lists, Salesforce Campaign Members, Mailchimp Audiences). Campaign send history does not migrate by default but can be replicated as engagement notes if the customer requests it.