Migrate from Atollon Lagoon CRM to Microsoft Dynamics 365 Sales

Atollon Folders store individual contact records within the Firm database. Folders carry a classification column (client, potential client, partner) and may have custom form data attached via formID and context. We map Folder records directly to Dynamics 365 Contact, preserve the classification as a custom Contact field, and parse any attached formvalue records into corresponding custom fields on the Contact. Folder-level classification tags map to a Dynamics 365 Option Set or text field depending on the customer's configuration preference.

Atollon Firms are company-level records with classification (client, potential client, partner) and optional custom form data. We map Firms to Dynamics 365 Account 1:1, using Firm name as the Account Name dedupe key and Firm ID as an external reference field. Custom classification columns become Account-level custom fields. Account is created before Contact import so that the parent AccountId lookup is satisfied at Contact insert time.

Atollon Projects with the Contract subtype map to Dynamics 365 Opportunity. Contract-specific custom fields from the project template map to Opportunity custom fields. Project status, start date, and end date migrate to corresponding Opportunity fields or custom date fields. The Project name becomes the Opportunity Name; contract value maps to Amount. We use a dedicated Opportunity Record Type for contract-type projects to keep them visually distinct in Microsoft Dynamics 365 Sales .

Atollon Business case projects map to a separate Opportunity Record Type (Business Case) in Dynamics 365. The Business Case template fields map to Opportunity custom fields including any financial modelling fields, stakeholder fields, or approval-status fields. We apply subtype-aware mapping so that business case metadata does not collide with contract project fields on the same Opportunity object.

Service contract projects can map to Opportunity (if the destination uses a sales-cycle model) or to a custom ServiceContract entity in Dynamics 365 if the customer maintains post-sale service tracking. We determine the mapping during scoping based on whether the customer wants to track service contracts inside the sales pipeline or as a separate service entity. Recurring billing values from Atollon migrate as custom fields on the destination entity.

Consultation and implementation projects map to a third Opportunity Record Type (Consultation) in Dynamics 365. Project milestones from Atollon migrate as custom Milestone fields or as child Tasks on the Opportunity. Template-specific fields from the Consultation template schema map to corresponding custom Opportunity fields defined before migration.

Atollon Activities (team email, SMS, phone calls, meetings) linked to Folders or Firms migrate to Dynamics 365 Task (for calls and tasks) and Event (for meetings). Email content migrates as Task body or EmailMessage records linked to the parent Contact or Account. Activity type, timestamp, owner, and direction (inbound/outbound) preserve. We resolve the owner by email match against the Dynamics 365 User table and hold unresolved owners in a reconciliation queue.

Atollon Milestones track timeline checkpoints within Projects or Activities. Each Milestone carries order, due date, status, and optional custom form data. We map Milestones to Tasks attached to the parent Opportunity, using the Milestone order to set the Task rank and ActivityDate to the due date. Custom form values on Milestones parse via formID and migrate to custom Task fields.

Atollon stores custom form field values in separate formvalue records linked by formID and context. One parent record may have multiple formvalues. We parse each formvalue individually, resolve the field schema via formID, and map field-level values to Dynamics 365 custom fields on the parent entity (Contact, Account, or Opportunity). The relationship is normalised at migration time and the original formvalue structure is documented in the handoff report for audit.

Atollon Service Support records track ticket-like issues with status, priority, assigned agent, and linked Firm or Project references. We map these to Dynamics 365 Case with Case Status from Atollon status, Case Priority from priority, and the agent lookup resolved by email against Dynamics 365 User. Linked Firm maps to the CustomerId (Account) lookup and linked Project maps to a custom reference field or the Regarding field if the project is an Opportunity.

Atollon Invoice header data (invoice number, date, amount, status, line items) maps to Dynamics 365 Invoice if the destination org has the Invoice entity enabled, or to custom fields on the parent Opportunity if Invoice is not in scope. Invoice status, amounts, and linked Firm or Project references migrate. Detailed financial history (payment receipts, credit notes) depends on whether the destination Dynamics 365 org has Finance modules enabled.