6sense Orchestrations will be sunset in 2026. Starting this spring, we’ll begin rolling communications asking you to migrate all Orchestrations to Intelligent Workflows. You'll be notified by email when your migration window begins. Once notified, you will have 12 weeks to complete the migration. We will provide access resources that help make the process smooth and simple.
Intelligent Workflows, which includes the Audience Workflows (AWF) and Data Workflows (DWF) products, are the much more flexible, automated alternative to Orchestrations. While Orchestrations handles basic automation, Audience and Data Workflows provide more flexibility, visibility, and availability across data, channels, and schedules, especially for data enrichment and marketing activation.
To learn more about the migration, refer to:
Video demos
Refer to the following videos.
Push Segment Names Orchestration migration video
The Push Segment Names Orchestration migration video covers:
Reviewing the existing Orchestration
Pausing the original Orchestration
Using DWF to create a workflow
Mapping profile
Testing the new workflow
Publishing the new workflow
Export Scores Orchestration migration video
The Export Scores Orchestration migration video covers:
Reviewing the existing Orchestration
Pausing the original Orchestration
Reviewing the mapping profile
Using DWF to create a workflow
Testing the new workflow
Publishing the new workflow
Acquire New Contacts migration video
The Acquire New Contacts Orchestration migration video covers:
Allocating credits
Reviewing the mapping profile
Reviewing the existing Orchestration
Using either DWF or AWF to create a workflow
Testing the new workflow
Unpublishing the original Orchestration
Publishing the new workflow
Enrich Records migration video
The Enrich Records Orchestration migration video covers:
Allocating credits
Reviewing the existing Orchestration
Using DWF templates for enrichment
Why you’d use "All accounts" versus "From a segment"
Mapping profile
Testing the new workflow
Unpublishing the original Orchestration
Publishing the new workflow
Create New Accounts migration video
The Create New Accounts Orchestration migration video covers:
Allocating credits
Reviewing the existing Orchestration
Using either DWF or AWF to create a workflow
Consider attaching to a broader, full-funnel workflow if using AWF
Mapping profile
Testing the new workflow
Unpublishing the original Orchestration
Publish the new workflow
Add Audience / Existing Contacts migration video
The Add Audience / Existing Contacts Orchestration migration video covers:
Reviewing the existing Orchestration
Unpublishing and changing the push settings of the original Orchestration
Using either DWF or AWF to create a workflow
Testing the new workflow
Publishing the new workflow
Match Leads to Accounts Orchestration migration video
The Match Leads to Accounts Orchestration migration video covers:
Reviewing the original Orchestration
Unpublishing and changing the push settings of the original Orchestration
Using DWF to create a workflow
Custom match rules
Testing the new workflow using a preview
Publishing the new workflow
FAQ: Orchestrations Migration
What is the date when Orchestrations will be turned off?
The target date for turning off Orchestrations for all customers is December 31st, 2026.
Will customers be required to perform the migration on their own?
There will be no automatic migration, so customers will be required to migrate their own Orchestrations to workflows.
Will there be a Professional Services package that I can buy?
While there is not a specific package for the migration, customers that require additional help can purchase the currently available Intelligent Workflows package, which is fifteen PS hours and two workflows.
How do I know which orchestrations to map to which workflows?
Refer to the following chart:
Orchestrations description | Data Workflows documentation | Audience Workflows documentation | Notes |
|---|---|---|---|
Push segment names | N/A | ||
Enrich records | N/A | ||
Add new contacts from email | N/A | N/A | Not supported in workflows |
Create new accounts | AWF new audience creation templates orcreate workflow from scratch using the Create Accounts in CRMaction node | You can use AWF or DWF workflows, it depends on your preference | |
Match leads to accounts | N/A | ||
Convert leads to contacts | N/A | ||
Add audience | N/A | ||
Acquire new contacts | You can use AWF or DWF workflows, it depends on your preference | ||
Export 6sense scores | N/A | ||
Drive web engagement | N/A | N/A | AI-driven orchestrations are not supported in workflows |
Create new opportunities | N/A | N/A | AI-driven orchestrations are not supported in workflows |
Can orchestrations and IWF workflows run in parallel?
Apart from Predictive Score Export, orchestrations and workflows can run in parallel. Publishing one score export via Data Workflows will disable all existing score exports via Orchestrations. We advise being ready to migrate and publish all score exports via Data Workflows at once to ensure all scores exports continue to export to CRM. For more information, refer to Export Predictive Scores from Data Workflows Templates.
Will migration change user permissions or roles (who can create, publish, or approve workflows vs. legacy orchestrations)?
6sense will not modify the roles and permissions users have. Administrators will need to ensure that the right users have the proper access in Orchestrations to unpublish orchestrations, and the proper access to Audience and/or Data Workflows to configure and publish the workflows replacing legacy orchestrations. For more information on roles and permissions refer to:
Who should I contact if I have a question about my migration?
Reach out to your CSM if you have any questions about when the migration is happening, what you need to do, or how to do it.