Skip to Main Content
Back to Learning Center

Migrate from PowerDMARC without a reporting gap

Samuel ChenardBy Samuel ChenardNovember 15, 202612 min read

In brief

To migrate from PowerDMARC, add a second rua address in Hosted DMARC, compare both tools for 30 days, then swap the CNAME, NS and SPF records it hosts.

Migrate from PowerDMARC without a reporting gap

To migrate from PowerDMARC without losing reports, run the new tool beside it first. Add the new provider's reporting address to the DMARC record so both tools receive the same aggregate reports, compare them for about 30 days, and only then replace what PowerDMARC hosts for you: usually a _dmarc CNAME, a _domainkey NS record and a PowerSPF include.

The order matters because PowerDMARC's Hosted Services answer for those names from its own servers. If you remove the _domainkey delegation before you have copied the DKIM keys behind it, those keys stop resolving. If you replace the PowerSPF include before you have copied its mechanisms, the senders it authorized stop passing SPF.

At a glance

Quick takeaways

  • A DMARC record can list more than one aggregate-report address, so PowerDMARC and another tool can read the same reports at once.
  • If PowerDMARC hosts your DMARC record, add the second address in its Hosted DMARC settings, which accept additional aggregate (RUA) recipients. Your DNS provider cannot edit a record PowerDMARC serves.
  • Hosted DKIM is an NS delegation of _domainkey, and PowerDMARC's own guide tells you to delete the old selectors from your zone once it is live. Copy every selector out of PowerDMARC before you remove that delegation.
  • PowerSPF keeps your sending mechanisms in PowerDMARC and publishes a single include. Copy the mechanism list before you replace the record.
  • Keep the policy tags (p, sp, np, adkim, aspf, and any t, fo or ri already present) exactly as they are during the move. A provider change is not a policy change.

Step 1: Find out what PowerDMARC hosts for the domain

PowerDMARC can host five kinds of record. Its Hosted DMARC guide replaces your TXT record with a CNAME at _dmarc; its Hosted DKIM guide adds an NS record that delegates _domainkey; its PowerSPF guide replaces your SPF record with a generated one; and its Hosted MTA-STS guide adds three CNAMEs for MTA-STS and TLS reporting. The fifth is Hosted BIMI, which hosts your logo and certificate behind a BIMI CNAME (Hosted BIMI guide). All five guides were checked on 15 November 2026.

Run these lookups for your own domain. Replace example.com with it.

Terminalbash
dig +short CNAME _dmarc.example.com
dig +short TXT _dmarc.example.com
dig +short NS _domainkey.example.com
dig +short TXT example.com | grep spf1
dig +short CNAME _mta-sts.example.com
dig +short CNAME mta-sts.example.com
dig +short CNAME _smtp._tls.example.com
dig +short CNAME default._bimi.example.com

On PowerDMARC's own domain, the same lookups on 15 November 2026 returned a _dmarc CNAME into hosteddmarc.dmarc-dns.com, an SPF record that was one powerspf.com include, MTA-STS CNAMEs into mta-sts.tech, a TLS reporting CNAME into tls-rpt.tech and a BIMI CNAME into powerbimi.com. Its DMARC reports went to addresses at rua.powerdmarc.com and ruf.powerdmarc.com. Customer domains may be given different host names, so treat these as examples: the values that count are the ones on each Hosted Services page in your account. Any answer that matches one of them is a record PowerDMARC hosts or reads. Write each one down with the record it replaces. Three patterns cover most domains:

  • A _dmarc CNAME. PowerDMARC's Hosted DMARC serves the record, and you edit the policy in PowerDMARC, not at your DNS provider.
  • A _dmarc TXT record whose rua points to PowerDMARC. This is the traditional setup the setup wizard offers, with the report addresses pre-filled. You manage the record yourself, and Step 2 is a one-line edit.
  • An NS record on _domainkey, or an SPF record that is a single PowerDMARC include. Hosted DKIM or PowerSPF is on, and the keys or the sender list live in PowerDMARC.
If PowerDMARC published records for you through its one-click DNS publishing with Entri, those are ordinary records in your zone. They still point to the same PowerDMARC hosts.

Step 2: Add the second reporting address

The rua tag takes a comma-separated list of addresses (RFC 9989, section 4.7), so both tools can receive the same aggregate reports. In Palisade, the domain's Manage DMARC page generates the record to copy; take the rua address from it (Palisade docs).

When _dmarc is a CNAME to PowerDMARC, the record is served by Hosted DMARC. Its guide lists "Additional Aggregate Report (RUA) recipients" among the settings you can change, and saving the record publishes the change without a DNS edit (Hosted DMARC guide). Add Palisade's address there and change nothing else.

When you manage the TXT record yourself, keep every tag and add the second address after the first:

Technical exampletext
_dmarc.example.com TXT "v=DMARC1; p=quarantine; rua=mailto:abc123@rua.powerdmarc.com,mailto:your-palisade-address@reports.example"

Both addresses above are placeholders. Keep your existing PowerDMARC address as it is, and copy Palisade's from the record Palisade generates.

Reports sent to an address on another domain need that domain's permission (RFC 9990, section 4). If no reports reach Palisade after two days, check the address was copied exactly, then contact Palisade support.

Step 3: Compare both tools for about 30 days

Aggregate reports usually arrive once a day from each mailbox provider, so a month gives you enough days to see every regular sender, including monthly billing and newsletter runs. During the overlap:

  • Confirm both tools list the same sending sources and roughly the same message counts.
  • Compare pass and fail rates for each sender. A large gap usually points to a sender that PowerSPF authorizes and that your new SPF record will need to name.
  • Download what you want to keep. PowerDMARC's Reporting > Download/Upload XML Reports page lets you download each raw aggregate report (XML reports guide). Its pricing matrix lists that download on Basic and above, and CSV export on Enterprise, API and Partner Program plans.
  • Leave the policy alone. If a policy change is due, make it before or after the move, not during it.

Step 4: Copy out what PowerDMARC holds, then swap the records

Keep PowerDMARC active until every replacement resolves. Work through the hosted records in this order.

  1. DKIM keys first. Open Hosted DKIM and copy every selector for every domain and subdomain, with its full record, CNAME target or public key. PowerDMARC's guide asks you to remove the old selectors from your own zone once the delegation works, so for most domains PowerDMARC is now the only place they are published in DNS (Hosted DKIM guide). If the new home is another provider's delegated zone, add each selector there first; Palisade's hosted DKIM is also a _domainkey NS delegation, so a move to Palisade works this way (Palisade hosted DKIM docs). Then switch the _domainkey NS record in one change. If the new home is your own zone, remove the NS record and add every selector in the same change, because selectors under a delegated name in your zone do not resolve. No DNS query lists every selector, so check your list against the selectors in the aggregate reports you collected during the overlap. A missed selector fails DKIM for that sender.
  2. SPF. Open Hosted SPF (PowerSPF) and copy every active mechanism. PowerSPF rechecks the senders behind your record every 20 minutes (PowerSPF guide); once you replace the include, nothing does that for you. Build a real SPF record from the mechanisms, or use the new provider's hosted SPF include, and check it stays under the 10-lookup limit. In Palisade, hosted SPF is a single include, and you copy every existing mechanism into it before you publish (Palisade hosted SPF docs).
  3. DMARC. Copy the current policy exactly from dig +short TXT _dmarc.example.com, which follows the CNAME. Then, in one change, remove the _dmarc CNAME and publish the new provider's hosted record or your own TXT record. A name that holds a CNAME cannot hold any other record (RFC 2181, section 10.1), so the two cannot overlap. Keep the same tags. If Hosted DMARC set the testing tag t=y, keep it: PowerDMARC's guide says some receivers treat p=reject; t=y as quarantine, so dropping it can tighten the policy those receivers apply. In Palisade, hosted DMARC is a CNAME, and a diff preview shows what changes before you apply it (Palisade hosted DMARC docs).
  4. MTA-STS and TLS reporting. If PowerDMARC hosts MTA-STS, repoint the mta-sts host first and wait until https://mta-sts.example.com/.well-known/mta-sts.txt serves the new policy with a valid certificate and the right mx lines. Then repoint _mta-sts, which changes the id (RFC 8461, section 8.1). Replace the _smtp._tls CNAME with the new provider's v=TLSRPTv1; rua=... TXT record in the same change. With Palisade, TLS reporting is a TXT record in your own zone.
  5. BIMI. If your BIMI record is a CNAME to PowerDMARC, its logo and certificate are hosted by PowerDMARC; on PowerDMARC's own domain they loaded from hostedbimi.com. Copy the SVG logo and any certificate, host both somewhere you control, and point the new BIMI record at those URLs before you change default._bimi.
  6. Verify, then cancel. Run the lookups from Step 1 again. When no CNAME, NS or SPF record points to a PowerDMARC host and only its rua address remains, remove that address from rua, and from ruf if present, then cancel on your schedule. PowerDMARC's MSP programme says partners pay as they go, with no contracts (MSP programme). Direct Basic plans are billed monthly or yearly (pricing), so check your renewal date.
Four steps to migrate from PowerDMARC: map what Hosted Services serves, add a second report address, compare for 30 days, copy DKIM selectors and SPF mechanisms then swap the records
Source: Palisade.

A switch from PowerDMARC that stops halfway

One unfinished move is easy to miss: two addresses left in rua for months. Both tools keep receiving reports, the old plan renews, and nobody owns the last step because the new tool already looks like it works. If dig +short TXT _dmarc.example.com still shows a PowerDMARC address next to your new provider long after the overlap, the switch did not finish. Either complete Step 4 or decide on purpose to keep PowerDMARC as the second reader.

What changes for an MSP moving many client domains

The method is the same for every client domain, so an MSP can batch it. Group domains by what PowerDMARC hosts: domains with a TXT record need only the rua edit, while domains on Hosted DKIM or PowerSPF need the selectors and mechanisms copied out first. Run the 30-day overlap for a whole group at once, and move the hosted records group by group.

Two PowerDMARC features need a check when you leave. Its HaloPSA integration syncs subscription quantities and its Autotask integration bills on real-time domain counts (MSP programme), so confirm each client's billing line changes when its domain leaves. And PowerDMARC does not charge for parked domains that have no MX records or active subdomains, publish v=spf1 -all and use no hosted MTA-STS, TLS-RPT, BIMI or PowerSPF (in-active domains); those defensive records are yours, so leave them in place.

In Palisade, a ConnectWise, HaloPSA or Autotask integration can import the client domains, and the agent drafts every SPF and DKIM change and proposes each policy step for your team to approve. For the general provider-change checklist, including rollback records and change approvals, see the DMARC provider migration guide, and for DMARC basics the DMARC learning hub. For how PowerDMARC and Palisade compare on price and MSP terms, see the PowerDMARC alternative for MSPs. For what PowerDMARC publishes about price and product, see PowerDMARC pricing and the PowerDMARC review.

Evidence

Sources and further reading

Questions readers ask

Frequently asked questions

Can I run Palisade and PowerDMARC at the same time?

Yes. A DMARC record's rua tag can list both tools' reporting addresses, so Palisade and PowerDMARC each receive the same aggregate reports. If PowerDMARC hosts the record through a _dmarc CNAME, add Palisade's address as an additional RUA recipient in Hosted DMARC. If you manage a TXT record, add the address to the rua list yourself.

How do I know if PowerDMARC hosts my DMARC record?

Run dig +short CNAME _dmarc.yourdomain.com. A CNAME answer that matches the value on PowerDMARC's Hosted DMARC page (PowerDMARC's own domain uses one ending in hosteddmarc.dmarc-dns.com) means PowerDMARC's Hosted DMARC serves the record and the policy is edited in PowerDMARC. A TXT answer whose rua lists a PowerDMARC address means you manage the record and PowerDMARC only receives reports.

What do I need to copy out of PowerDMARC before leaving?

Copy every Hosted DKIM selector and every PowerSPF mechanism, for every domain and subdomain, plus any raw aggregate reports you want to keep. While _domainkey is delegated to PowerDMARC the DKIM keys are served from there, and PowerSPF keeps the sender list in PowerDMARC, so neither survives the move unless you rebuild it.

How long should PowerDMARC and the new tool run side by side?

Run PowerDMARC and the new tool side by side for about 30 days. Aggregate reports usually arrive daily, and a month covers monthly senders such as billing and newsletter platforms, so both tools have seen the same full set of sources before you remove any hosted record.

Will I lose my DMARC report history when I leave PowerDMARC?

PowerDMARC's report history does not move to a new tool on its own. Download the raw aggregate reports you want to keep from PowerDMARC's Download/Upload XML Reports page during the 30-day overlap, and ask the new provider whether it can import them. None of the PowerDMARC pages checked for this guide say what happens to stored history after you cancel.

Does moving off PowerDMARC change my DMARC policy?

No. Moving off PowerDMARC does not change your DMARC policy as long as you keep p, sp, np, adkim and aspf, plus any t, fo or ri tags, exactly as they are when you replace the record. Changing provider and changing policy are separate changes, and doing both at once makes any delivery problem harder to trace.

Prioritize authentication work across client domains

Start in Palisade.

Get started

Share this article

Samuel Chenard

Written by

Samuel Chenard

CEO & Co-Founder, Palisade

Samuel Chenard is the CEO and co-founder of Palisade, agentic DMARC software for IT teams and MSPs, from one domain to thousands.

More from Samuel →

Related articles and tools