Migrate from Act-On to monday CRM

Discovery and schema mapping

We audit the Act-On portal for Contact and Company volumes, Custom Data schema definitions (field names, types, picklist options), List definitions (static vs dynamic), Program membership logs, engagement history volume by event type, and tag taxonomy. We pair this with a Monday.com CRM workspace audit to identify existing boards, column types, and automations. The discovery output is a written migration scope with a field-level mapping table for every Act-On field and its Monday column equivalent, including any new columns that need to be created before import.

Board and column configuration in Monday.com CRM

We configure the Monday CRM boards before any data import. This includes creating the People board (if not already present) with all required columns mapped from Act-On Contact properties, creating the Organizations board with company fields, and adding any custom columns required for Custom Data schema fields. Column types are set per the Act-On field type mapping (text, number, date, email, phone, dropdown). Boards are configured in a staging workspace first and validated before moving to production.

Data cleansing and deduplication

We run a data quality pass on Act-On export data before import. This includes identifying duplicate Contacts (by email address), standardizing phone number formats, resolving blank required fields (last name, email), and flagging orphaned Companies with no linked Contacts. Deduplication rules are applied at import time: duplicate email addresses are merged into a single Person item with activity history consolidated. Any records failing validation are held in a review queue for the customer's admin to resolve before re-import.

Organization import first, then People

We import Organizations (from Act-On Companies) before People (from Act-On Contacts) because the People-Organization relationship requires the Organization to exist at the time of Person insert. Owner assignment resolves by email against Monday workspace members during import. Unresolved owners are flagged for admin to assign manually. Tags and List membership migrate alongside their parent records.

Engagement history and Program membership import

Activity events (email opens, clicks, form submissions) import as Activity Log entries on the relevant Person items, chunked by date range to stay within Act-On's undocumented throttling. Program membership logs import as a separate reference board with one item per contact showing which Programs they were enrolled in and when. This board serves as the blueprint document for rebuilding Program sequences as Monday Workflow automations.

Cutover, validation, and handoff documentation

We freeze Act-On writes during the cutover window, run a final delta migration of any records modified since the initial export, then mark Monday CRM as the system of record. We deliver a validation report comparing record counts and spot-checking field values against the Act-On source. The handoff package includes the field mapping table, Program membership reference board, Workflow automation rebuild guide (for the admin), and the engagement score component reference. We do not rebuild Act-On Programs as Monday Workflows inside the migration scope; that work is a separate engagement or an internal admin task.