Migrate from ActiveDEMAND to Salesforce Sales Cloud

ActiveDEMAND Contacts route to Salesforce Lead or Contact based on a lifecycle rule defined during scoping. Contacts with a Senior Living prospect lifecycle stage map to Lead; contacts at qualification stage or beyond map to Contact attached to an Account. The original ActiveDEMAND lifecycle stage, community assignment, and lead quality rating migrate to custom fields (ad_original_lifecycle__c, ad_community__c, ad_lead_quality__c) for audit and reporting.

ActiveDEMAND Companies map to Salesforce Account. Company name becomes Account.Name, city and state map to BillingAddress fields, and phone maps to Phone. Where multiple ActiveDEMAND Companies share the same domain or address, we merge duplicates using the destination org's duplicate rules before final import.

ActiveDEMAND Campaigns (email, funnel, multi-channel, event) map to Salesforce Campaign. Campaign type distinction (Email, Event, Digital Ads, etc.) maps to the Salesforce Campaign Type picklist. Campaign membership (which Contacts are members) migrates as CampaignMember records linked to the appropriate Lead or Contact. Campaign status and dates preserve through the migration.

ActiveDEMAND Call Tracking records include source number, destination number, duration, recording URL, disposition, and lead quality rating. We map these to Salesforce Task records with TaskSubtype set to Call. Call duration maps to CallDurationInSeconds, recording URL to CallObject, and disposition to a custom Task field. If the destination includes Service Cloud Voice, call transcripts also migrate as ContentNote records linked to the Task.

ActiveDEMAND website chat conversations migrate as Task records (one per conversation) with conversation text preserved in the Task Description field. If the conversation includes email exchanges, those messages migrate as EmailMessage records. The original contact link preserves through the Contact-to-Lead/Contact resolution.

ActiveDEMAND Appointment and Tour booking records map to Salesforce Event. StartDateTime, EndDateTime, and Location preserve. The linked Contact resolves through the Contact-to-Lead/Contact mapping. Appointment status (Confirmed, Cancelled, Completed) maps to a custom Event status field. For Senior Living tours, the community reference maps to ad_community__c on the Event record.

ActiveDEMAND Brand Custom Field schemas vary per brand/tenant and are not consistent across accounts. We export the full field schema (field name, type, picklist values if applicable) before exporting any Contact records, then pre-create equivalent custom fields in Salesforce with matching API names (ad_fieldname__c). Custom field types map to Salesforce field types: text to Text(255), date to Date, picklist to Picklist, checkbox to Checkbox, number to Number.

Where ActiveDEMAND supports Company-level Brand Custom Fields, we replicate those as custom fields on the Salesforce Account object using the same pre-schema approach. Field types and picklist values match the ActiveDEMAND definition.

ActiveDEMAND Contact Lists and Segments export as static lists of contact IDs. We reconstruct these in Salesforce as Campaign membership (for marketing list equivalents) or as Tags on the Contact/Lead record via a custom multi-select picklist. The customer chooses the strategy during scoping based on how lists are used in Salesforce.

ActiveDEMAND Forms and their field definitions export as structured metadata. The form HTML/CSS is preserved as an attachment reference for manual re-creation in Salesforce Web-to-Lead, Experience Cloud forms, or a third-party form tool. Field-level mapping notes are documented in the handoff package so the admin knows which ActiveDEMAND form fields feed which Salesforce fields.

Landing page templates and content export as structured data with URL references. Styling and script embeds require manual reassembly in the destination CMS or Salesforce Experience Cloud. We provide a complete URL redirect map so that existing ActiveDEMAND landing page URLs can point to Salesforce-hosted pages or a replacement landing page tool.

ActiveDEMAND Funnel Builder multi-stage journeys export with stage labels and contact-stage assignments. Stage labels map to Salesforce Opportunity stage values within a configured Pipeline (Record Type). Contact-stage history preserves as a custom multi-select picklist on the Contact or as Opportunity history if a Deal is created per funnel stage.

ActiveDEMAND Owners (assigned to Contacts, Campaigns, Deals) resolve by email match against the Salesforce User table. Owners without a matching Salesforce User go to a reconciliation queue for admin provisioning before record import. Active or inactive status on the Salesforce User matches the original ActiveDEMAND Owner status.

File attachments to Contacts, Campaigns, or Forms export by URL reference. We download files to local storage and re-upload to Salesforce as ContentDocument records linked via ContentDocumentLink to the parent Contact, Account, or Campaign. Filename and MIME type preserve.

ActiveDEMAND Automated Workflow definitions are complex JSON structures that do not map to Salesforce Flow. We export workflow names, step counts, trigger conditions, and action types as metadata notes attached to the relevant Contact or Campaign records. A written Workflow Inventory Document is delivered to the customer's admin for manual rebuild in Salesforce Flow or a marketing automation tool.