Migrate from Camp Automation to Salesforce Sales Cloud

Camp Automation Contacts with lifecycle stage of subscriber, lead, or marketing qualified lead map to Salesforce Lead. Lifecycle stages of sales qualified lead, opportunity, customer, or evangelist map to Salesforce Contact tied to an Account. We compute the split at migration time using Camp's lifecyclestage and hs_lead_status properties (or equivalent custom fields), and preserve the original stage in a custom field camp_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Camp Company records map directly to Salesforce Account. The company domain becomes the Account Website field and serves as the dedupe key during import. Account is created before any Contact import so that the AccountId Lookup relationship is satisfied at Contact insert time. Industry, employee count, and annual revenue fields map from their Camp equivalents.

Camp Deal records map to Salesforce Opportunity. The Camp dealstage property maps to Salesforce StageName, and the pipeline assignment maps to a Salesforce Record Type and Sales Process that we configure before migration. Deal value, close date, and owner transfer directly. Closed-Lost and Closed-Won reason fields from Camp custom properties become Salesforce Loss Reason and custom win_reason__c fields.

Each Camp pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Camp to Salesforce StageProbability with rounding to the nearest integer allowed by Salesforce. Stage names are mapped via a customer-approved stage-to-stage table during scoping.

Camp Automation Campaigns group email, SMS, social post, and push notification assets under a single parent record. Salesforce does not have a native multi-channel Campaign object, so we create a named Campaign record as the parent and tag each channel-specific activity record (email Tasks, Event records for meetings, SMS Tasks, social Tasks) with a campaign reference field. The unified multi-channel view in Camp does not replicate in Salesforce's Campaign UI; the association is preserved through naming conventions and tagging rather than a native parent-child structure.

Camp email templates include subject line, HTML body with inline CSS, and variable placeholders. We export templates as HTML and import them into Salesforce as Email Templates (ContentBuilder or Classic) or as ContentNote records with a custom Template_Type__c field to distinguish them. Variable placeholder syntax is preserved in the HTML body; variable resolution requires Salesforce administration post-migration.

Camp Automation workflows define triggers (form submit, email open, deal stage change) and multi-branch action sequences. We do not migrate workflows as executable Salesforce Flow. Instead, we document the full trigger-action graph during discovery and deliver a written inventory of each active workflow with its trigger type, conditions, action sequence, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds them post-migration.

Camp Automation custom field definitions are not exposed in a public metadata API. We prompt the customer to export the full field list from the Camp UI or provide a screen recording of the Contact, Company, and Deal settings pages before migration begins. Field types (text, date, dropdown, number, checkbox) are mapped to equivalent Salesforce field types. Without this discovery step, incorrect field types in Salesforce can corrupt reporting filters and validation rules that depend on field type.

Camp Automation tags are flat label objects applied to Contacts and Deals. We preserve the full tag taxonomy and reapply all tags at import time. Tags are mapped to Salesforce Multi-Select Picklist fields on the target object, or to Salesforce Topics with TopicAssignment records if the customer uses Topics for content classification. The customer chooses the tag strategy during scoping.

Camp Automation Owners map to Salesforce User records by email address match. We resolve owners on email and assign records to the corresponding User in Salesforce. Users that do not exist in Salesforce are held in a reconciliation queue; the customer's admin provisions the missing Users before record import resumes. Inactive users are created as inactive in Salesforce to preserve ownership history.

Camp landing page forms and inline web forms are exported with field configurations and submission data. Form records are migrated as Salesforce Custom Objects because form structures vary significantly across platforms and Salesforce does not have a native equivalent to Camp's form builder. Form submission data is imported as Custom Object records linked to the parent Contact or Lead.

Camp call engagements map to Salesforce Task with TaskSubtype = Call. Call disposition, duration (CallDurationInSeconds), and any recording URL preserved in custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original Camp timestamp. WhoId points to the converted Lead or Contact; WhatId points to the related Opportunity or Account.

Camp email engagements migrate to Salesforce EmailMessage records linked to an Activity Task record. The WhoId on Task points to the converted Lead or Contact; WhatId points to the related Opportunity or Account. Email body content, subject line, and timestamp transfer directly. Attachments migrate as ContentDocumentLink records attached to the EmailMessage.

Camp meeting engagements map to Salesforce Event. StartDateTime, EndDateTime, Location, and subject preserve. Attendee mapping links to EventRelation records pointing at the converted Leads, Contacts, and Users. Recurring meeting series in Camp are documented as separate Event records with a recurrence_reference__c field rather than Salesforce Series.

Camp Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity. Note body migrates as rich text with image attachments preserved as separate ContentDocument records. Created date and created by are preserved from the Camp source.

Camp task engagements map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Task assignment migrates by resolving Camp owner_id to Salesforce OwnerId via the User mapping. Open and completed task states transfer directly. Tasks without a parent reference are attached to the Contact or Account as WhoId or WhatId respectively.

Camp SMS, push notification, and social post engagements have no native Salesforce equivalent. We import these as Task records with a custom field camp_channel__c (values: SMS, Push, Social) and a campaign_reference__c linking back to the parent Salesforce Campaign. Content body transfers to Task Description. These records appear in the Activity timeline but do not replicate the Camp multi-channel campaign UI view.

Any Camp Automation custom objects discovered during schema mapping migrate to Salesforce Custom Objects with matching API names (plus __c suffix per Salesforce convention). We pre-create the destination schema including all custom fields, lookup relationships, and validation rules before any data import. Custom objects that reference standard objects (Contacts, Accounts, Opportunities) are imported after the parent standard records are present in Salesforce to satisfy lookup constraints.