Migrate from SalezShark to Microsoft Dynamics 365 Sales

Discovery and export coordination planning

We audit the SalezShark account to document the object inventory, custom field definitions, pipeline configuration, active workflow count, and exportable activity volume. We then plan the CSV export schedule with the customer's SalezShark admin, determining whether exports can be run as single large batches or require date-range filtering to avoid timeout. We also confirm the target Dynamics 365 edition and licensing count, since Sales Professional ($65/user) covers most migrations and Sales Enterprise ($105/user) is required only if the customer needs advanced AI features or custom relationship behavior.

Schema design and custom attribute creation

We design the Dynamics 365 destination schema based on the SalezShark custom field inventory. This includes creating any custom attributes on Contact, Account, Lead, and Opportunity that have no direct Dynamics equivalent, configuring the Sales Process and Record Type for each SalezShark pipeline, and setting up OptionSet definitions for picklist fields. Schema changes deploy to a Dynamics Sandbox first for validation. We also document the field map as a written artifact that maps each SalezShark field to its Dynamics attribute name and any transformation logic applied during import.

CSV extraction and transformation

We coordinate with the customer to run CSV exports from SalezShark in the agreed batches. Each exported CSV is validated for row count, column completeness, and encoding issues before transformation. During transformation, we apply the field map: standard fields map directly by name, custom fields map by label or API name lookup, picklist values map to the Dynamics OptionSet values, and date formats convert to the Dynamics-required ISO 8601 format. Owner email addresses are held as a lookup reference rather than a raw ID, to be resolved against the Dynamics User table in the next phase.

Sandbox migration and reconciliation

We run a full test migration into the customer's Dynamics Sandbox using production-like record volumes. The customer reconciles record counts and spot-checks 20-30 records against the SalezShark source for field accuracy. Owner lookup failures are identified at this stage and the customer provisions the missing Dynamics Users. The Sandbox validation also confirms that the Sales Process and Record Type configuration produces the expected pipeline stages in the Dynamics UI. Sign-off on the Sandbox results authorizes the production migration to proceed.

Production migration in dependency order

We run production migration in record-dependency sequence: Accounts first (parent for Contacts), then Contacts with AccountId resolved, then Leads with any unconverted status preserved, then Opportunities with AccountId and OwnerId resolved and RecordTypeId assigned. Tasks and Activities import last after all parent records are confirmed. Owner resolution against the Dynamics User table is applied as each record batch processes. Each phase emits a reconciliation row-count report before the next phase begins.

Cutover, validation, and automation handoff

We freeze SalezShark write access during the final cutover window and run a delta migration of any records modified since the last export batch. We deliver the Workflow Automation configuration document (trigger, conditions, actions, and Power Automate equivalent recommendation) to the customer's Dynamics admin. We provide a one-week hypercare window for reconciliation issues and do not charge for record re-imports caused by pre-validated mapping errors. Power Automate workflow rebuild, Microsoft 365 integration activation (Outlook tracking, Teams embedding, SharePoint document management), and Dynamics 365 Copilot configuration are outside standard migration scope and are handled as separate engagements.