Migrate from Prophet CRM to Nutshell

Prophet Contact records map to Nutshell Person. We freeze Outlook bidirectional sync before extraction to prevent duplicate records post-import. Standard fields (name, email, phone, address) map cleanly. If the Prophet Contact has a linked Company record, we reference the Company by name lookup in Nutshell's Companies table during import to preserve the account association. Custom fields on Contact migrate to Nutshell's custom Person fields after the custom field audit enumerates all field names and types.

Prophet Company records map to Nutshell Company. Standard fields including industry, address, employee count, and revenue export cleanly. Industry classification maps from Prophet's taxonomy to Nutshell's industry picklist values. Nutshell Company must be created before any Person with a Company association imports, so we sequence Companies first in the import order to satisfy the lookup dependency.

Prophet Opportunity records map to Nutshell Deal. Deal name, value (monetary amount), expected close date, probability, owner, and pipeline stage migrate as Deal fields. Nutshell's Deal type determines the stage list we apply; we configure the Nutshell pipeline stages before migration to match the stage names and order from Prophet's scoping audit.

Prophet pipeline stages are configurable per department, meaning the stage list can vary across departments within the same organization. We capture the full stage list during scoping, normalizing stage names that differ only by department prefix. The normalized stage list becomes the Nutshell Deal pipeline configuration we deploy before any Deal records import.

Prophet Activities include email tracking, tasks, appointments, and call logs linked to Contacts and Opportunities. There is no bulk export endpoint, so we paginate via OData and batch in groups of 500 to 1,000. Completed activities and meeting notes migrate to Nutshell Task or Note records linked to the corresponding Person or Deal via Nutshell's activity association fields. We preserve the original timestamp by setting the activity date to the Prophet recorded date.

Prophet supports custom fields on Companies, Contacts, and Opportunities, with additional per-department template customization that can make the effective field schema vary by department. We include a mandatory custom field audit step in every Prophet CRM migration, enumerating all field names, types, and which departments use which templates. We then map these to Nutshell's custom field system, normalizing picklist values and handling any Prophet-specific field types (such as department-linked fields) as text fields in Nutshell or as a separate tagging approach if the customer requires the data.

Prophet stores file attachments on Companies, Contacts, and Opportunities. We extract attachment metadata and URLs from the OData export and upload files to Nutshell via its file attachment endpoint, associating each file with the target Person, Company, or Deal record. File content types and original filenames are preserved during upload.

Prophet departments are a first-class concept with custom templates and configurable cross-department read/write access. Nutshell does not have an equivalent multi-department hierarchy with separate field schemas per team. We map department assignments on records to a Team or tag field in Nutshell, preserving which department originally owned the record. The customer chooses whether to use Nutshell's native team feature or a text-based department tag during scoping.