Migrate from Prospects CRM to Microsoft Dynamics 365 Sales

Prospects CRM contacts migrate to D365 Contact records. D365 requires each Contact to have an AccountId pointing to a parent Account — contacts without a primary company in Prospects CRM are attached to a placeholder 'Unassigned Account' record, or your team specifies a default company rule for migration.

Prospects CRM Company becomes D365 Account. The Domain field maps to Account.Website. Industry pick-list values require value-by-value mapping because Prospects CRM and D365 use different industry taxonomies. AnnualRevenue and NumberOfEmployees map directly if populated in Prospects CRM. Any custom company-level fields also migrate as custom Account attributes, with field-level validation confirming data type compatibility before loading.

Prospects CRM Deal migrates to D365 Opportunity. The deal name becomes Opportunity.Name, amount maps to Amount, close date maps to CloseDate, and stage maps to StageName. D365 Opportunity requires an AccountId — Accounts must be migrated before Deals so foreign keys resolve correctly.

Prospects CRM pipelines become D365 Business Process Flows. Each pipeline requires a separate BPF in D365, and the pipeline stage values map to an Option Set on the Opportunity entity. Stage-entered timestamps are preserved as custom datetime fields on the Opportunity record.

Prospects CRM activities (calls, emails, meetings) migrate to D365 Task and Appointment records. The activity subject, description, and original created date are preserved. Task owner is resolved by email match against D365 SystemUser records — unmatched owners are flagged before migration commits.

Prospects CRM notes migrate as D365 Annotations. Rich-text formatting is preserved where D365 supports it. Notes attached to specific records (Contact, Account, Deal) carry their parent record lookup in D365 to maintain the original association context. Any embedded images or file links within notes are extracted and migrated as separate Annotation attachments, preserving the original file references for audit continuity.

File attachments from Prospects CRM records are migrated as D365 Annotations with file attachments, or re-hosted in D365's SharePoint or OneDrive integration depending on your configured document management setup. FlitStack confirms the target storage location before migration runs. Attachment metadata including original file names, creation dates, and owner information is preserved in D365's Annotation entity fields to support post-migration auditing and traceability.

Prospects CRM products migrate as D365 Product records. Product name, product code, description, and pricing information (list price, standard cost) map to D365 Product fields. Products must exist in D365 before OpportunityProduct line items can reference them. FlitStack validates product ID uniqueness and currency settings against your D365 base currency configuration before loading to prevent validation errors.

Prospects CRM custom fields on Contact, Company, Deal, or Activity migrate to D365 custom fields on the corresponding entity. D365 custom fields are created via the D365 solution framework before data loads. FlitStack delivers a field creation checklist as part of the migration plan.

Prospects CRM custom objects (if your plan includes them) migrate to D365 custom tables via Dataverse. N:N relationships between custom objects require junction tables in D365 — your FlitStack plan documents the relationship model and creates the junction schema before migration.

Prospects CRM users and deal owners are resolved by email match against D365 SystemUser records. If a Prospects CRM owner has no corresponding D365 user, records are assigned to a fallback owner your team designates, and the original owner email is preserved in a custom field for audit purposes.