How to Migrate Business Email to Microsoft 365 Safely

Understanding Why Now Matters

Exchange Server versions approaching end of support leave organizations running unsupported infrastructure, creating mounting compliance and security risks. Microsoft no longer provides security patches or technical support for these older versions, leaving organizations exposed to vulnerabilities that attackers actively exploit.  At the same time, Microsoft 365 is used by more than 430 million people globally, and over 90% of Fortune 500 companies trust Microsoft 365 Copilot, signaling an industry-wide shift toward cloud email. For most businesses, the strategic question is no longer whether to migrate, but how to execute migration safely without disrupting daily operations or losing business-critical data.

Why Safety Isn’t Optional

Email downtime instantly disrupts client communication, internal coordination, and time-sensitive workflows. Data loss or incomplete transfers of emails, contacts, or calendars may be impossible to recover once the source environment is decommissioned. Backup retention windows close.

23% of organizations experience some data loss during migration, often from preventable oversights in the planning phase. 45% of migration failures stem from compatibility issues, most caught too late to prevent disruption. Niya Digital’s team has observed that migrations that rush through planning consistently face unexpected delays and post-cutover scrambling that a structured upfront approach could have prevented.

The Cost of Doing It Wrong

Over 80% of data migration projects run over time or exceed budget, according to Bloor Group research spanning hundreds of organizations. Extended downtime, corrupted records that surface weeks after go-live, and teams unable to access critical data are not edge cases; they happen routinely when planning is rushed or insufficient.

The difference between a smooth migration and a chaotic one is not luck. It is preparation, testing, validation, and having clear rollback plans documented before cutover begins.

Microsoft 365 Plans & Pricing

Find the Microsoft 365 plan that fits your needs, whether you're using it at home, with your family, or for your business. With a range of plans designed for different budgets and requirements, you can enjoy the tools you need to stay productive, connected, and protected.

Microsoft 365 Email Essentials

$4.99 per month

Professional email with 10GB of email storage.

• Professional email using your domain name
• 10GB storage for email, contacts & calendar
• Sync across all devices
• Shared online calendars
• Up to 400 email aliases

Order Now

Microsoft 365 Email Plus

$5.99 per month

Professional email with 50GB of email storage.

• Professional email using your domain name
• 50GB storage for email, contacts & calendar
• Sync across all devices
• Shared online calendars
• Up to 400 email aliases

Order Now

Microsoft 365 Online Business Essentials

$9.99 per month

Office web apps & professional email.

• Office apps (online only)
• 1TB OneDrive storage
• Unlimited online meetings & HD video
• Professional email using your domain
• 50GB email storage
• Sync across all devices

Order Now

Microsoft 365 Business Professional

$13.99 per month

Office apps on 5 devices, web apps & professional email.

• Office apps installed on up to 5 devices
• Office web apps
• 1TB OneDrive storage
• Business apps included
• Professional email using your domain
• 50GB email storage

Order Now

Assessing Your Current Setup

The first step is thorough inventory and assessment. Before choosing a migration path, you need a clear map of what you are moving and the constraints you face. Whether you use on-premises or cloud-based business email hosting, a thorough assessment informs your migration strategy and helps identify potential blockers early.

Mapping Your Email Environment

Document your existing infrastructure in detail: which email platform you are running (Exchange 2013, 2016, 2019, or other cloud providers), how many mailboxes exist, their average sizes, and which users are active versus inactive. Identify third-party integrations, connectors, and add-ins used across your organization. Note any compliance requirements, data residency rules, retention policies, and litigation holds that will shape your Microsoft 365 configuration after migration. Evaluate your network infrastructure: insufficient bandwidth for bulk data transfer can become a bottleneck, extend the migration window, and increase risk.

A thorough discovery step helps you define the best way to move your data and anticipate challenges. List all domain names in use, any public folders or archives storing business-critical data, and confirm who owns the DNS registrar and domain registrations within your organization. One common failure point: critical legacy data stored in public folders, archives, or third-party systems often gets missed during planning, then discovered after cutover when the source system is no longer accessible or backed up.

Choosing Your Migration Method

Microsoft offers three official paths for on-premises Exchange migrations, each with distinct characteristics and use cases. Staged migration supports older Exchange versions and enables permanent coexistence with on-premises servers. However, it is limited to organizations with Enterprise licenses. Cutover migration moves all mailboxes at once for organizations with fewer mailboxes running Exchange 2003 or later, offering speed but carrying the highest risk. Hybrid migration permanently connects on-premises and cloud environments, offering granular control and coexistence but requiring more infrastructure setup and ongoing management.

For other cloud email providers or legacy IMAP systems, Microsoft 365 supports IMAP migration as the standard path. Your mailbox count, source version, and compliance requirements determine the best fit for your organization. Cutover is fastest if you have few mailboxes and can tolerate a single migration window. Staged is methodical if you need weeks of coexistence between systems. Hybrid is most resilient if you want zero risk but requires sustained on-premises infrastructure investment. No single answer is universally correct; your environment and risk tolerance should guide the decision.

Preparing Before Migration Touches Any Data

Planning and preparation determine migration success more than any technical tool or vendor. Planning typically consists of three main parts: discovery (mapping your current setup), clean-up (removing old accounts and redundant data), and communication (notifying users of what to expect). Each phase requires attention to detail and honest assessment of your organization’s readiness.

Cleaning Mailboxes to Reduce Risk

Before any data moves from source to destination, clean the source mailboxes thoroughly. Unnecessary data bloat increases migration complexity by 40–60 percent, expands the cutover window, and increases the risk surface. Delete promotional emails and newsletters you no longer read, remove spam, and audit older archived messages. Remove duplicate messages, broken attachments, and corrupted items that will only cause problems in the new environment. This isn’t merely an efficiency measure; smaller migrations are faster, cheaper, and easier to validate because discrepancies stand out immediately instead of getting buried in noise.

Create a documented policy for what stays and what gets cleaned before migration begins, and apply it consistently across all mailboxes in your organization. Consider archiving emails older than a certain date if your retention policy allows, moving them to separate storage outside the migration scope. This cleanup phase prevents downstream technical failures and ensures your Microsoft 365 mailboxes start clean, with only relevant business email and data.

Building Communication & Migration Planning

Email outages affect the entire organization immediately and visibly. Users who understand what is happening and why are far less likely to resist the change or panic during disruptions. Communicate the migration strategy, expected operational impact, what will change about their email access, and when training will occur. Set clear expectations: when they will regain full access, which devices to reconfigure, where to find support if issues arise. Communication before migration begins prevents confusion and reduces support ticket volume during the critical post-cutover window.

Establish a migration steering committee including stakeholders from IT, business units, and leadership to oversee planning and execution. Define clear roles: who approves the plan, who manages the technical execution, who handles user support, and who makes decisions if problems emerge. Document all decisions and assumptions in writing so that if challenges arise, your team understands the context and reasoning behind earlier choices.

Configuring Security Before Data Arrives

The single most critical mistake organizations make is configuring security after migration is underway. By then, initial access logs, threat detection alerts, and compliance audit trails are already missing. Every element must be active and tested before the first user moves to Microsoft 365.

Enabling Audit Logging & Threat Detection

The Unified Audit Log defaults to OFF in Microsoft 365, and an administrator must enable it in the Security and Compliance Center before the first user migrates. Enabling the audit log after data arrives means you cannot record events that occurred during cutover or the immediate post-migration window, a gap that creates compliance blind spots and blocks forensic investigation if compromise is later suspected. Enable suspicious activity alerts for suspicious location logins and high volumes of outgoing emails, which could indicate a compromised account.

Coordinate with your compliance and legal teams to ensure the audit log scope matches regulatory requirements for your industry. Configure the audit log to record all relevant activities, including mailbox access, forwarding rule changes, delegate access modifications, and file access. Test the audit log to confirm it captures events correctly before migration begins, ensuring no compliance events go unrecorded.

Enforcing Multi-Factor Authentication & Access Controls

Enable Security Defaults for simple environments or configure Conditional Access policies for environments with more complex security requirements. Enable both multi-factor authentication and legacy-authentication blocking before users arrive in Microsoft 365. Legacy authentication protocols are the primary attack vector for password spray and brute force attacks against Microsoft 365 tenants, so block them outright unless a specific integration requires them.

Document any exceptions to legacy-authentication blocking, including which systems or integrations require it and why. Communicate MFA requirements to users before migration and provide clear guidance on setting up authenticator apps or security keys. Test MFA login flows with a pilot group to identify technical issues before the organization-wide rollout.

Setting Up DNS & Email Authentication

Email routing and authentication are technical blockers that must be correct before cutover. Misconfigured DNS can break mail delivery entirely or send emails to spam folders instead of inboxes. Misconfigured SPF, DKIM, and DMARC prevent bulk sending and trigger authentication failures across receiving mail servers globally.

Adding MX & SPF Records

Publish a single SPF record with the value v=spf1 include:spf.protection.outlook.com -all. This authorizes all of Exchange Online’s sending infrastructure globally. Do not create multiple SPF records for the same domain, as this violates SPF specifications and causes authentication failures. Add an MX record pointing to your tenant-specific target (for example, yourcompany-com.mail.protection.outlook.com at priority 0).

These records must be in place and fully propagated before the DNS cutover. During the pre-migration phase, lower the TTL (time-to-live) on your existing MX records to allow faster propagation when you eventually cut over to Microsoft 365. Work with your DNS administrator to understand how changes propagate in your environment and plan accordingly.

Enabling DKIM & DMARC

Add DKIM CNAME records selector1._domainkey and selector2._domainkey pointing to Microsoft’s targets. Unlike SPF TXT records, DKIM uses CNAME records and enables automatic key rotation, meaning you never need to manually update DNS when encryption keys change. Enable DKIM signing in the Microsoft 365 Defender portal for your domain. Verify that DKIM is enabled not just at the DNS level but also in Defender, as the records alone do not activate signing.

Deploy DMARC gradually, starting with p=none (monitoring only), reviewing aggregate reports, then advancing to p=quarantine and finally p=reject. Publish your DMARC policy as a TXT record at _dmarc.yourdomain.com. As of May 2025, Microsoft enforces SPF, DKIM, and DMARC for bulk senders to Outlook.com; configuration is mandatory, not optional. This enforcement means that without proper authentication, major mail providers will reject or quarantine your organization’s email.

Testing Before Cutover

After publishing DNS records, allow sufficient time for global propagation. Send a test email from Microsoft 365 to an external email account, open it, and view the complete email headers. Check the Authentication-Results line: you should see spf=pass, dkim=pass, and dmarc=pass. If any shows fail or is missing, troubleshoot the configuration before cutover. Use Microsoft’s built-in Message Trace in the Exchange Admin Center or the Email Entity page in Defender to verify mail flow is working correctly.

Document the results of your email authentication tests in writing, including the test email addresses used, the headers examined, and the results. Keep this documentation for post-migration reference if delivery issues emerge, as it provides a baseline of what worked correctly before cutover.

The Migration & Cutover Window

The actual cutover is the culmination of weeks or months of careful preparation and planning. By this point, your strategy and communication have been locked, your security policies are active and tested, and your DNS records have been validated. The cutover window itself should be uneventful if planning were thorough.

Running a Pilot Migration

Never run a full organization migration without testing at scale. Run a pilot migration with a group of real users first to confirm information accuracy, mailbox sizes, calendar entries, contacts, and other data before organization-wide adoption. This pilot catches real-world issues, sync delays, missing emails, and authentication errors on specific devices that isolated lab testing will not expose.

The pilot should include users across different client platforms, including Outlook desktop, mobile devices with the Outlook app, and Outlook on the web, to expose any platform-specific failures before full cutover. Document all issues found during the pilot, their root causes, and the resolutions applied. This documentation becomes invaluable if similar issues emerge during the full migration, since you already have tested solutions ready. Train your support team on the issues and solutions discovered during the pilot.

Executing the Batch Migration

If you use staged or cutover migration, start the migration batch in the Exchange Admin Center and let it run. Exchange Online synchronizes mailboxes in batches based on your schedule and available system capacity. Do not rush this phase by forcing all mailboxes to migrate simultaneously, as this can overwhelm the system and cause performance issues or sync failures.

Keep the old system running and accessible until background synchronization is complete, allowing users to continue accessing their email from the legacy system while migration proceeds in the background. Monitor the migration progress closely through the Exchange Admin Center reporting. Review error logs and failed mailbox reports as they are generated. For any mailboxes that fail to migrate, investigate the root cause and take corrective action before retrying the migration for those specific mailboxes.

The DNS Cutover (The Critical Moment)

When you change your MX records to point to Microsoft 365, the actual cutover begins, and new email starts flowing to the new system immediately. DNS propagation can take time, during which some emails will be routed to the old system and some to the new system. A good migration plan accounts for this transition period by keeping the old email system running and monitoring both systems for incoming mail.

Email flow connectors can forward mail from the old system to the new if needed, ensuring no incoming email is lost during the propagation window. Have a clear rollback plan documented before you make DNS changes. If critical issues emerge immediately after DNS cutover, you should be able to reverse the MX record changes and reroute email back to the old system. At the same time, you investigate and resolve the problems.

Post-Migration Validation & Troubleshooting

Cutover is not the end of the migration; it is the beginning of the validation phase. The first 48 to 72 hours after cutover are critical for identifying and resolving issues before they become widespread problems affecting the entire organization.

Verifying Data Integrity

Compare data from the old system to the new using migration reports and validation tools. Check item counts: if 50,000 emails were in the old mailbox, confirm 50,000 are in the new one. Spot-check a sample of emails, contacts, and calendar entries for completeness and accuracy. Verify that email formatting, attachments, and embedded images migrated correctly and display properly in Outlook.

Keep access to the old email system available for recovery if issues surface after cutover, allowing administrators to retrieve missing data if needed. Create a rollback procedure in advance that documents how to restore from backups if data corruption is discovered. Ensure that IT staff understand the procedure and can execute it quickly if needed. Test the rollback procedure in advance in a non-production environment to ensure it works before you need it in an emergency.

Resolving Common Post-Migration Issues

Syncing delays can often be resolved by forcing a manual sync or clearing the cache in Outlook. Missing emails may require re-running selective migrations for affected mailboxes to recover the missing data. Authentication errors usually point to OAuth 2.0 settings and can be fixed by updating those settings on devices.

Monitor logs and user reports closely; prioritize problems affecting multiple users or critical workflows for immediate resolution, while escalating minor issues affecting individual users to support queues. Document all issues encountered and their resolutions in a centralized knowledge base for your support team. This documentation accelerates resolution if similar issues emerge for other users and provides a reference for future support staff.

Validating Mail Flow

Send test emails between internal addresses, to external domains, and observe that replies deliver successfully in both directions. Confirm that shared mailboxes, distribution lists, and forwarding rules migrated correctly and function as expected. Reconfigure any multifunction devices, such as scanners and fax machines, that send emails. Hence, they route through Exchange Online instead of the old system.

Verify that mail flow connectors work if you use them for backup routing or security inspection. Test sending email to external recipients, ensuring authentication passes and emails arrive in the inbox rather than spam. Ask external contacts to confirm they are receiving email correctly. Verify that DMARC reports are being generated and delivered to your monitoring address.

User Onboarding & Microsoft 365 for Small Business Adoption

After cutover completes and data integrity is confirmed, users need hands-on support to transition successfully to the new environment. This onboarding phase is when users experience the collaboration and productivity gains available with Microsoft 365. Without proper onboarding, users may struggle with the new interface or miss features that could accelerate their work.

Reconfiguring Outlook & Mobile Access

Users must update Outlook on desktop workstations to connect to their new Microsoft 365 mailbox instead of the old system. The Autodiscover mechanism should handle this automatically if DNS is configured correctly. Still, some environments or specific users may need manual reconfiguration. Provide updated authentication methods, including multi-factor authentication setup on mobile devices and Outlook apps. Test Outlook on iOS and Android to confirm sync works, calendars load properly, and meeting notifications function correctly.

Create detailed step-by-step guides with screenshots showing users how to reconfigure Outlook on their specific devices. Many post-migration helpdesk tickets come from users who haven’t reconfigured their mobile devices or don’t understand how to set up MFA. Proactive communication and clear instructions significantly reduce support volume.

Training on New Features & Security Practices

Microsoft 365 includes collaboration features many organizations haven’t used before: Microsoft Teams for messaging and video conferencing, SharePoint for team sites and document management, and OneDrive for personal file storage accessible from any device. Brief training on these tools, plus security practices like recognizing phishing emails and using multi-factor authentication correctly, prevents both productivity loss and security gaps. Schedule live training sessions during the first week after migration and provide recorded versions for reference and future employees.

Focus training on the features most relevant to your organization’s workflows. If your teams use email heavily, focus training on shared mailboxes and distribution lists. If your organization needs collaborative document management, focus on OneDrive and SharePoint. Tailor training to your audience rather than delivering generic training that covers every feature equally.

Support Channels & Escalation

Announce clear support channels: email for non-urgent issues, a phone line or chat for critical problems, and escalation paths for complex technical issues that require specialized expertise. First-week response times should be same-business-day at minimum to maintain user confidence. Have escalation procedures documented so support staff can quickly route complex technical issues to your IT department or migration partner without leaving users waiting.

Staff your support team appropriately during the first week after cutover. Have extra resources available to handle the higher volume of questions and issues that always emerge during migrations. Many issues can be resolved through self-service resources or support articles if you make them accessible to users immediately.

Long-Term Optimization & Decommissioning

Once all users are successfully operating in Microsoft 365 and no incoming mail flows to the old email system, plan the decommissioning phase. This phase is not urgent and should not be rushed, as premature decommissioning can cause problems if issues surface later and you need access to historical data.

Maintaining Access for Recovery

Keep the old email system online and accessible for recovery purposes after migration completes. If a critical email is missing or a user discovers data corruption, you have a safety net to retrieve the data without complex and time-consuming restoration procedures from backup media. After a sufficient period has passed and you have confirmed no data issues have surfaced, you can safely shut down and decommission the old system.

Document the decommissioning procedure for the old email system, including backup procedures, hardware disposal, and license cancellation. Ensure all stakeholders understand when the old system will be shut down and what to do if they find issues that require access to the old data.

Configuring Retention & Compliance

Set up retention policies, sensitivity labels, and eDiscovery in Microsoft Purview to meet regulatory requirements and protect compliance-critical data. These policies protect compliance-critical data against accidental deletion and make it accessible for audit and litigation holds when required. Compliance configuration is your organization’s responsibility; Microsoft provides the tools, but you define the policy. Consult legal and compliance teams to ensure your configuration matches regulatory requirements.

Review retention policies to ensure they balance compliance requirements with storage costs. Set automatic deletion policies for old email, if your regulations allow, to reduce storage burden. Configure litigation holds for users or departments that may be involved in legal matters, ensuring their email is preserved for legal discovery.

Optimizing Mailbox Configuration

Review licensing assignments to ensure users are on the appropriate plan tier for their actual usage patterns and job responsibilities. Users who only need email access can be on a lower plan tier than knowledge workers who use full Office applications. Reserve Business Premium for users with specific compliance needs or device management requirements. Mixed licensing saves costs at scale without sacrificing functionality for users who need it.

Monitor mailbox growth and storage utilization to ensure users don’t approach quota limits. Configure appropriate quota limits for your organization and communicate them to users so they understand storage expectations.

Frequently Asked Questions

What happens if the migration fails partway through?

If a migration batch fails, you can re-run the batch for failed mailboxes or restart the entire batch if needed. Microsoft’s migration tools include detailed error reporting and logs showing exactly what failed and why. If you suspect data corruption, revert to the old system and consult your migration partner or Microsoft support for guidance on recovery options.

Can I migrate email without any operational disruption?

No approach eliminates all operational impact, but staged and hybrid migrations significantly minimize disruption. Staged migration allows an extended coexistence period, so users experience no outage. Cutover migration requires a transition during which mail routing switches to the new system. Plan for this transition and communicate expectations clearly to users.

How do I handle email for users on leave or who have left the organization?

Address inactive accounts before migration begins. Decide whether to migrate their mailboxes, archive them separately, or delete them based on your retention policies and compliance requirements. Communicate these decisions to relevant managers and document your decisions.

What if our domain registrar isn’t on the supported list?

Microsoft 365 domain setup works with any registrar that allows you to manage DNS records. If your registrar doesn’t have built-in Microsoft 365 setup, you can manually add the DNS records provided by Microsoft through your registrar’s DNS management interface. Contact your registrar’s support if you need help adding MX, CNAME, or TXT records.

Will all my email attachments migrate correctly?

Most attachments migrate without issues, but very large attachments can cause sync problems during migration. Exchange Online supports large attachments, but IMAP migration has limitations. Clean up oversized emails before migration if your organization uses IMAP migration. Verify attachment sizes in your source system and ensure they are supported in Microsoft 365.

How do we ensure email deliverability after migration?

Proper SPF, DKIM, and DMARC configuration is essential for deliverability. After setting these records, send test emails to major providers and verify that authentication passes. Many post-migration deliverability issues stem from incomplete DNS configuration, not Microsoft 365 itself. Work with your email authentication experts to ensure complete configuration.

Can we migrate shared mailboxes and distribution lists?

Yes. Shared mailboxes migrate their content and configuration. Distribution lists migrate as groups and maintain their membership. In staged and hybrid migrations, mail-enabled groups retain membership and forwarding rules. Verify that permissions were preserved post-migration by testing access with a few users.

What compliance risks should we watch for during migration?

If your organization is subject to data-residency requirements, retention policies, or litigation holds, ensure these are configured in Microsoft Purview before data migrates. Compliance is your organization’s responsibility; Microsoft provides the tools, but you define policy. Consult legal and compliance teams before migration to avoid violations that could trigger regulatory penalties.

What support is available after migration?

Microsoft 365 includes 24/7 support through the admin center and phone support depending on your plan level. For complex issues, engage a Microsoft partner or your internal IT team. Niya Digital provides post-migration support and optimization to ensure your organization gets maximum value from Microsoft 365 after the transition.

Can I migrate incrementally, some users in waves rather than all at once?

Yes. Staged and hybrid migrations are specifically designed for phased adoption. Cutover migration is all-or-nothing, but staged migration lets you migrate users in waves, validating each batch before moving to the next. Phased migration reduces risk and allows you to learn from each wave before proceeding.

What if users keep accessing the old system after migration completes?

This creates duplicate mailboxes and prevents you from fully decommissioning the old system. After an initial coexistence period, begin restricting access to the old system to force users to transition. Users who keep accessing the old mailbox can cause mail delivery confusion and create compliance gaps if email isn’t properly archived.

How do I migrate with limited IT resources?

Engage a Microsoft partner or migration service provider to handle the technical execution. This approach frees your IT team to focus on internal communication, user training, and post-migration support. Professional migration services reduce risk and accelerate the project compared to managing it entirely in-house with limited resources.

Is migration reversible if something goes wrong?

If critical issues emerge immediately post-cutover (within the first few hours), you can reverse DNS changes to reroute mail back to the old system while investigating. This requires keeping the old system online. After several days, reversing becomes complex, and the risk of data loss increases significantly. This is why testing before cutover is absolutely critical.

Do we need to upgrade our network for migration?

Large migrations require adequate outbound bandwidth to avoid bottlenecks. Most modern business networks support the requirements; if you have constrained bandwidth, plan to migrate during off-hours or in smaller batches to spread the load.

What’s the best approach for communicating with users about migration?

Start communicating early and regularly. Announce the migration decision, explain why it is happening, and describe what users will experience. Provide detailed instructions on what users need to do before, during, and after migration. Schedule training and explain where to get support. Regular communication reduces anxiety and support tickets significantly.

Glossary

• Audit Log: A record of all actions and events occurring in Microsoft 365. Enable the Unified Audit Log before data migrates to ensure compliance events are captured and available for forensic investigation if needed.
• DKIM (DomainKeys Identified Mail): An email authentication method using DNS CNAME records to cryptographically sign outgoing messages, proving they originated from your domain and were not forged in transit.
• DMARC (Domain-based Message Authentication, Reporting and Conformance): A DNS policy published as a TXT record on _dmarc.domain.com that defines what receiving email servers should do with unauthenticated email claiming to be from your domain.
• DNS (Domain Name System): The global infrastructure that translates domain names into IP addresses and routes internet traffic to the correct servers, maintaining the address book of the entire internet.
• Exchange Online: Microsoft’s cloud-hosted email platform; the email component of Microsoft 365 that replaces on-premises Exchange Server with a cloud service managed by Microsoft.
• Hybrid Migration: A migration approach that connects on-premises Exchange and Exchange Online permanently, allowing mailbox coexistence and enabling gradual mailbox moves over time rather than all at once.
• MX Record (Mail Exchange Record): A DNS record that tells email systems worldwide where to deliver email for a specific domain, directing incoming mail to the correct mail server.
• SPF (Sender Policy Framework): A DNS TXT record that authorizes which mail servers are permitted to send email on behalf of your domain, preventing unauthorized systems from spoofing your domain.