Migrate to standalone DNS Filtering

This article explains the DNS Filtering (DNSF) migration process, which transitions MSPs from an integrated account (managed through N-central) to a standalone account (managed directly through the DNSF portal). It also outlines the differences between the two account experiences and highlights the actions required before, during, and after migration.

Review the migration steps

After you agree to proceed with the migration, N-able follows this process:

  1. Site renaming

    N-able personnel run an API on the designated server to rename all the DNSF sites that match the N-central service organizations (SOs), customers, and sites. This ensures clarity after migration.

  2. Disconnect integration

    N-able submits the migration request to our DNSF partners, who complete the transition to a standalone account. The connection between the N-central server and your DNSF account is removed.

  3. Disable DNSF rules

    N-able disables DNSF-related rules on the N-central server.

  4. Initiate migration

    N-able runs the DNSF API to start the migration process on the N-central server and all associated devices.

The migration process may take up to 30 days. During that time, DNSF integration indicators may still appear in N-central.

Compare the N-central experience before and after migration

Feature N-central before migration N-central after migration
DNSF integration menus Shown under Integration Management

 No longer shown
DNSF integration indicators Visible in the All Devices view

Example DNSF integration indicator:

 Visible in the All Devices view, but only for up to 30 days, until the migration is fully complete.

After migration, these indicators no longer appear.

After migration, devices that previously used integrated DNS Filtering in N-central but now use DNSFilter standalone will continue to show a DNS Filtering status.

New devices using DNSFilter standalone won't show this status.
Rule and policy management Managed using the N-central interface All DNSF-related functions are managed using the DNSF portal
DNSF agent control DNSF agent installed or removed using N-central Managed using the DNSF portal or directly on devices
Ecosystem agent behavior Uninstalling the Ecosystem agent removes the DNSF agent The Ecosystem agent should not be present on devices unless other integrations, such as Intune or EDR, are active.

If the Ecosystem agent is still present on devices and you manually uninstall it, the DNSF agent should remain installed—unless a communication issue with the N-central server prevented the devices from being marked as migrated.

Understand changes to DNSF portal access

Role DNSF portal before migration DNSF portal after migration
MSP No access Full access to your DNSF portal
N-able Full access No access to your DNSF portal

Understand how the DNSF portal structure changes

The DNSF portal structure differs between integrated and standalone accounts.

Integrated account structure

Device visibility is based on the user’s level in N-central. For example, users at the site level see only that site’s devices. Users at the SO level can access all devices under that SO and drill down into customers and sites.

CustomerServer
├── SO1
│   ├── Customer1
│   │   ├── Site1
│   │   └── Site2
│   └── Customer2
├── SO2
│   └── Customer1
│       ├── Site1
│       └── Site2

Standalone account structure

Device information is presented as a flat list. There is no hierarchy of SOs, customers, or sites.

SO1
SO1_Customer1
SO1_Customer1_Site1
SO1_Customer1_Site2
SO2
SO1_Customer2
SO2_Customer1_Site1
SO2_Customer1_Site2

Take action after migration

After the migration is complete, you may need to take the following actions in the DNSF portal:

  • Clean up inactive devices

    Remove DNSF devices that haven’t been active for more than 30 days.

  • Review reappearing devices

    Devices previously deactivated or deleted may reappear due to the migration process.

  • Manage policies and rules

    Review and adjust migrated DNSF policies and rules as needed.

  • Organizational cleanup

    Remove empty organizations or sites that were created during migration but do not contain devices.