Migrate from SalesSeek to Microsoft Dynamics 365 Sales

SalesSeek Organizations map directly to Microsoft Dynamics 365 Sales Accounts. The Organization name maps to Account Name, physical address fields map to Address composite fields, and industry taxonomy aligns with the standard Industry picklist in Dynamics 365. We use Organization ID as the dedupe key during import. Account is created before any Contact import so that the parent Account lookup is satisfied at the moment of Contact insert. Custom fields on Organization (text, number, date, or dropdown types) map to custom fields on Account, with dropdown options explicitly matched to Dynamics 365 picklist values.

SalesSeek People map to Dynamics 365 Contacts. Each Person's linked Organization ID resolves to the target Account ID at migration time, establishing the Contact-to-Account parent relationship. Email address, phone, job title, lifecycle stage (if present as a custom property), and owner assignment migrate directly. If SalesSeek lifecycle stage is present as a custom field, we preserve it in a custom field original_lifecycle_stage__c on the Contact for reporting continuity. People without a linked Organization are imported as Contacts with no parent Account and flagged for manual review.

SalesSeek Deals map to Dynamics 365 Sales Opportunities. Deal name maps to Opportunity Name, monetary value maps to Amount, expected close date maps to Close Date, and probability maps to a custom probability field or the standard Probability field if the probability percentages align with the target Sales Process. The Deal's linked Organization resolves to the parent Account; the Deal's linked Person resolves to the parent Contact if one exists. Stage transitions and closed-lost/closed-won timestamps are preserved.

Each SalesSeek named pipeline maps to a Dynamics 365 Record Type on Opportunity, paired with a Sales Process that scopes the valid stage values to that pipeline. This preserves the SalesSeek multi-pipeline structure where different lines of business use different stage sequences. We export each pipeline's stage order, labels, and probability percentages during scoping and configure the Sales Process in the target Dynamics 365 environment before Deal migration begins.

SalesSeek pipeline stages are configurable enumerations with label, sequence order, and probability. These map to Dynamics 365 Sales Process Stage entries. We preserve stage labels exactly (including any non-standard names specific to the customer's pipeline) as Stage Name values, and we set Stage Probability to match SalesSeek's configured percentages, rounded to the nearest integer allowed by Dynamics 365. Stage renaming or reordering post-migration is a manual admin task.

SalesSeek Tasks map to Dynamics 365 Tasks with Subject, Description, Due Date, Status, Priority, and Owner preserved. Completed and open tasks export equally. Task assignment migrates by resolving the SalesSeek owner's email against the target Dynamics 365 User table. Tasks linked to a specific Person or Organization resolve their parent record ID at migration time and set the Regarding (object) lookup accordingly.

SalesSeek engagement activities (calls, emails, meetings, notes) migrate as Task or Event records in Dynamics 365. Call engagements set TaskSubtype to Call with duration stored in a custom field. Email engagements store content in the Task Description or a custom EmailContent field since Dynamics 365 Sales stores emails natively in EmailMessage objects only when Exchange integration is active. Meeting engagements migrate as Event records with StartDateTime, EndDateTime, and Location. We preserve the original engagement timestamp to maintain activity timeline ordering.

SalesSeek custom fields on Organizations, People, and Deals map to custom fields on the corresponding Dynamics 365 object (Account, Contact, Opportunity). Field types translate: text to Single Line of Text or Multi Line of Text, number to Whole Number or Decimal Number, date to Date Only or Date and Time, and dropdown to Picklist. Dropdown options require explicit value mapping — we generate a custom field mapping spreadsheet during scoping that lists each field name, SalesSeek option values, and the proposed Dynamics 365 picklist values for customer review before migration.

SalesSeek filters segment records into Groups and are not accessible for update or delete via the API. Filters not associated with a Group are periodically cleaned up by SalesSeek's system. During scoping, we identify all active filters and export their definitions (field criteria, operators, values). We recreate these as Saved Views in Dynamics 365 Sales using the equivalent filter criteria against Account, Contact, and Opportunity fields. Note that any orphaned SalesSeek filters may have already been deleted before migration begins.

SalesSeek Groups are collections of records used for filtering and sharing. We export group membership and recreate groups as Dynamics 365 Teams or Security Roles depending on whether the group controls data access (Security Role) or collaboration visibility (Team). The customer's admin selects the appropriate strategy during scoping. Group membership mapping is applied as a post-import step after User records are reconciled.