Migrate from Spotler Mail+ to Twenty CRM

Discovery and data audit

We audit the Spotler Mail+ account across contacts, tags, scores, custom field definitions, form submissions, user accounts, and mailing analytics. We identify which data exists as native objects versus custom fields, confirm the export format available per the Spotler API and dashboard, and assess whether any deal or pipeline data exists in external systems that must be merged. We also confirm the customer's Twenty instance status (self-hosted or cloud-hosted on twenty.com) and any existing data in Twenty that would create duplicates. The discovery output is a written migration scope with record counts per object and a data quality pre-assessment.

Schema design in Twenty CRM

We pre-create all required fields in Twenty CRM Settings → Data Model before any import. This includes custom fields matching Spotler field types (text, numeric, currency, select, multi-select, date), a spotler_original_id__c field for contact traceability, a spotler_score__c numeric field for lead scores, and any company-domain or segmentation fields needed for company splitting. If Opportunity records must be constructed, we create the Opportunity object schema with relevant fields. We also invite all team members who will be mapped as Twenty Members before record import begins, as Twenty requires user records to exist before Owner references can be resolved.

Export and transform from Spotler Mail+

We export contact data via the Spotler REST API using cursor-based pagination with exponential backoff on rate-limit responses. For large databases (over 50,000 contacts) we implement scripted looping with checkpointing to resume from the last successful page. We export tags as multi-value fields, scores as numeric fields, and custom fields by type. Form submissions export as separate CSV files per form. Analytics data exports from the Spotler analytics dashboard within the 24-month retention window. During transformation we split company names from contacts into a separate Company dataset, deduplicate Company records by name, and assign email domains for additional company matching.

Sandbox import and reconciliation

If the customer has a Twenty staging or development instance, we run a full import there first. The customer reconciles record counts (People in, Companies in, Opportunities in), spot-checks 20-30 random Person records against the Spotler source for field accuracy, and validates that tag-label associations and score values are preserved correctly. Mapping corrections are made before production import. If no staging environment exists, we run a dry-run import using a subset of records to validate the import pipeline before committing the full dataset.

Production import in dependency order

We run production import in record-dependency order: Companies first (resolved from contact company names), then People (linked to Companies via theWorkEmail relation), then Labels (created and linked to People), then custom field data. Form submissions load as Notes attached to People. User accounts map to Twenty Members. Analytics data loads into a custom object or as document-attached Notes. Each phase emits a row-count reconciliation report before the next phase begins. Owner and assignee references resolve via email matching against the Twenty Member table.

Cutover, validation, and automation rebuild handoff

We freeze writes to Spotler Mail+ during cutover, run a final delta migration of any records modified during the migration window, then enable Twenty CRM as the system of record. We deliver the written Workflow Automation inventory document to the customer's admin team with trigger-condition-action documentation for each Spotler workflow. We support a three-day hypercare window where we resolve any data reconciliation issues raised by the customer's team. We do not rebuild Spotler automations as code; that work is a separate engagement or an internal admin task using the customer's chosen automation platform.