Migrate from Atollon Lagoon CRM to Odoo CRM

Atollon Folders are individual contact records stored within the Firm hierarchy. We map Folders to Odoo Contact records with standard name, email, phone, and address fields carried forward. Classification columns (client, potential client, partner) migrate to a contact_type tag on the Odoo Contact. Folder-level custom formvalues attach to the Contact as custom fields via Odoo's ir.model.fields API after we resolve the formID schema.

Atollon Firms are the top-level company records with classification columns and optional parent-child hierarchies. We map Firms to Odoo Companies (res.partner records with is_company=True). The Firm's classification column migrates to a custom tag or a picklist field on the Company. Address, industry, and classification fields carry forward. Odoo Companies must exist before Folders map to Contacts so the parent Company lookup is satisfied on import.

Atollon Projects span at least four subtypes — Contracts, Business cases, Service contracts, and Consultations — each potentially using different templates with different custom field sets. We classify each project by its template origin, apply the corresponding field mapping schema, and map to Odoo Project records. Subtype information is preserved in a project_tag so filtering by origin type remains possible in Odoo. Projects without a clear template default to a generic Odoo Project mapping. Odoo Project must be installed from the Apps list before migration begins.

Atollon Activities track engagement records (calls, emails, meetings) linked to Folders or Firms with timestamp, type, and owner. We map to Odoo mail.message records for the activity content and type, and project.task records for task-style follow-up items. Email type activities migrate to mail.message; call dispositions migrate to a custom call_duration field on the mail.message. Activity owner resolves to an Odoo User by email match.

Atollon Milestones track timeline checkpoints within Projects with ordering, due date, and optional custom form data. Odoo Project does not have a native Milestone object; we map Milestones to project.task records with the milestone name in task_name, the original due date as deadline, and ordering preserved via sequence or stage assignment. Custom field values from any milestone formvalue records migrate to custom fields on the Odoo task.

Atollon stores custom form field values as separate formvalue records linked by formID and context (parent object type and ID). The form-to-formvalue relationship is not always 1:1 — one parent may have multiple formvalues from different form schemas. We parse each formvalue record, resolve the field schema via formID, normalise field-level values to their data types, and map them to Odoo custom fields on the equivalent standard object (Contact, Company, Project, or Task). We pre-create Odoo's ir.model.fields entries before import so the fields exist in the schema.

Atollon's service and support module manages ticket-like records with status, priority, assigned agent, and links to Firms and Projects. We map these to Odoo Helpdesk tickets (helpdesk.ticket) if the Helpdesk app is installed. Ticket status, priority, and agent assignment carry forward. Linked Firm and Project references resolve to the Odoo Company and Project IDs created during earlier phases. Helpdesk stage names are configured to match Atollon's status labels.

Atollon's billing and finance module generates invoices linked to Projects or Firms. We map invoice header data (number, date, partner, amount, status) to Odoo account.move records. Line items, tax amounts, and detailed financial history transfer depends on Odoo Accounting being installed and configured with a matching chart of accounts. We do not migrate detailed payment reconciliation history or partial payment allocations as these require account-specific configuration.

Workflow Automation is an Advanced-tier feature (EUR 496+/month) that sequences business process steps. Atollon does not expose automation logic via its public API. We do not migrate automation rules as code. We document which automations existed, their trigger conditions, steps, and recommended equivalents in Odoo's Automated Actions (base.automation) and Server Actions (ir.actions.server), and deliver a rebuild guide for your admin.

Campaign management is available on Atollon's Ultimate tier. We map campaign-level records (name, status, linked targets) to Odoo UTM campaigns (utm.campaign) if the UTM app is installed. Marketing automation actions, sequence steps, and campaign performance metrics do not migrate as these are action-oriented features requiring manual rebuild in Odoo's Email Marketing or Marketing Automation apps.

Atollon Folder owners, Firm owners, Project owners, and Activity owners all reference a user profile. We extract every distinct owner referenced on migrating records and match by email against Odoo's res.users table. Any Atollon owner without a matching Odoo User is held in a reconciliation queue; your admin provisions the missing user in Odoo before record import resumes. OwnerId must be resolved before importing any record that carries an ownership reference.

Atollon uses classification columns on Folders and Firms (client, potential client, partner, etc.) and tags on Projects. We map these to Odoo Tags: res.partner.category for contact and company classifications, and project.tags for project-level categorisation. Tags are created in Odoo before data import so the tag IDs are available during record load.