Migrate from Saleshiker to Microsoft Dynamics 365 Sales

Saleshiker Leads map directly to Dynamics 365 Lead. We map firstname, lastname, phone, email, source, status, and owner to their Dynamics 365 equivalents, preserving phone number exactly and setting leadqualitycode based on Saleshiker's lead status. Any custom properties that do not map to standard Dynamics fields are preserved in a custom field hs_custom_properties__c as a JSON blob for reference and post-migration admin review.

Saleshiker Contacts map to Dynamics 365 Contact with standard field mapping: Phone to Telephone1, Email to EmailAddress1, Website to WebsiteURL, and owner to systemuserid. We resolve the Organization-to-Account lookup so every Contact attaches to the correct parent Account at import time. Duplicate or unmapped Organizations are held in a reconciliation queue for the customer's admin to resolve before Contact import completes.

Saleshiker Organizations map 1:1 to Dynamics 365 Account. The Organization name becomes Account Name, domain becomes Website, and address fields map to address composites. Organization is the parent entity for Contacts, so we migrate Organizations first to satisfy the AccountId lookup on every Contact record during import.

Saleshiker Deals map to Dynamics 365 Opportunity. The pipeline stage from Saleshiker maps to a Dynamics 365 Opportunity Stage via a customer-confirmed mapping table we build during scoping. Deal value migrates to Amount, expected close date to CloseDate, and owner to OwnerId. Any Saleshiker deal stage with no matching Dynamics stage is flagged in the mapping report for admin confirmation before import.

Saleshiker's named pipeline structures map to Dynamics 365 Record Types on Opportunity, each paired with a corresponding Sales Process that whitelists the mapped stage values. Stage ordering and probability percentages migrate from Saleshiker to the Sales Process stage definition. We configure the Record Type and Sales Process in a Dynamics 365 Sandbox before production migration.

Saleshiker Quotes map to Dynamics 365 Quote. We migrate quote headers including total, status, and expiration date, along with line items referencing Products. Quote requires an active Pricebook on the Opportunity parent, so we validate Pricebook presence before Quote import and flag any orphaned quote records. Signed Quote PDFs are preserved as SharePoint document attachments linked to the Quote record.

Saleshiker Invoice headers and line items migrate as Invoice records in Microsoft Dynamics 365 Sales with payment status and totals preserved. Microsoft Dynamics 365 Sales does not include a full Accounts Receivable accounting engine; if the customer requires AR/AP accounting flows, we recommend a parallel Business Central engagement. Payment reconciliation history that depends on Saleshiker's internal accounting state does not carry over.

Saleshiker Products map to Dynamics 365 Product2 with name, SKU, price, and description preserved. The Saleshiker SKU maps to Product Code. We create Standard Pricebook entries during migration so Products are immediately available for Quotes and Opportunities without manual price book configuration.

Saleshiker Tasks migrate to Dynamics 365 Task with title, due date, status, and assignment preserved. We resolve owner references by email match against Dynamics 365 Users. Tasks with no valid owner are assigned to the migration system user and flagged for admin reassignment post-migration.

Saleshiker Events migrate to Dynamics 365 Event with start and end datetime, title, and location preserved. Recurrence patterns carry over as Event recurringpattern values. Owner resolution follows the same email-match strategy used for Tasks and Contacts.

Saleshiker file attachments are downloaded from Saleshiker's storage and uploaded to the SharePoint site linked to the Dynamics 365 organization. We create SharePointDocumentLocation records to re-establish the attachment-to-record linkage so files remain accessible from within Dynamics 365 without storing binary blobs in Dataverse.

Saleshiker custom field values that do not map to standard Dynamics 365 field types are serialized into a custom Dynamics 365 field hs_custom_properties__c on the Lead and Contact objects as a JSON object. This preserves the full property set without forcing a schema redesign. The customer reviews this field post-migration and promotes frequently-used properties into typed Dynamics fields as adoption grows.