The Ultimate Act! to Zoho CRM Migration Checklist: Preserving Notes, History, and Relationships

If you're still running Act! CRM, you're in good company: and you've probably noticed that Swiftpage hasn't exactly been innovating. Meanwhile, your team is asking for mobile access, workflow automation, and integrations that Act! just can't deliver anymore.

We've migrated dozens of Act! databases to Zoho CRM over the past 25 years, and we've learned one critical lesson: a migration is not a data dump. It's a reconstruction.

Most migrations fail because companies treat them like a simple CSV export and import. They move contacts, companies, and maybe a few deals: then wonder why their sales team can't find the notes from three years ago, why activity histories are incomplete, and why attachments disappeared.

This guide walks you through what it actually takes to preserve the business logic, relationships, and historical context that make your CRM valuable in the first place.

Why Simple Data Exports Aren't Enough: The Reconstructor Philosophy

Act! wasn't built like modern CRMs. It's a relational database with decades of custom tables, linked records, and embedded business logic. When you export to CSV, you get flat files: rows and columns with no memory of how records connect to each other.

Here's what gets lost in a basic export:

• Parent-child relationships between contacts and companies
• Activity chains that show the full sales cycle progression
• Note sequences that tell the story of each customer relationship
• Attachment associations that link files to the right records
• Custom field dependencies and lookup values
• User ownership and security visibility rules

At FullRange CRM Consulting, we approach every migration as a reconstruction project, not a data transfer. That means:

1. Mapping the existing business logic in your Act! database before touching any data
2. Rebuilding relationships in Zoho using custom Deluge scripts and API calls
3. Preserving context so your team doesn't lose institutional knowledge
4. Training your team on the new structure so adoption is smooth

Think of it like moving a house. You don't just dump all the furniture in the new place and hope it works: you have a floor plan, you know what goes where, and you reconstruct the layout so people can actually live there.

The Critical Elements That Usually Break

Over two decades of migrations, we've seen the same four data types cause problems every single time. Let's break them down.

1. Notes and History Records

Act! stores notes as separate records linked to contacts, companies, and opportunities. They include timestamps, user attribution, and often contain the most valuable context in your entire database: why a deal was lost, what a customer's pain points are, verbal agreements that never made it into a contract.

What breaks: Standard CSV imports treat notes as plain text fields. You lose the timestamp, the author, and the linkage to the right record. Three years of sales history becomes a single text blob with no context.

How we fix it: Custom Deluge scripts that recreate each note as a discrete record in Zoho, preserving the original date, the user who wrote it, and the correct parent record association.

2. Activity Histories and Scheduled Tasks

Act! tracks calls, meetings, to-dos, and emails with incredible detail: recurrence patterns, alarm settings, completion status, and linked contacts. When you export to CSV, most of that structure collapses.

What breaks: Activities import as static records with no recurrence, no alarms, and often the wrong timezone. Your team loses their task queue and can't see the historical cadence of customer interactions.

How we fix it: We extract activities with their full metadata, convert timezone offsets correctly, and use Zoho's API to rebuild recurring tasks and set proper reminders. For completed activities, we preserve the completion date and outcome notes so your sales history stays intact.

3. Attachments and Documents

Act! lets you attach Word docs, PDFs, images, and spreadsheets directly to contact and company records. These files live in your Act! directory structure and are referenced by internal IDs.

What breaks: Standard exports don't include file attachments at all. You end up with references to files that no longer exist, or worse: everything dumps into a single folder with no way to tell which file belongs to which customer.

How we fix it: We extract attachments with their original filenames and parent record IDs, then use Zoho's file upload API to reattach them to the correct records in Zoho CRM. Large file batches are handled in stages to respect Zoho's API rate limits.

4. Relationships Between Records

This is the big one. Act! uses internal relationship IDs to connect contacts to companies, opportunities to contacts, and activities to all of the above. CSV exports strip those IDs out, leaving you with orphaned records.

What breaks: Contacts lose their company associations. Deals lose their related contacts. Activities show up with no clear owner. Your sales pipeline becomes a disconnected mess.

How we fix it: We preserve Act! record IDs during extraction, map them to new Zoho IDs during import, and use custom Deluge scripts to rebuild every relationship link. This is where 25 years of migration experience makes a difference: we know which ID fields to trust and which ones Act! corrupts over time.

How Custom Zoho Deluge Code Ensures a Clean Reconstruction

Zoho's built-in import tools are solid for simple data. But Act! migrations require custom code because you're not just moving data: you're rebuilding business logic in a completely different system architecture.

Here's where Zoho Deluge (Zoho's scripting language) becomes essential:

Relationship Rebuilding

We write Deluge functions that query imported records, match them by preserved IDs, and use Zoho's API to create the proper linkages. For example, after importing contacts and companies separately, a Deluge script runs through each contact, finds its parent company by matching the old Act! Company ID, and updates the Zoho "Account" lookup field.

Note Sequencing and Attribution

Standard imports can't preserve note authorship or timestamps accurately. We use Deluge to create each note as a separate Zoho Notes record, set the created time to match the original Act! timestamp, and attribute it to the correct Zoho user (after mapping Act! users to Zoho users during setup).

Activity Recurrence and Alarms

Zoho's API allows programmatic creation of tasks with recurrence rules and reminders. We extract Act! activity metadata, translate recurrence patterns into Zoho's format, and use Deluge to schedule tasks correctly so your team's follow-up cadence doesn't skip a beat.

Batch Processing and Error Handling

Large databases can have tens of thousands of records. Deluge scripts handle batch processing, API rate limiting, retry logic for failed imports, and detailed error logging so we can catch and fix issues before cutover.

This level of customization isn't optional for a clean Act! migration: it's the difference between a working CRM and a data graveyard.

Pre-Migration Checklist

Before we touch any data, here's what needs to happen:

Week 1-2: Discovery and Planning

• Full Act! database backup (stored safely offsite)
• Inventory of custom fields, groups, and modules in scope
• User mapping (which Act! users become which Zoho users)
• Field mapping document (Act! fields → Zoho fields)
• Decision on what not to migrate (old duplicates, test records, obsolete fields)

Week 2-3: Zoho Configuration

• User accounts and profiles created in Zoho
• Custom fields built in Zoho before import
• Picklist values configured to match Act! dropdown options
• Page layouts designed for your sales process
• Workflow automation drafted (but disabled until after cutover)

Week 3-4: Test Migration

• Small sample dataset extracted from Act!
• Test import into Zoho sandbox environment
• Validation of relationships, notes, activities, attachments
• Adjustments to field mapping and Deluge scripts
• Team walkthrough of test environment for feedback

Migration Execution: The Cutover Weekend

We schedule the final migration during off-hours (typically Friday night through Sunday morning) to minimize business disruption. Here's the sequence:

1. Final Act! backup and database export
2. Data extraction in correct order: Companies → Contacts → Deals → Activities → Notes → Attachments
3. Zoho import in the same order, using custom Deluge scripts for relationship rebuilding
4. Validation checks after each module (record counts, spot checks, error log review)
5. Workflow activation once data validation passes
6. User access enabled Sunday afternoon
7. Act! database remains available read-only for two weeks during transition

Post-Migration Validation

The first week after cutover is critical. We work with your team to:

• Spot-check 50+ records across all modules
• Verify that notes, attachments, and activities appear in the right places
• Confirm that workflows trigger correctly
• Address any user questions or confusion
• Monitor Zoho's API logs for issues

We also keep your Act! database accessible (read-only) for two weeks so your team can reference old records if needed. After two weeks, most teams are fully transitioned and Act! gets retired.

Ready to Migrate Your Act! Database to Zoho?

If you're still reading, you probably realize this isn't a DIY project. Act! migrations require deep knowledge of both systems, custom scripting expertise, and experience with the edge cases that break most migrations.

At FullRange CRM Consulting, we've been doing this since before Zoho existed. We're Certified Zoho Partners with 25+ years of CRM implementation experience, and we've migrated hundreds of legacy databases (Act!, Salesforce, Dynamics, Pipedrive, HubSpot) to Zoho without data loss.

Our process:

• Discovery call to assess your Act! database and migration goals
• Fixed-price proposal (no surprises, no hourly billing creep)
• Dedicated project manager from start to finish
• Custom Deluge scripting for relationship preservation
• Two weeks of post-migration support to ensure smooth adoption

We don't hand you a CSV file and wish you luck. We rebuild your CRM so your team can actually use it on day one.

Schedule your free discovery call at fullrangecrm.com and let's talk about your migration timeline, budget, and what success looks like for your team.

Your Act! data is valuable. Let's make sure it stays that way.