Migrate from Function 365 to Salesforce Sales Cloud

Function 365 contacts map directly to Salesforce Contacts. Salesforce requires an AccountId on every contact — if the Function 365 contact has no associated company, we attach it to a default 'Unassigned Account' record or flag it for manual resolution before migration commits.

Function 365 records flagged as leads or prospects with no closed-won status route to Salesforce Lead. Records with an active account relationship and deal history route to Salesforce Contact. The split is determined by the presence of a sales transaction or opportunity association in the source record.

Function 365 accounts and companies map to Salesforce Accounts. Parent-account hierarchies in Function 365 preserve as Salesforce ParentId. Multi-company associations (N:N in Function 365) collapse to a primary AccountId plus Account Contact Relations for secondary affiliations. This ensures a single primary relationship in Salesforce while preserving secondary affiliations.

Function 365 opportunities and deals map to Salesforce Opportunities. Each pipeline in Function 365 becomes a Salesforce Sales Process keyed by Record Type — this is the most impactful structural decision because stage pick-list values, probabilities, and forecast categories are scoped per record type.

A single Function 365 pipeline maps to one Salesforce record type with its own sales process. Multiple Function 365 pipelines require multiple Salesforce record types, each needing a page layout, profile assignment, and validation rules pre-created in Salesforce before data lands.

Stage names map value-by-value per Salesforce record type. Stage probability and forecast category (Open, Commit, Best Case) are re-applied based on Salesforce's stage-history model. Function 365 stage-entry timestamps are preserved as custom datetime fields for reporting continuity and historical tracking.

Function 365 email activities map to Salesforce Tasks with Type='Email'. Call activities map to Tasks with Type='Call'. Meetings map to Salesforce Events with original start and end times. Notes migrate as Salesforce Notes — rich-text body preserved. Original timestamps and owner IDs carry over.

Function 365 custom entities and Dataverse custom tables map 1:1 to Salesforce custom objects (CustomObject__c). Custom-entity relationships that use Dataverse N:N junction tables require Salesforce junction objects — we surface this in the migration plan and pre-build the junction schema before the load.

Function 365 users are resolved by email match against Salesforce users. Unmatched owners are flagged before migration — the team either invites them to Salesforce first or assigns their records to a designated fallback owner. No record lands without a valid Salesforce OwnerId.

File attachments on Function 365 records are downloaded and re-uploaded to Salesforce Files, linked to the target record via ContentDocumentLink. Salesforce's default 25MB per-file limit applies; files exceeding this are flagged, chunked into smaller segments, or skipped based on your pre-defined handling instructions.

Function 365 workflow definitions, Power Automate flows, and business rules do not migrate automatically. We export all rule definitions as JSON and structured documentation so your Salesforce admin can rebuild them in Flow. This is a manual step requiring careful planning — allocate 2–4 weeks of admin time for complex automation rule sets.

Dynamics 365 SSRS reports and Power BI dashboards do not migrate directly. The underlying migrated data is fully available in Salesforce, but all reports and dashboards must be rebuilt from scratch. Salesforce Reports provide equivalent standard functionality, while CRM Analytics (Tableau) handles advanced analytical dashboards and visualizations.