Migrate from Prophet CRM to Salesforce Sales Cloud

Prophet Contacts map directly to Salesforce Contacts. Prophet's bidirectional Outlook Contact sync must be frozen before extraction and re-enabled post-import; skipping this step creates duplicate Contact records when Outlook re-syncs against the newly migrated Salesforce contacts. We export contact name fields, email, phone, title, address, and owner. Custom fields on Contact migrate to Salesforce custom Contact fields after the department-template schema audit completes.

Prophet Companies map to Salesforce Accounts. Standard fields (industry, address, employee count, revenue, website) export cleanly from the OData API. Company is the parent record of Contact, so Accounts are created first during migration so that AccountId is resolved at Contact insert time. Industry classification maps to the Account Industry picklist; employee count and revenue map to NumberOfEmployees and AnnualRevenue.

Prophet Opportunities map to Salesforce Opportunities with name, amount, close date, probability, owner, and stage exported from the OData API. Stage assignments export as part of the record and are mapped to Salesforce StageName during the transform. We flag any Opportunity without a valid Company reference for manual AccountId assignment before production load. Closed-Lost and Closed-Won status migrate as-is; probability percentages map to StageProbability in Salesforce.

Prophet pipeline stages are configurable per organization and vary by department even within a single Prophet installation. We capture the full stage list during scoping and map each stage name to a Salesforce StageName value and probability. Each stage gets a corresponding Salesforce Sales Process that whitelists only the valid stages for that pipeline. Stage ordering is preserved via SortOrder in the Sales Process.

Prophet email tracking engagements migrate to Salesforce EmailMessage records (the email content) linked to a Task record (the activity timeline entry). The WhoId on Task points to the migrated Contact; WhatId points to the related Opportunity or Account. Email body, subject, timestamp, and direction (sent/received) transfer. We use the Salesforce Bulk API 2.0 for large email histories because the volume exceeds what the REST API can handle within rate limit windows.

Prophet task engagements map to Salesforce Task records with Status, Priority, Subject, ActivityDate, and owner preserved. Task assignment migrates by resolving the Prophet owner email to Salesforce OwnerId via the User mapping. TaskSubtype defaults to Task for plain tasks; call tasks set TaskSubtype=Call with CallDisposition and CallDurationInSeconds migrated to custom Task fields.

Prophet appointment engagements map to Salesforce Event records with StartDateTime, EndDateTime, Subject, Location, and description preserved. EventRelation records link attendees to the migrated Contact or Opportunity. Activity timeline ordering is preserved by setting ActivityDateTime to the original Prophet timestamp. Recurring appointments map as individual Event records; recurrence metadata is not preserved as Salesforce Events do not have native recurrence on non-Calendar-standard objects.

Prophet call logs migrate to Salesforce Task with TaskSubtype = Call. Call duration, disposition code, and notes transfer to custom fields on the Task. The original call timestamp becomes ActivityDate. Call recording URLs stored in Prophet become a URL custom field on the Task for reps to access playback in Salesforce.

Prophet custom fields on Contact, Company, and Opportunity are mapped to Salesforce custom fields of equivalent data type. The department-template audit is mandatory because custom field schemas vary by department even on the same object; fields invisible in the default Company or Contact view will be dropped if the audit is skipped. We enumerate all field names, types, and department assignments during scoping and create Salesforce custom fields in the destination org's schema before any data loads begin.

Prophet file attachments on Companies, Contacts, and Opportunities migrate as Salesforce ContentDocument records via the ContentVersion upload workflow. We extract attachment metadata (filename, MIME type, file size) and URL from the OData export, download each file, and upload via the Salesforce ContentVersion API. ContentDocumentLink records link each file to the parent Contact, Account, or Opportunity. Files over 25 MB trigger chunked upload handling.

Prophet departments are a first-class concept with custom templates and configurable cross-department read/write access. Salesforce has no native department object. We export the department assignment on each record and populate a custom picklist field Department__c on the relevant Salesforce object. Role-based access and cross-department visibility are documented in the migration handoff for the customer's admin to implement via Salesforce Profiles, Permission Sets, and Sharing Rules.

Prophet Owner references on Contacts, Companies, and Opportunities resolve by email match against the Salesforce User table in the destination org. Any Prophet Owner without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Salesforce Users are created as inactive to preserve historical owner attribution without granting login access.

Prophet's group email sending and thread tracking groups related emails under a single thread view. We preserve thread grouping by creating a parent Task record representing the thread, then attaching individual EmailMessage records as children. The thread subject becomes the parent Task subject. This preserves the conversation view that sales reps rely on without replicating a thread object that Salesforce does not natively support.

Prophet group email campaigns map to Salesforce Campaign records with CampaignMembers representing each recipient. The Campaign Type is set to Email Newsletter or Email Blasting depending on the group send type. Individual email tracking events (opens, clicks, bounces) from Prophet are not directly migratable to Salesforce Campaign Member Status because Salesforce tracks engagement at the Campaign level; we document the engagement data for import into a marketing analytics layer if the customer has Marketing Cloud Account Engagement.