Views:

Partner Guide (Self‑Serve Submission)

Purpose

This guide helps you determine whether your DNSFilter environment can be transferred to Sherweb, what you must provide to avoid delays, and what to expect after you submit a transfer request. 

Who submits the request?

Partners submit the Transfer-In Request Form directly. The form will guide you through the required information and attachments. 

1) Choose the transfer type

  • Single customer organization (transfer one organization/tenant under a Sherweb MSP). 

    • Note: The organization will lose any policies that were set up by the source MSP.

  • Full partner (MSP) account (transfer your partner account/tenant to Sherweb). 

2) Contractual eligibility

A transfer cannot be forced if contractual obligations exist with the current provider/distributor. 

  • Confirm there is no active contract preventing the move. 

  • Confirm there is no outstanding balance with the losing provider (where applicable). 

3) Written approvals (required)

Written approval is required from the following parties (as applicable):

  • Source distributor

  • Source MSP (single‑organization transfers only)

Approval replies must confirm consent to the transfer and include confirmation that there is no contractual restriction and no outstanding balance.

Approval email templates (English/French) are provided as downloadable attachments directly in the Transfer‑In Request Form. Use those templates to avoid rework.

4) Cumulus readiness

Before submitting the request:

  • Any Cumulus organization(s) that do not exist must be identified within the organization creation CSV.

  • The organization mapping file must be completed for all DNSFilter organizations that will be transferred in to ensure proper billing.

5) Transfer timing

To avoid billing intricacies, it is preferable to request a transfer be done for the 1st of the requested month.

  • Provide a preferred transfer date.  This should be no later than 6 days prior to the first of the transferring month

  • If no date is provided, the transfer proceeds as soon as it is submitted/processed.  

6) Information you will need to submit

Required for all requests:

  • Transfer type (single organization or full partner account)

  • Cumulus URL(s)

  • Approvals (upload the email replies)

  • Intended transfer date (optional)
     

Additional information – Single organization:

  • Organization Administrator First Name 

  • Organization Administrator Last Name

  • Organization Administrator Email Address

  • Organization ID (found in the URL while filtered on the Organization account)

  • Source & destination Partner Name
     

Additional information – Full partner account:

  • Partner Administrator First Name: 

  • Partner Administrator Last Name: 

  • Partner Administrator Email Address:  

  • Current MSP Organization ID (found in the URL while filtered on the account)

  • Partner Organization Name

Billing & PSA visibility

To learn more about when you can expect to see DNSFilter usage on your Sherweb invoice and in your PSA integration post-transfer, please refer to Sherweb’s billing knowledge base article:

https://helpdesk.sherweb.com/en-us/knowledge-base/articles/KA-04681 

What happens after you submit?

  1. Sherweb reviews the request for completeness (approvals, required data).  

  2. Sherweb coordinates the transfer with all involved parties.

    • DNSFilter will move your data to Sherweb.

    • DNSFilter will switch your billing to Sherweb.  

  3. You are notified once the transfer is completed or if additional information is needed.  

Quick self‑check

  • I can obtain written approvals from the required parties.

  • I confirm there are no contractual restrictions or outstanding balances.

  • I have my Cumulus URL(s).

  • I have all required DNSFilter information ready.