Cloudflare Email Routing
Cloudflare Email Routing adds MX records that point to Cloudflare's inbound relays and publishes SPF and DKIM records for messages Cloudflare sends on behalf of the zone.
Cloudflare's documentation lists the MX hostnames and the TXT records the dashboard adds when routing is enabled. Outbound mail from Workers or other products uses separate DNS names documented on those product pages.
Cutover
Cloudflare's guide lists MX priorities and targets to add at the zone. Remove or lower priority on old MX hosts when moving inbound delivery to Cloudflare.
Outbound SPF authorizes the hosts that submit mail. Inbound routing MX changes do not replace SPF for separate SMTP submission paths.
Separate outbound names
Workers and other Cloudflare send paths may use different DNS names from Email Routing. Follow the documentation for the product you enable.
Inbound MX changes affect where mail arrives. SPF for mail sent through Cloudflare still has to authorize the hosts that actually submit SMTP for the domain.
Cloudflare's routing documentation lists the MX hostnames to add when enabling the product. Disable or remove conflicting MX at the previous host before cutover.