CRM migration
Field-level mapping, validation, and rollback between Atollon Lagoon CRM and Pipedrive. We move data and schema; workflows are rebuilt natively in Pipedrive.
Atollon Lagoon CRM
Source
Pipedrive
Destination
Compatibility
8 of 12
objects map 1:1 between Atollon Lagoon CRM and Pipedrive.
Complexity
BStandard
Timeline
3-6 weeks
Overview
Moving from Atollon Lagoon CRM to Pipedrive is a migration from a Central European all-in-one platform with bundled project and service modules to a globally-distributed sales-focused CRM with a well-documented API and a large integration marketplace. Atollon does not publish API documentation covering authentication, endpoints, or rate limits, which means the extraction approach must be validated at scoping before migration proceeds. Custom form data lives in formvalue records linked by formID and context, requiring a normalisation step not present in standard CRM-to-CRM migrations. Pipedrive's Deals and Activities are the primary destination objects for Atollon Projects and Activities respectively, with Folders mapping to Contacts and Firms mapping to Organizations. Workflow Automations (Advanced tier) and Campaign Management (Ultimate tier) are not accessible via API and do not migrate; we deliver a written inventory for manual rebuild. Pipedrive's Import2 partner tool supports a limited list of named CRMs and Atollon is not among them, so a custom API migration or structured CSV extraction is required.
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 Pipedrive, 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
Folders (Contacts)
Pipedrive
Person
1:1Atollon Folders classified as contacts (client, potential client, partner) map to Pipedrive Person records. The Folder classification column (client, potential client, partner) migrates as a custom Person field (e.g., contact_type__c with values matching the Atollon column). Folder-level custom forms with formvalue records parse to custom Person fields using formID to resolve the field schema. We map the primary contact's email, phone, and address fields to the corresponding Pipedrive Person fields; additional communication data migrates to custom fields.
Atollon Lagoon CRM
Firms (Companies)
Pipedrive
Organization
1:1Atollon Firm records map to Pipedrive Organization. The Firm classification column (client, potential client, partner) migrates as a custom Organization field. We use the Firm name as the Organisation name and map industry, size, and address data to Pipedrive Organisation fields. Any custom form data attached to the Firm via formvalue records normalises to custom Organisation fields using the same formID-based parsing approach used for Folders.
Atollon Lagoon CRM
Folders and Firms (linked)
Pipedrive
Person-Organisation relationship
1:1Atollon links Folders to Firms through the shared Folder structure. We resolve the Organisation reference on each Person record during migration by matching the Firm name to the destination Organisation. If a Folder has no Firm link, the Person is imported without an Organisation association and flagged for reconciliation.
Atollon Lagoon CRM
Projects
Pipedrive
Deal
1:1Atollon Projects map to Pipedrive Deals. Each of the four project subtypes (Contracts, Business cases, Service contracts, Consultations) may carry different custom fields based on their template origin. We classify each project by its template before migration and apply the corresponding field mapping schema. Projects without a clear template default to a generic mapping with title, status, dates, and budget amount mapped to Pipedrive Deal fields. The project budget migrates as the Deal value if a monetary amount is present.
Atollon Lagoon CRM
Project Milestones
Pipedrive
Activity (Note)
1:manyAtollon Milestones track timeline checkpoints within Projects. We map each Milestone as a Pipedrive Activity of type Note with the milestone name, due date, and completion status preserved. Milestones with custom form data carry those formvalue fields as custom Activity fields. If the customer requires milestone-to-Deal stage mapping, we configure a Pipedrive Deal field to track the current milestone and document the correlation.
Atollon Lagoon CRM
Activities (calls, emails, meetings)
Pipedrive
Activity
1:1Atollon Activities (team email, SMS, phone calls) linked to Folders or Firms map to Pipedrive Activity records. We preserve the activity type, timestamp, owner, and linked Person or Organisation reference. Call disposition and duration from Atollon phone integration migrate to custom Activity fields. Meeting activities carry location, attendees (as Activity participants), and duration.
Atollon Lagoon CRM
Custom Forms on Folders
Pipedrive
Custom Person fields
lossyAtollon custom forms attached to Folders use formID and context to link formvalue records. We parse each formvalue record, resolve the field schema via formID, and map typed values (text, number, date, dropdown) to Pipedrive custom Person fields. Multi-value form fields map to Pipedrive multi-select fields where the destination field type supports it.
Atollon Lagoon CRM
Custom Forms on Projects
Pipedrive
Custom Deal fields
lossyProject-attached custom forms carry the most varied field schemas due to template inheritance across project subtypes. We apply subtype-aware field mapping: Contracts forms map to Deal fields related to contract terms and values; Service contract forms map to fields related to deliverables and SLAs. The formvalue parsing normalises each subtype's field set independently before import.
Atollon Lagoon CRM
Service Support Records
Pipedrive
Lead
1:1Atollon's service and support module generates ticket-like records linked to Firms or Projects. We map these to Pipedrive Lead records, preserving status (open, in progress, resolved), priority, assigned agent, and the linked Organisation reference. Service ticket history migrates as Activity notes on the Lead. If Pipedrive Service Cloud is active, we evaluate mapping to Cases instead during scoping.
Atollon Lagoon CRM
Invoices and Billing Records
Pipedrive
Custom fields on Deal
lossyAtollon invoices and billing records are linked to Projects or Firms. We migrate invoice header data (invoice number, date, amount, status) as custom fields on the related Pipedrive Deal. Detailed financial line items are not mapped to Pipedrive's native data model because Pipedrive does not include a billing or ERP module. We document the invoice schema for the customer's admin to evaluate Pipedrive billing integrations post-migration.
Atollon Lagoon CRM
Campaign Records (Ultimate tier)
Pipedrive
Campaign
1:1Atollon campaign records (Ultimate tier) migrate to Pipedrive Campaign records, preserving campaign name, status, start and end dates, and linked target contacts. Campaign-level performance data (opens, clicks, responses) migrates to custom Campaign fields if present in Atollon. Marketing automation actions within the campaign do not migrate; we document the campaign workflow for rebuild in Pipedrive Workflows or a dedicated marketing automation tool.
Atollon Lagoon CRM
Workflow Automations
Pipedrive
Not migrated
1:1Workflow Automation is an Advanced-tier feature (EUR 496+/month) that sequences business process steps. The platform does not expose automation logic via its public API, and the automation model does not map to Pipedrive's Workflow engine in a portable way. We do not migrate automation rules. We document every active automation rule (trigger, conditions, actions, sequence order) and provide a rebuild guide mapping each rule to Pipedrive Workflow equivalents. The customer's admin rebuilds the automations post-migration.
| Atollon Lagoon CRM | Pipedrive | Compatibility | |
|---|---|---|---|
| Folders (Contacts) | Person1:1 | Mapping required | |
| Firms (Companies) | Organization1:1 | Mapping required | |
| Folders and Firms (linked) | Person-Organisation relationship1:1 | Fully supported | |
| Projects | Deal1:1 | Mapping required | |
| Project Milestones | Activity (Note)1:many | Fully supported | |
| Activities (calls, emails, meetings) | Activity1:1 | Fully supported | |
| Custom Forms on Folders | Custom Person fieldslossy | Fully supported | |
| Custom Forms on Projects | Custom Deal fieldslossy | Fully supported | |
| Service Support Records | Lead1:1 | Mapping required | |
| Invoices and Billing Records | Custom fields on Deallossy | Mapping required | |
| Campaign Records (Ultimate tier) | Campaign1:1 | Fully supported | |
| Workflow Automations | Not migrated1:1 | Not 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
Pipedrive gotchas
Custom field hash keys differ per account
Export access gated by visibility groups
Token-based API rate limits since December 2024
Sequences and Automations not exposed via REST API
Cost escalates via workflow caps and add-ons
Pair-specific challenges
Migration approach
Discovery and extraction strategy
We audit the Atollon Lagoon CRM instance across tiers (Basic, Advanced, Ultimate), active-user count, object inventory (Folders, Firms, Projects by subtype, Activities, custom forms by context, service records), and engagement volume. We verify API access credentials and test connectivity to the observed internal endpoints. If the API is unavailable or unreliable, we document the CSV export paths available in Atollon's data tools. We pair this with a Pipedrive scoping session covering the target pipeline structure, custom field requirements, and user provisioning plan. The discovery output is a written migration scope, an extraction strategy recommendation (API or CSV), and a Pipedrive field mapping draft.
Formvalue schema parsing and subtype classification
We extract the complete set of formID values referenced across Folders, Firms, Projects, Activities, and Milestones. For each formID we resolve the field schema (field name, type, required flag, picklist values). We classify each Project by its template origin to assign the correct field mapping. We flag any formvalue record that maps to a field not yet defined in Pipedrive so that custom fields are provisioned before import. This step produces a normalised data model ready for Pipedrive import without schema mismatch errors.
Pipedrive sandbox migration and reconciliation
We run a full migration into a Pipedrive sandbox using production-like data volume. The customer reconciles record counts (Persons in, Organisations in, Deals in, Activities in), spot-checks 20-30 random records against the Atollon source, and validates the formvalue-mapped custom fields. We also validate the Person-Organisation relationship resolution, the Deal pipeline stage mapping, and the activity timestamp ordering. Any mapping corrections happen in the sandbox before production migration begins.
Owner reconciliation and user provisioning
We extract every distinct Atollon user referenced as an activity owner or Folder/Project owner and match by email against the Pipedrive destination account's user list. Any Atollon owner without a matching Pipedrive user goes to a reconciliation queue. The customer's Pipedrive admin provisions any missing users (active or inactive depending on whether the original Atollon user is still with the company). Migration cannot proceed past this step because Activity owner references and Deal owner assignments require a valid Pipedrive user.
Production migration in dependency order
We run production migration in record-dependency order: Organisations (from Atollon Firms), Persons (from Atollon Folders with Organisation lookup resolved), Deals (from Atollon Projects with subtype-aware field mapping applied), Activities (from Atollon Activities linked to Persons or Organisations), Milestones (as Activity notes), custom fields (populated from formvalue records in the same batch as their parent object), Service records (as Leads), and Campaigns. We use Pipedrive's REST API with rate-limit handling and exponential backoff, falling back to CSV import if the API proves unreliable during the migration window. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation rebuild handoff
We freeze Atollon writes during cutover, run a final delta migration of any records modified during the migration window, then set Pipedrive as the system of record. We deliver the Workflow Automation and Campaign inventory document to the customer's admin team with a Pipedrive Workflow rebuild guide. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild Atollon automations as Pipedrive Workflows inside the migration scope; that is a separate engagement.
Platform deep dives
Atollon Lagoon CRM
Source
Strengths
Weaknesses
Pipedrive
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Pipedrive.
Object compatibility
3 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 Pipedrive migration scoping. Not seeing yours? Book a call.
Walk through your Atollon Lagoon CRM to Pipedrive 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 Pipedrive
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.