CRM migration

Migrate from Atollon Lagoon CRM to Twenty CRM

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 logo

Atollon Lagoon CRM

Source

Twenty CRM

Destination

Twenty CRM logo

Compatibility

70%

7 of 10

objects map 1:1 between Atollon Lagoon CRM and Twenty CRM.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Atollon Lagoon CRM logo

Atollon Lagoon CRM

What's pushing teams away

  • Very limited public API documentation means customers needing deep integrations or data portability hit a wall and look for alternatives with better developer resources.
  • The platform has stronger market presence in Czech and Central European markets; English-language support resources and documentation are thin for international teams.
  • With only three verified G2 reviews, independent signal on long-term reliability and feature trajectory is sparse — some buyers seek more validated platforms.
  • Organizations that grow beyond mid-market requirements often find the platform's feature set less extensible than global CRM leaders like Salesforce or HubSpot.
  • Limited third-party app marketplace compared to established CRMs means teams needing niche tools (specialised enrichment, advanced analytics) migrate elsewhere.

Choosing

Twenty CRM logo

Twenty CRM

What's pulling them in

  • Top open-source CRM on GitHub with 40.6K stars, giving teams full source code access and infrastructure ownership without per-feature licensing surprises.
  • Free self-hosting under AGPL-3.0 means unlimited users and custom objects for the cost of cloud infrastructure alone, typically $20–100/month.
  • Pricing page explicitly mocks competitors for charging add-on fees for API access, webhooks, and workflows — transparency that resonates with RevOps teams burned by Salesforce.
  • Unlimited custom objects and fields with no price impact, letting teams shape the data model to their business rather than forcing business into rigid schemas.
  • Modern TypeScript/React/PostgreSQL stack means developer-led teams can extend, self-host, or integrate without fighting legacy architecture.

Object mapping

How Atollon Lagoon CRM objects map to Twenty CRM

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)

maps to

Twenty CRM

Person

1:1
Fully supported

Atollon 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)

maps to

Twenty CRM

Company

1:1
Fully supported

Atollon 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

maps to

Twenty CRM

Opportunity

1:1
Fully supported

Atollon 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

maps to

Twenty CRM

Task and Event

1:many
Fully supported

Atollon 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

maps to

Twenty CRM

Task or Opportunity custom field

lossy
Fully supported

Atollon 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)

maps to

Twenty CRM

Custom fields on Person, Opportunity, Task

1:1
Fully supported

Atollon 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

maps to

Twenty CRM

Task (Case-like)

1:1
Fully supported

Atollon'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

maps to

Twenty CRM

Not migrated

lossy
Fully supported

Atollon'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)

maps to

Twenty CRM

Not migrated

1:1
Fully supported

Workflow 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)

maps to

Twenty CRM

Not migrated

1:1
Fully supported

Campaign 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.

Gotchas + challenges

What specifically takes care here

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 logo

Atollon Lagoon CRM gotchas

High

Active-user billing scoping on import

High

No publicly documented API for programmatic export

Medium

Custom form data requires formvalue-level parsing

Medium

Project templates and subtypes need subtype-aware mapping

Low

Workflow Automations are tier-gated and non-portable

Twenty CRM logo

Twenty CRM gotchas

High

Import order is enforced and critical

High

Export limited to 20,000 records and visible columns only

Medium

Soft-deleted records count toward uniqueness and trigger restores

Medium

API rate limits cap at 200 req/min on Organization tier

Low

No native email sequences — follow-up cadences require external tools

Pair-specific challenges

  • No publicly documented API means export method is uncertain

    Atollon Lagoon CRM does not publish API documentation covering endpoints, authentication methods, or rate limits. We have observed internal form API patterns (CreateCustomForm, formID, context, formvalue records) in Atollon's internal documentation, but these are not publicly confirmed stable. During scoping we verify API access credentials and test connectivity. Where the API is unavailable or unreliable, we fall back to structured CSV export supported by Atollon's data tools. This fallback affects the migration approach and timeline, so early API verification is the first step in every engagement.

  • Custom form formvalue records require multi-step normalisation

    Atollon stores custom form field values in separate formvalue records linked by formID and context, not directly on the parent Folder, Project, Activity, or Milestone. One parent record may have multiple formvalue entries. We parse each formvalue individually, resolve the field schema via the corresponding formID, and map field-level values to destination custom fields. This normalisation step is not required for Atollon's standard objects and must be validated against the live form schema before final import. Skipping this step results in orphaned or misattributed custom field data.

  • Project subtypes require subtype-aware field mapping

    Atollon Projects span at least four subtypes — Contracts, Business cases, Service contracts, and Consultations — each potentially using different templates with different custom field sets. Projects without a clear template origin default to a generic mapping. We classify each project by its template origin during the extract phase, then apply the corresponding field mapping schema to Twenty Opportunities. Failure to classify subtypes results in custom field mismatches and data integrity issues in the migrated Opportunities.

  • Workflow Automations are non-portable and tier-gated

    Workflow Automation is gated to the Advanced tier (EUR 496+/month) and is not exposed via Atollon's API. Customers on the Basic tier do not have automations to migrate. For Advanced and Ultimate customers, workflow rules cannot be exported programmatically and must be manually rebuilt. We document every active automation during discovery and deliver a rebuild guide, but we do not configure automations in Twenty as part of the migration scope. The absence of an automation layer in Twenty (Twenty focuses on the data model and permissions; workflow automation is typically handled via external tooling) should be addressed before cutover.

  • Finance module invoice migration is header-data only

    Atollon's Advanced and Ultimate tiers include a full invoicing and billing module. Twenty CRM has no native finance, billing, or accounting module. We migrate invoice header data (number, date, status, linked Firm, linked Project) as a reference record in Twenty's custom object tooling, but detailed line items, payment history, and financial reporting data cannot be represented in Twenty's data model. Customers requiring financial history must export from Atollon to a dedicated accounting platform post-migration.

Migration approach

Six steps for a successful Atollon Lagoon CRM to Twenty CRM data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Atollon Lagoon CRM logo

Atollon Lagoon CRM

Source

Strengths

  • All-in-one CRM, project management, service, and finance reduces tool sprawl for professional services teams.
  • Custom forms on Folders, Projects, Activities, and Milestones allow administrators to extend the data model without code.
  • Active-user billing model — paying only for users who log in — differentiates from per-seat pricing for firms with variable team sizes.
  • Built-in team email, SMS, and phone integration within the CRM eliminates separate communication stack costs.
  • Cloud and desktop deployment options give customers flexibility on hosting preference.

Weaknesses

  • Extremely limited public API documentation — no publicly available developer reference, authentication method, or rate limits documented.
  • Very low independent review volume (3 verified G2 reviews) makes it difficult to assess real-world satisfaction with support and uptime.
  • Central European market focus means fewer English-language resources, community forums, and integration connectors than globally-distributed CRMs.
  • No documented bulk export or bulk API capabilities, which complicates large-volume data migration for customers switching platforms.
  • Workflow automations are not exposed via API — automation rules cannot be migrated and must be manually rebuilt in the destination system.
Twenty CRM logo

Twenty CRM

Destination

Strengths

  • AGPL-3.0 open-source license with full source code on GitHub — no vendor lock-in, no sunset risk.
  • Unlimited users and unlimited custom objects on self-hosted, with no feature gating based on headcount.
  • REST and GraphQL APIs available on all paid tiers, not locked behind an enterprise add-on fee.
  • MCP server and webhooks shipped as standard features, not premium upgrades.
  • Modern PostgreSQL-backed data model that developer teams can query, extend, and self-host.

Weaknesses

  • Recent v1.0 release means limited production hardening compared to CRMs with multi-year operational track records.
  • No native email sequencing or sales engagement tools — follow-up cadences require a separate platform.
  • No native two-way email sync or inbox integration, requiring third-party connectors for full activity logging.
  • Self-hosting 'free' pricing hides real infrastructure and DevOps costs that stack up over time.
  • Workflow automation is functional but lacks the complexity needed for sophisticated multi-step sales motions.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Atollon Lagoon CRM and Twenty CRM.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Atollon Lagoon CRM: Not publicly documented.

  • Data volume sensitivity

    B

    Atollon Lagoon CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Atollon Lagoon CRM to Twenty CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Atollon Lagoon CRM to Twenty CRM data migrations

Answers to the questions buyers ask most during Atollon Lagoon CRM to Twenty CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for accounts under 15,000 Folders, 3,000 Firms, and straightforward custom form structures. Migrations with nested formvalue record hierarchies across multiple project subtypes, large Activity histories (over 200,000 records), or invoice header data requiring a custom object schema move to seven to eleven weeks because of the normalisation work and subtype classification. Timeline also depends on how quickly API access is confirmed or CSV export is produced.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Atollon Lagoon CRM.
Land in Twenty CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day