CRM migration
Field-level mapping, validation, and rollback between Atollon Lagoon CRM and Twenty CRM. We move data and schema; workflows are rebuilt natively in Twenty CRM.
Atollon Lagoon CRM
Source
Twenty CRM
Destination
Compatibility
7 of 10
objects map 1:1 between Atollon Lagoon CRM and Twenty CRM.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Atollon Lagoon CRM bundles CRM, projects, service, and finance into a single application with an active-user billing model, but its near-complete absence of public API documentation creates a data-portability wall that becomes critical the moment a customer needs to move platforms. Twenty CRM is an open-source, self-hostable CRM built on a modern React and NestJS stack with a documented REST API, GitHub-backed development, and a data model that maps closely to the Company, Person, Opportunity, Task, and Event objects familiar from Salesforce-style schemas. The structural migration involves resolving Atollon's Folder-and-Firm hierarchy into Twenty's separate Company and Person objects, normalising custom form formvalue records into Twenty's custom field properties, and mapping Atollon Projects against Twenty Opportunities with subtype-aware field schemas. Workflow Automations (Advanced tier only) cannot be exported via API and are documented for manual rebuild. Finance module records migrate as header data only; full financial history requires a separate finance-system migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Atollon Lagoon CRM object lands in Twenty CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Atollon Lagoon CRM
Folder (Contacts)
Twenty CRM
Person
1:1Atollon Folders are individual contact records classified by role (client, potential client, partner) and stored within the Firm hierarchy. We map Folders to Twenty Person records, preserving the full name, email, phone, classification columns, and any custom field values parsed from formvalue records linked to the Folder context. The Firm lookup on Folder becomes a Company (from Firm) link in Twenty Person via the workspace Company relation.
Atollon Lagoon CRM
Firm (Company)
Twenty CRM
Company
1:1Atollon Firms are the company-level records in the firm database, serving as the parent entity for Folders. We map Firms to Twenty Company records 1:1, preserving company name, address, classification (client, potential client, partner), and any custom firm-level formvalue records. The Company is created before Folder migration so that the Person.Company relation is satisfied at insert time.
Atollon Lagoon CRM
Project
Twenty CRM
Opportunity
1:1Atollon Projects span four subtypes — Contracts, Business cases, Service contracts, and Consultations — each potentially using different templates with different custom field sets. We first classify each project by its template origin, then apply a subtype-aware field mapping schema to Twenty Opportunities. Without a clear template, a generic mapping applies. Project subtypes map to Opportunity names prefixed with the subtype for disambiguation. Milestones and due dates on a Project migrate as Opportunity custom fields or linked Tasks.
Atollon Lagoon CRM
Activity
Twenty CRM
Task and Event
1:manyAtollon Activities track engagement records (calls, emails, meetings, SMS) linked to Folders or Firms. We split by activity type: call activities map to Twenty Task with TaskSubtype=Call; meeting activities map to Twenty Event with start and end timestamps; email and SMS activities map to Twenty Task records with a custom body field carrying the message content. All activities preserve the original timestamp, the linked Folder (Person) or Firm (Company), and the owning user reference.
Atollon Lagoon CRM
Milestone
Twenty CRM
Task or Opportunity custom field
lossyAtollon Milestones track timeline checkpoints within Projects or Activities and may carry custom form data. We map Milestones to Twenty Task records linked to the parent Opportunity (from the Project mapping), preserving order, due date, and any custom field values carried in formvalue records. If the customer prefers milestone-as-field, we convert milestone data to custom fields on the Opportunity during schema design.
Atollon Lagoon CRM
Custom Forms (Folder, Project, Activity, Milestone)
Twenty CRM
Custom fields on Person, Opportunity, Task
1:1Atollon stores custom form field values in separate formvalue records linked by formID and context, not directly on the parent object. One parent may have multiple formvalues. We parse each formvalue record individually, resolve the field schema via formID, and map field-level values to destination custom fields on the corresponding Person, Opportunity, or Task object. This normalisation step adds processing time not present in standard object migrations and must be validated against the form schema before final import.
Atollon Lagoon CRM
Service Support Record
Twenty CRM
Task (Case-like)
1:1Atollon's service and support module manages ticket-like records with status, priority, assigned agent, and linked Firm or Project references. We map these to Twenty Task records, setting a custom task type field to distinguish them from standard CRM activities. Status maps to Twenty Task Status, priority maps to Task Priority, and the linked Firm becomes a Company lookup on the Task. Complex case workflows require manual configuration in Twenty post-migration.
Atollon Lagoon CRM
Invoice / Billing Record
Twenty CRM
Not migrated
lossyAtollon's finance and invoicing module generates invoices linked to Projects or Firms. Twenty CRM has no native billing or finance module. We migrate invoice header data (invoice number, amount, status, date, linked Firm and Project) as a custom Invoice object in Twenty's workspace custom field tooling, but detailed financial history, line items, and payment records require export to a separate accounting system. This is scoped as a partial migration with a written handoff to the customer's finance team.
Atollon Lagoon CRM
Workflow Automation (Advanced tier)
Twenty CRM
Not migrated
1:1Workflow Automation is gated to the Advanced tier (EUR 496+/month) and is not accessible via Atollon's API. We do not migrate automation rules. During discovery we document every active workflow rule (trigger conditions, actions, and sequence) and deliver a written rebuild guide mapped to Twenty's custom data model capabilities or a third-party automation tool. Customers on the Basic tier have no automations to migrate.
Atollon Lagoon CRM
Campaign Record (Ultimate tier)
Twenty CRM
Not migrated
1:1Campaign Management is available only on Atollon's Ultimate tier. We map campaign-level records including name, status, and linked target list size to a written inventory for the customer's admin to rebuild in their chosen marketing tool. Marketing automation actions, sequence steps, and campaign workflows are not migratable from Atollon and are documented for manual rebuild.
| Atollon Lagoon CRM | Twenty CRM | Compatibility | |
|---|---|---|---|
| Folder (Contacts) | Person1:1 | Fully supported | |
| Firm (Company) | Company1:1 | Fully supported | |
| Project | Opportunity1:1 | Fully supported | |
| Activity | Task and Event1:many | Fully supported | |
| Milestone | Task or Opportunity custom fieldlossy | Fully supported | |
| Custom Forms (Folder, Project, Activity, Milestone) | Custom fields on Person, Opportunity, Task1:1 | Fully supported | |
| Service Support Record | Task (Case-like)1:1 | Fully supported | |
| Invoice / Billing Record | Not migratedlossy | Fully supported | |
| Workflow Automation (Advanced tier) | Not migrated1:1 | Fully supported | |
| Campaign Record (Ultimate tier) | Not migrated1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Atollon Lagoon CRM gotchas
Active-user billing scoping on import
No publicly documented API for programmatic export
Custom form data requires formvalue-level parsing
Project templates and subtypes need subtype-aware mapping
Workflow Automations are tier-gated and non-portable
Twenty CRM gotchas
Import order is enforced and critical
Export limited to 20,000 records and visible columns only
Soft-deleted records count toward uniqueness and trigger restores
API rate limits cap at 200 req/min on Organization tier
No native email sequences — follow-up cadences require external tools
Pair-specific challenges
Migration approach
API verification and export method selection
We begin every Atollon Lagoon CRM migration with an API accessibility test using the customer's credentials. We attempt to reach the observed form API endpoints, verify authentication (token or session-based), and measure response shape and completeness. If the API is accessible and returns consistent data, we use API-based extraction for Folders, Firms, Projects, Activities, and custom formvalue records. If the API is unavailable or returns inconsistent data, we fall back to structured CSV export supported by Atollon's data tools. The chosen export method is locked before any downstream schema design begins.
Discovery and data audit
We audit the Atollon instance across active-user count, tier (Basic, Advanced, Ultimate), Folders, Firms, Projects (with subtype classification), Activities by type, custom forms (with formID and context inventory), service support records, and any invoice or billing data. We identify all workflow automations and campaign records for documentation. We assess data quality (duplicate Firms, orphaned Folders, null required fields) and produce a written data audit report that includes record counts per object, custom form schema inventory, and a list of any data requiring cleaning before migration.
Twenty workspace schema design
We design the destination Twenty workspace schema based on the audit output. This includes creating Company and Person custom fields matched to Atollon Folder and Firm field names, designing Opportunity stages mapped from Atollon Project statuses and subtypes, defining custom fields for migrated Milestones and Service Support records, and creating a reference custom object for invoice header data. The schema is validated in a staging Twenty instance before production migration begins. Owner reconciliation runs in parallel: we extract every distinct Atollon user referenced on records and map them to Twenty workspace user accounts by email.
Custom formvalue normalisation and field mapping
We parse Atollon's custom form formvalue records in isolation, resolving each formID to its field schema, and building a normalised field-to-value map per parent record. This normalisation step is applied to Folders, Firms, Projects, Activities, and Milestones. The output is a flat set of field-value pairs per record that can be directly mapped to Twenty custom fields. We validate the normalised output against a sample of Atollon records before running the full production migration. Any formvalue records with missing formID references are flagged and held for manual review.
Production migration in dependency order
We run production migration into the live Twenty instance in record-dependency order: Companies (from Atollon Firms, first because they are the parent of Persons), Persons (from Atollon Folders with Company relation resolved), Opportunities (from Atollon Projects with subtype-aware field mapping applied), Tasks and Events (from Atollon Activities split by type), Service support Tasks (from Atollon service records), and custom field data (from normalised formvalue records applied to the corresponding parent record). Each phase emits a row-count reconciliation report before the next phase begins. We use exponential backoff and chunking on any API-based destination writes.
Cutover, delta sync, and automation handoff
We freeze writes in Atollon during the cutover window, run a final delta migration of any records modified since the last full sync, then enable Twenty as the system of record. We deliver the Workflow and Automation inventory document and the Campaign rebuild guide to the customer's admin team. We do not configure automations in Twenty as part of the migration scope. We support a one-week hypercare window for reconciliation issues raised by the customer's team. Finance module invoice header data is handed off to the customer's finance team for import into their accounting platform of choice.
Platform deep dives
Atollon Lagoon CRM
Source
Strengths
Weaknesses
Twenty CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Atollon Lagoon CRM and Twenty CRM.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Atollon Lagoon CRM: Not publicly documented.
Data volume sensitivity
Atollon Lagoon CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Atollon Lagoon CRM to Twenty CRM migration scoping. Not seeing yours? Book a call.
Walk through your Atollon Lagoon CRM to Twenty CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Atollon Lagoon CRM
Other ways to arrive at Twenty CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.