Migrate from Prophet CRM to monday CRM

Prophet Contacts map to Monday.com CRM Contacts. The bidirectional Outlook contact sync must be frozen before extraction to prevent duplicate records from re-syncing during migration. We extract contact records via OData pagination (batches of 500-1,000), preserving FirstName, LastName, Email, Phone, Title, and Address fields. The contact's related Company (Account) is resolved via a lookup we run against the Company table before inserting contacts so that the Organization link is satisfied at insert time.

Prophet Companies map to Monday.com CRM Organizations. Standard fields including Industry, Address, Employee Count, and Revenue export cleanly from Prophet's OData endpoints. Industry classification and employee count ranges map to Monday.com's corresponding text or number columns. We export Companies first (before Contacts) so that the Organization lookup on each Contact can be resolved at migration time without separate parent-record lookup passes.

Prophet Opportunities map to Monday.com CRM Deals. Fields including Name, Value (Amount), Close Date, Probability, Owner, and Pipeline Stage transfer directly. Stage assignments export as part of the Opportunity record and map to Monday.com Status Column values. We pre-create the Monday.com Status Column with the exact stage names and probability percentages from Prophet's pipeline configuration so that deal value and probability display correctly in Monday.com's pipeline views immediately after migration.

Prophet pipeline stages are configurable per department, meaning stage names and probabilities can vary across departments even on the same Opportunity object. During the custom field audit, we capture the full stage list per department and design a Monday.com Status Column mapping that either consolidates all departments into one board or creates separate boards per department if the customer requires distinct stage workflows. Stage probability percentages migrate to Monday.com Deal Probability fields where configured.

Prophet email tracking engagements map to Monday.com Activity Items linked to the parent Contact or Deal. There is no bulk export endpoint in Prophet, so we extract via OData pagination in batches, preserving the email subject, body, direction (sent/received), and timestamp. Activity items in Monday.com CRM display in the Emails & Activities section of the Contact or Deal record. We preserve activity timeline ordering by setting the Activity timestamp to the original Prophet engagement timestamp.

Prophet Task engagements map to Monday.com Activity Items with Task type. We transfer Status, Priority, Due Date, and assigned Owner. Task assignment migrates by resolving the Prophet owner reference to a Monday.com team member. Any Task without a matching owner goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Prophet call log engagements map to Monday.com Activity Items with Call type. Call disposition, duration, and any recording URL stored in Prophet custom fields transfer to corresponding Monday.com Activity columns. Activity date ordering is preserved using the original Prophet engagement timestamp.

Prophet file attachments on Companies, Contacts, and Opportunities export as file metadata with URLs from the OData response. We upload files to Monday.com via the platform's file attachment API and link them to the corresponding CRM record. File names and any associated descriptions migrate alongside the binary. We do not migrate Outlook MSG files that contain embedded email threading; those are flagged for manual handoff if they contain material deal context.

Prophet custom fields on Companies, Contacts, and Opportunities migrate to Monday.com Custom Columns on the corresponding CRM Board. The custom field schema in Prophet varies by department template, which means two departments may have different custom fields on the same object. During scoping, we enumerate the complete custom field list per department per object and design Monday.com column configurations that either consolidate all custom fields into a single board (with nullable columns for department-specific fields) or create separate board views per department if the customer requires department-scoped field visibility.