Migrate from Sierra Interactive to Microsoft Dynamics 365 Sales

Sierra leads map directly to Dynamics 365 Lead records. Phone, email, address, and source information transfer as standard Lead fields. Owner assignment resolves via email match to Dynamics users. During the migration, we validate each mapped field against the target schema, preserve the original creation timestamp, and flag any missing required fields for manual correction before final load.

Sierra leads that have converted to clients (transaction closed) map to Dynamics Contact records, preserving the contact's name, email, phone, and company association as an Account lookup. The mapping also retains the original Sierra lead ID in a custom field to support traceability and future reconciliation. Any additional custom fields on the Sierra lead are transferred to the Contact record using corresponding custom columns created in Dataverse.

Sierra company records map to Dynamics Account. Company name, website, phone, address, and industry fields transfer. Parent-company hierarchies map to Account.ParentId where applicable. During migration, we validate each company record against the target Dataverse schema, preserve the original creation date, and map any custom fields such as rating or territory to custom columns on the Account entity.

Sierra deals map to Dynamics Opportunities. Deal name becomes Opportunity.Name, amount transfers to Amount, close date maps to CloseDate, and pipeline stage maps to StageName with value mapping per stage. All custom deal fields such as property address, listing ID, or commission split are migrated to custom Opportunity columns. The original deal creation timestamp is preserved as CreatedOn, and owner assignment follows email matching to ensure continuity.

Sierra deal pipelines become named Sales Processes in Dynamics 365 Sales. Each pipeline requires a corresponding Sales Process so stage values are scoped correctly per deal type. During migration, we create each Sales Process in Dataverse with the same stage names and probability weights defined in Sierra, then link Opportunities to the appropriate process using the SalesProcess field. Any stage-specific custom fields are mapped accordingly.

Sierra saved searches have no native Dynamics equivalent. We create a custom SavedSearch table in Dataverse with fields for search criteria, associated lead, and creation date — preserving the reference data for manual review. The table includes a lookup to Lead, stores search name, criteria text, and filter parameters. After migration, your Dynamics admin can rebuild the search logic with Power Automate triggers based on stored criteria.

Saved listings in Sierra — listing ID, address, price, status — migrate to a custom SavedListing table in Dataverse linked to the associated Lead or Contact record via a lookup relationship. The table stores listing ID, address, price, status (Active, Pending, Sold), and a link to the associated Lead or Contact. After migration, you can build Power Automate flows to alert contacts about status changes or refresh listings.

Sierra lead tasks and activities map to Dynamics Tasks. Subject, description, due date, status, and owner transfer. Original timestamps and task type (call, email, showing) are preserved as custom fields. During migration, we validate each task against the target schema, map the task type to a custom Picklist field, and preserve the original created-on timestamp. Any incomplete tasks are flagged for follow-up after cutover.

Sierra notes map to Dynamics Annotations (the Note entity in Dataverse). Note body, subject, created date, and owner transfer. File attachments on notes re-upload as Dynamics FileAttachments. During migration, we preserve the note creation timestamp as CreatedOn, map the owner via email matching, and ensure any URLs in the note body remain intact. File attachments are uploaded to Dataverse using the file upload API after the note records are committed.

Sierra lead tags have no native Dynamics equivalent. Tags migrate to a multi-select text field (Tags__c) or a custom Tags table with a many-to-many relationship to Lead. During migration, we create the Tags__c column on the Lead entity, populate it with the tag values separated by commas, and preserve the tag list for segmentation. If a Tags table is preferred, we set up a many-to-many relationship using an intersect entity.

Lead source values in Sierra (website, referral, Zillow, Realtor.com) map to a custom Lead_Source_Detail__c field on Dynamics Lead with value mapping for each source label. During migration, we create the field, define the picklist values that match Sierra's source labels, and assign each lead the appropriate value based on the source. If a source does not match any picklist entry, we store it as a text value for admin review.

Sierra Action Plans — automation sequences of emails, texts, voicemails, and tasks — do not migrate. We export Action Plan definitions as a JSON reference document for your Dynamics admin to rebuild as Power Automate flows. The exported JSON contains each plan's conditions, sequence, timing, and recipient criteria. Your admin can use this blueprint to rebuild the automation in Power Automate, focusing on sequences like new‑lead welcome and follow‑up reminders.