Migrate from Atollon Lagoon CRM to Salesforce Sales Cloud

Atollon Folders (individual contacts stored within the Firm database) map to Salesforce Contact. The Folder's primary classification column (client, potential client, partner) migrates to a Salesforce custom picklist field Folder_Classification__c. Email address, phone, and address fields map to standard Contact fields. The parent Firm reference resolves to an AccountId at migration time by matching the Firm name. We verify that the Account exists before inserting Contacts to satisfy the lookup constraint.

Atollon Firms (company-level records in the firm database) map to Salesforce Account. The firm classification column (client, potential client, partner) maps to Account Type or a custom classification field. Firm name becomes Account Name; registered address maps to Billing fields. We create Accounts before Contacts so that AccountId is available for the Contact lookup at insert time. If the same company name appears under multiple Folders, we dedupe to a single Account and link all related Contacts.

Atollon Projects span four subtypes (Contracts, Business cases, Service contracts, Consultations) with different templates and custom field sets. We classify each Project by its template origin before applying the corresponding field mapping schema. All subtypes map to Salesforce Opportunity, with subtype information stored in a custom Opportunity Type field and the project template name preserved in a custom Project_Template__c field. Projects without a clear template default to a generic mapping. Opportunities are linked to Accounts via AccountId resolved from the parent Firm reference.

Each Atollon project subtype (Contracts, Business cases, Service contracts, Consultations) becomes a Salesforce Opportunity Record Type with a corresponding Sales Process. The Record Type scopes the Page Layout and whitelists the relevant stage values so that sales reps only see stages relevant to their project type. Stage probability percentages and stage order migrate from Atollon's template configuration.

Atollon Activities (calls, emails, meetings, SMS) linked to Folders or Firms map to Salesforce Task and Event. Call and SMS activities map to Task with TaskSubtype set appropriately. Email activities map to Task with the content stored as Task.Description. Meeting activities map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Owner resolution is by email match against the Salesforce User table; unresolvable owners are held in a reconciliation queue.

Atollon Milestones (timeline checkpoints within Projects or Activities) map to Salesforce Task records linked via WhatId to the parent Opportunity. Milestone order, due date, and completion status migrate as Task fields. Any custom form data attached to a Milestone is parsed via formvalue-level extraction and stored as custom Task fields. We preserve milestone sequence by setting Task.ActivityDate to the milestone due date and Task.Priority to reflect ordering.

Atollon stores custom form field values in separate formvalue records linked by formID and context (Folder, Project, Activity, or Milestone). We parse each formvalue record individually, resolve the field schema via formID, and map field-level values to Salesforce custom properties on the parent object. This normalisation step handles cases where one parent has multiple formvalues — each is processed separately and its values mapped to distinct custom fields. We create the custom fields in Salesforce before import using the field type inferred from the formvalue data type.

Atollon's service and support module manages ticket-like records. We map these to Salesforce Case, with ticket status mapping to Case Status, priority mapping to Case Priority, and assigned agent mapping to Case OwnerId via email resolution. The linked Firm and Project references migrate as Case AccountId and a custom Project__c lookup field respectively. Conversation history migrates as EmailMessage records linked to the Case.

Atollon invoices linked to Projects or Firms migrate as a custom Invoice object in Salesforce (custom object with __c API name matching the Atollon billing module naming convention). Invoice header data, line items, amounts, and payment status migrate as custom fields. We do not migrate financial transaction history into standard Salesforce objects because Salesforce is not a financial system of record; the migrated invoice data provides billing context against the Opportunity rather than a complete accounting ledger.

Atollon Campaign records (Ultimate tier feature) map to Salesforce Campaign with campaign name, status, start date, and end date preserved. Campaign targets and linked Folders migrate as CampaignMember records. We do not migrate marketing automation actions (email sends, lead scoring from campaigns) because those are automation-layer features that require rebuild in Salesforce Marketing Cloud Account Engagement (Pardot) or Marketing Cloud.

Atollon Owner references on Folder, Firm, Project, Activity, and Milestone records are resolved by email match against the Salesforce destination org's User table. We extract every distinct Owner from the source data before migration and reconcile against the target org. Any Owner without a matching User goes to a reconciliation queue; the customer's Salesforce admin provisions missing Users before record import resumes.

Atollon Workflow Automations are Advanced-tier only and are not exposed via API. We do not migrate automation rules as code. We deliver a written inventory of every active Atollon Workflow Automation documenting its trigger, conditions, actions, and step sequence, paired with a recommended Salesforce Flow equivalent and rebuild steps. The customer's admin or a Salesforce partner reconstructs the automations post-migration.