Migrate from Camp Automation to Microsoft Dynamics 365 Sales

Camp Automation Contacts with no associated Deal or pipeline stage map to Dynamics 365 Lead. Contacts with an active Deal and pipeline stage map to Dynamics 365 Contact attached to the corresponding Account. We resolve the split using Camp's pipeline and dealstage properties, and preserve the original contact properties (email, phone, company association) as custom fields on both Lead and Contact for reconciliation. Owner assignment uses email-based matching to the corresponding Dynamics 365 User.

Camp Automation Company records map directly to Dynamics 365 Account. The company domain becomes the Account Website field and is used as the deduplication key during import. Account is created before any Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. Industry and size fields map to standard Account fields where present in Camp; custom fields migrate via schema discovery.

Camp Automation Deal records map to Dynamics 365 Opportunity. The Deal pipeline maps to a Microsoft Dynamics 365 Sales Process (Record Type), and dealstage maps to the corresponding StageName via a named stage-to-stage mapping defined during scoping. Deal value, close date, and owner assignment transfer directly. Closed-Lost and Closed-Won custom properties become custom fields on Opportunity for historical reporting continuity.

Camp Automation Campaigns group email, SMS, social post, and push notification assets under a single parent. We create one Dynamics 365 Campaign per Camp parent and separate CampaignActivity records per channel (email, SMS, social). Channel-specific records are linked to the parent Campaign via the campaignid reference. The Dynamics 365 UI will not display a unified multi-channel view; we document the association through a campaign_reference__c tag on each activity so admins can reconstruct the original grouping in reporting.

Camp Automation email templates (subject, HTML body, variable placeholders) migrate as Dynamics 365 Email Templates with inline CSS preserved. Variable syntax from Camp is documented in a migration notes field and re-mapped to Dynamics 365 token syntax by the admin during any email send sequence setup. HTML content and asset URLs transfer without transformation.

Camp Automation Automation workflows (triggers: form submit, email open, deal stage change; actions: email send, task creation, tag application) do not migrate as executable code because the trigger-action model differs from Power Automate. We audit every active Camp Automation workflow and deliver a written inventory with trigger type, conditions, action sequence, and a Power Automate template recommendation for each. The customer or a Dynamics partner rebuilds these post-migration in Power Automate.

Custom fields on Contacts, Companies, and Deals are discovered via customer-provided schema export from the Camp UI (Contact, Company, and Deal settings pages) or screen recording. Field types (text, date, dropdown, number) map to equivalent Dataverse field types. We pre-create the destination schema in a Dynamics 365 Sandbox before production migration. Fields with incorrect types in the destination can corrupt reporting filters, so type accuracy is validated against the schema discovery before any import batch runs.

Camp Automation tags (flat label objects applied to Contacts and Deals) migrate as new text fields on the corresponding Dynamics 365 entity or as Option Set values where the tag taxonomy is finite and controlled. Tags that do not exist in Dynamics are created as new fields automatically during migration. The customer selects the tag strategy during scoping: multi-select for dynamic segmentation, Option Set for controlled taxonomy.