Migrate your Existing SentinelOne Console to Red Canary’s SentinelOne Console

Red Canary will create a new SentinelOne console for you in our managed instance and provide the site token.

1. The Red Canary team will complete the required steps to provide you with a new SentinelOne account. 

2. The Red Canary team will create a Console User for you to gain access to it with the Admin role.

3. The Red Canary team will provide you with the site token and this help article. You’ll use this in a later step.

1. Review exclusions and blacklist items in your current SentinelOne console.

2. Export Exclusions manually (recreate on target Console) or through the Exclusion Tool.

   1. For more information on this process, see the SentinelOne User Guide.

3. Import Exclusions to the new account manually (recreate on target Console) or through the Exclusion Tool.

   1. For more information on this process, see the SentinelOne User Guide.

4. Copy over the policy configuration settings from the source to the target console.

Note: Dynamic groups will not require individual site or group tokens as they will filter automatically to their matching site or group. For everything else, you will likely go group by group. Additionally, all threats must be resolved in the current SentinelOne console, and an endpoint must be online to migrate it.

1. In the group or site, select Endpoint name.

2. Actions will automatically highlight; click Actions.

3. Type and then search for Migrate agent.

4. Input the site token provided by your Red Canary contact from Step 1.3.

5. Click through prompts to initiate migrations, and a box will appear briefly at the top of Atlas, telling you how many agents will be migrated. 

6. Repeat the above steps until all groups and sites have been migrated.