CRM migration

Migrate from Atollon Lagoon CRM to Freshsales

Field-level mapping, validation, and rollback between Atollon Lagoon CRM and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Atollon Lagoon CRM logo

Atollon Lagoon CRM

Source

Freshsales

Destination

Freshsales logo

Compatibility

91%

10 of 11

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

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Atollon Lagoon CRM to Freshsales addresses the core limitation that drives most departures from Atollon: the absence of a publicly documented API for reliable data export and the thin independent review signal on the platform's long-term trajectory. Freshsales, part of the Freshworks suite, provides a fully documented REST API, global support infrastructure, and a tiered pricing model (Growth at $29/user/month, Pro at $69/user/month, Enterprise at $99/user/month) with AI-assisted routing and Freddy AI features. We map Atollon's Folder-based contact structure to Freshsales Contacts, Firms to Accounts, and Projects (Contracts, Business cases, Service contracts, Consultations) to Deals with subtype-aware field mapping. Custom form data requires parsing formvalue records by formID before populating Freshsales custom fields. Workflow Automations, billing automation, and campaign management records do not migrate because Atollon does not expose automation logic via its public API; we deliver a written inventory of these for the customer's admin to rebuild in Freshsales.

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Atollon Lagoon CRM objects map to Freshsales

Each row shows how a Atollon Lagoon CRM object lands in Freshsales, 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 (Contact)

maps to

Freshsales

Contact

1:1
Fully supported

Atollon stores individual contacts as Folders within the firm database, classified by type columns (client, potential client, partner, or custom). We map Folder records to Freshsales Contacts, preserving the Folder type as a custom contact field, the contact's email address as the dedupe key, and the linked Firm reference as the AccountId lookup. Folders without an email address are flagged for review before import.

Atollon Lagoon CRM

Firm (Company)

maps to

Freshsales

Account

1:1
Fully supported

Atollon Firms are the company-level records, classified as client, potential client, or partner. We map Firms to Freshsales Accounts with a 1:1 field mapping on name, address, phone, website, and industry. The Firm classification column migrates to a custom Account field. Account is created before Contact import so that the AccountId lookup is satisfied at Contact insert time.

Atollon Lagoon CRM

Project (Contracts)

maps to

Freshsales

Deal (Contract subtype)

1:1
Fully supported

Atollon Projects with the Contracts subtype carry template-driven fields (contract value, renewal date, contract type). We map these to Freshsales Deals, assigning a Deal subtype custom field to distinguish them from other project types. Contract-specific fields (renewal date, contract value) map to Freshsales custom Deal fields. We use Freshsales Record Types to segment by project subtype if the customer requires separate pipeline views for each project type.

Atollon Lagoon CRM

Project (Business cases)

maps to

Freshsales

Deal (Business case subtype)

1:1
Fully supported

Atollon Business case projects carry structured fields for justification data, projected ROI, and approval status. We map these to Freshsales Deals with a custom Business case subtype field. Approval status and ROI projections migrate to custom Deal fields. The project template origin is preserved in a migration metadata field so that subtype classification is auditable post-migration.

Atollon Lagoon CRM

Project (Service contracts)

maps to

Freshsales

Deal (Service contract subtype)

1:1
Fully supported

Service contract projects in Atollon track deliverables, SLA terms, and service-level milestones against a Firm. We map these to Freshsales Deals with a custom Service contract subtype field. SLA terms and deliverable descriptions migrate as custom fields on the Deal. Milestone data attached to the service contract migrates as a separate task list linked to the Deal.

Atollon Lagoon CRM

Project (Consultations)

maps to

Freshsales

Deal (Consultation subtype)

1:1
Fully supported

Consultation and implementation projects in Atollon track scope, milestones, and resource allocation. We map these to Freshsales Deals with a custom Consultation subtype field. Project milestones migrate as Tasks against the Deal, preserving due dates and milestone status from the Atollon record.

Atollon Lagoon CRM

Activity

maps to

Freshsales

Activity (calls, emails, meetings, tasks)

1:1
Fully supported

Atollon Activities track engagement records (calls, emails, meetings, tasks) linked to Folders or Firms. We map each activity type to its Freshsales equivalent: calls to Freshsales Call records, emails to Email records, meetings to Meeting records, and tasks to Task records. Activity owner resolves via email match to the Freshsales User. Timestamp and duration fields migrate directly. Linked Folder or Firm references resolve to the migrated Contact or Account.

Atollon Lagoon CRM

Milestone

maps to

Freshsales

Task

1:1
Fully supported

Atollon Milestones track timeline checkpoints within Projects or Activities. We map Milestones to Freshsales Tasks linked to the corresponding Deal (from the project mapping). Milestone order, due date, and status migrate directly. Any custom field values stored on the Milestone via formvalue records are parsed and populated on the Freshsales Task custom fields.

Atollon Lagoon CRM

Custom Form (formvalue records)

maps to

Freshsales

Custom Fields on standard objects

lossy
Fully supported

Atollon custom forms are attached to Folders, Projects, Activities, and Milestones via formID and context. Formvalues are stored separately and linked by formvalue ID — the relationship between form and formvalue is not always 1:1. We parse each formvalue record individually, resolve the field schema via formID, and map field-level values to Freshsales custom properties on the corresponding standard object. We create Freshsales custom fields (text, number, date, picklist, or checkbox) before import and populate them during the object import phase. This normalisation step adds a preprocessing pass not required for standard object migration.

Atollon Lagoon CRM

Service Support Record

maps to

Freshsales

Ticket

1:1
Fully supported

Atollon's service and support module manages ticket-like records. We map these to Freshsales Tickets, preserving status, priority, assigned agent (resolved by email match), and linked Firm/Project references. Ticket conversation history migrates as a threaded note or attachment on the Freshsales Ticket.

Atollon Lagoon CRM

Invoice and Billing Record

maps to

Freshsales

Deal custom financial fields

1:1
Fully supported

Atollon billing and finance module generates invoices linked to Projects or Firms. We map invoice header data (invoice number, date, amount, status) and line items to custom fields on the corresponding Freshsales Deal. Detailed financial history migration depends on the destination Freshsales tier and whether the customer uses Freshbooks or another finance integration. We document the invoice field mapping and flag any financial data that requires a separate accounting system migration.

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Active-user billing scoping on import

    Atollon Lagoon bills per actively-used user profile, not per total seat or named user. Freshsales bills per user seat. When migrating data from Atollon, the destination system creates User accounts based on Owner references on migrated records. If the customer has more named employees than Atollon active users, importing records may cause Freshsales to create more user accounts than their intended seat count. We flag the active-user count during scoping, align the import to the minimum required User accounts, and map inactive Owner references to a migration service account rather than a full user seat to avoid unexpected cost escalation in Freshsales.

  • No publicly documented API for programmatic export

    Atollon Lagoon provides no publicly accessible API documentation covering endpoints, authentication, or rate limits. We have observed custom form and project API patterns in internal documentation (CreateCustomForm, formID, context, formvalue records) but these are not guaranteed stable or complete. We verify API access credentials and test connectivity before migration; where the API is unavailable or returns inconsistent results, we fall back to structured CSV export supported by Atollon's data tools. We document which export method was used per object in the migration package so that the customer can audit the source data lineage.

  • Custom form data requires formvalue-level parsing

    Atollon stores custom form field values in separate formvalue records linked by formID and context, not directly on the parent object. The relationship between form and formvalue is not always 1:1 — one parent record may have multiple formvalues from different form templates. We parse each formvalue record individually, resolve the field schema via formID, and map field-level values to Freshsales custom fields. This adds a normalisation preprocessing step. For custom forms with dynamic schemas (fields added or removed over time), we pin the formvalue to the schema version active at the time of the record's creation and flag schema drift in the migration report.

  • Project subtypes need subtype-aware field mapping

    Projects in Atollon span at least four subtypes — Contracts, Business cases, Service contracts, and Consultations — each using different templates with different custom field sets. We handle subtype-aware mapping by first classifying each project by its template origin, then applying the corresponding field mapping schema for that subtype. Projects without a clear template default to a generic Deal mapping with a custom project_type__c field to flag them for post-migration review. If the customer uses multiple simultaneous templates within a single subtype, we capture the template name in a migration metadata field on the Freshsales Deal.

  • Workflow Automations and billing automation do not migrate

    Workflow Automation in Atollon Lagoon is gated to the Advanced tier (EUR 496+/month) and is not exposed via the API. Billing automation and Campaign Management (Ultimate tier) similarly cannot be exported programmatically. We document which automations existed in Atollon, capture their trigger conditions and actions in a written inventory, and provide a rebuild guide mapping each automation to Freshsales Workflow equivalents. The customer's admin rebuilds these in Freshsales after migration. We do not include workflow rebuild in the standard migration scope.

Migration approach

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

  1. Discovery and scoping

    We audit the source Atollon Lagoon instance across tier (Basic, Advanced, Ultimate), active-user count, object volumes (Folders, Firms, Projects by subtype, Activities, Milestones, Service Support Records), custom form count with field definitions, and any known data quality issues. We pair this with a Freshsales edition decision: Growth ($29/user) covers most migrations without complex custom objects; Pro ($69/user) is required if the customer needs multiple sales pipelines, advanced workflow branching, or custom Deal fields at scale; Enterprise ($99/user) only if AI-driven routing, territory management, or集团-level reporting is required. The discovery output is a written migration scope document and a Freshsales edition recommendation.

  2. Schema design and custom field provisioning

    We design the destination schema in Freshsales. This includes creating custom fields on Contact (Folder type, custom contact properties), Account (Firm classification), and Deal (subtype field, contract-specific fields, service SLA fields, milestone mapping). For each project subtype, we configure a Freshsales Record Type or custom picklist field to distinguish Contracts, Business cases, Service contracts, and Consultations. Custom form fields from Atollon formvalue records are pre-created as Freshsales custom fields with matching types (text, number, date, checkbox, picklist). Schema is validated in a Freshsales sandbox before production migration begins.

  3. Sandbox migration and reconciliation

    We run a full migration into a Freshsales sandbox environment using production-like data volume. The customer's RevOps lead reviews record counts (Folders in, Firms in, Projects in, Activities in), spot-checks 20-40 random records against the Atollon source for field-level accuracy, and validates that the subtype-aware project mapping is producing the expected Deal structure. Formvalue parsing is specifically audited — we sample 10-20 records with complex custom form data and verify that the parsed field values match the original Atollon formvalue content. Any mapping corrections happen in sandbox before production migration begins.

  4. Owner reconciliation and User provisioning

    We extract every distinct Owner referenced on Folders, Firms, Projects, Activities, Milestones, and Service Support Records and match by email against the Freshsales destination User table. Atollon stores owner IDs internally without a direct email field on every record — we resolve owners by cross-referencing the user profile email in Atollon's user management module. Owners without a matching Freshsales User are held in a reconciliation queue. The customer's Freshsales admin provisions any missing Users. Migration cannot proceed past this step because owner lookups are required on most standard objects in Freshsales.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Atollon Firms), Contacts (from Folders with AccountId resolved), Deals (from Projects with subtype-aware field mapping applied), Activities (calls, emails, meetings, tasks via Freshsales Bulk API with chunking), Milestones (as Tasks linked to Deals), Service Support Records (as Tickets), custom form data (formvalue records parsed and populated on the parent standard object during the parent import phase), and invoices (as Deal financial fields). Each phase emits a row-count reconciliation report before the next phase begins. We freeze Atollon writes during the cutover window and run a final delta pass for any records modified during migration.

  6. Cutover, validation, and automation rebuild handoff

    After the final delta migration, we enable Freshsales as the system of record and deliver the migration package: a reconciliation report comparing Atollon record counts to Freshsales import counts, a custom field mapping matrix showing every source field to destination field mapping including formvalue-derived fields, and a written Workflow and Automation inventory documenting each Atollon automation with its trigger, conditions, actions, and a recommended Freshsales Workflow equivalent. We support a three-day hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild Atollon Workflows as Freshsales Workflows inside the migration scope; that is a separate engagement or an internal admin task.

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.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 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 Freshsales.

  • Object compatibility

    B

    2 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 Freshsales 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 Freshsales data migrations

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

Can't find your answer?

Walk through your Atollon Lagoon CRM to Freshsales 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 10,000 Folders, 2,000 Firms, and 1,000 Projects with no complex custom form structures. Migrations with multiple project subtypes (Contracts, Business cases, Service contracts, Consultations), more than 50 custom form fields with formvalue-level dependencies, large engagement histories (over 200,000 Activity records), or owner reconciliation spanning more than 50 distinct user profiles move to seven to eleven weeks because of formvalue parsing overhead, subtype-aware schema mapping, and Freshsales Bulk API chunking for activity history.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Atollon Lagoon CRM.
Land in Freshsales, 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