After Changing Your Company Domain in 2026, Which Account Emails Should Cross-Border Sellers Update First?

Shopify’s account guidance distinguishes the email used to access an account from the store contact email used for store communications (Shopify’s account email guidance). That separation matters during a company email domain change: update store access, payment and billing, customer communication, and recovery addresses first, then confirm the new mailbox works before retiring the old one. Keep long-term business accounts on an address the business can control and recover; treat short-term evaluation accounts as a separate cleanup task.

This guide is for cross-border sellers and small-business owners changing a company domain, plus the operations staff responsible for updating account records. It focuses on business continuity across account types, not on migrating a particular email provider.

Which accounts should be updated first?

Start with accounts where losing access, missing a payment notice, or failing to answer a customer could interrupt business. A login email, a public contact address, a billing recipient, and a recovery address may be separate fields. Do not assume that changing one updates the others.

Use this priority order as a working rule:

1. Store and marketplace administration: Sign-in, security alerts, and account recovery.
2. Payments, payouts, and billing: Payment notifications, invoices, security checks, and recovery.
3. Customer and supplier communication: Public contact details, service inboxes, reply addresses, and signatures.
4. Business-critical SaaS: Tools that hold operating data, support orders, or renew automatically.
5. Short-term evaluations and unused accounts: Review whether they still need access or ongoing notices before making changes.

A practical case: a seller updates the email printed on the storefront but leaves the administrator login and recovery address unchanged. Customers can reach the new address, yet a security check or password reset may still go to the old mailbox. The account’s visible contact details and its access route serve different purposes, so each needs its own check.

Store and marketplace accounts: check access before public details

For each selling platform, inspect the fields for login, account contact, security notifications, and recovery separately. Some platforms may use one address for several purposes; others may let you set them independently. The platform’s help page, rather than a general assumption about domain changes, should determine what to change.

Shopify’s guidance for updating an account email explains the account-level change, while its separate store email setup instructions cover store email settings and verification. These are distinct tasks. If a store uses a different customer-facing address from the administrator’s sign-in email, changing one does not establish that the other has changed.

A safe operating sequence is:

• Sign in through the existing, authorized account.
• Identify the current login email, contact email, security-notification address, and recovery method.
• Change the login or account email using the platform’s official instructions.
• Complete any confirmation sent to the new address.
• Review store contact and customer-facing email settings separately.
• Confirm that password recovery and security notices can reach a channel the business controls.

If the old inbox is already inaccessible, use the platform’s official recovery process rather than creating a new account or repeatedly attempting changes. Shopify’s account recovery guidance describes what to do when the original email can’t be accessed. The relevant steps may depend on the account situation, so follow the current instructions rather than treating domain migration as an automatic recovery event.

Billing and payout accounts: keep notices and recovery separate

Billing and payment accounts deserve high priority because they can carry invoices, payout updates, security challenges, and notices about account activity. Check which address receives each type of message. A billing contact saved in a platform profile may not be the same as the login email, and neither should be assumed to be the recovery address.

Keep these accounts on a mailbox the business expects to maintain. A short-lived address is a poor choice for an account that may need a password reset or a response to a payment review. Likewise, don’t rely on the idea that changing the company domain will move every notification automatically. The actual result depends on the platform’s settings and the email provider’s handling of the old domain.

For every payment, payout, or invoicing service, record the address currently assigned to:

• Sign-in and security verification.
• Billing notices and invoices.
• Payment or payout notifications.
• Recovery and administrator contact.

After changing an address, look for a confirmation message and review the account settings again. Where the platform provides a test or notification option, use it; otherwise, check for the next legitimate account message and confirm its recipient. Don’t trigger unnecessary transactions just to test email delivery.

Mid-migration comparison: match the address to the account’s job

Not every registration needs the same kind of inbox. The key decision is whether the address controls a continuing business relationship, receives information needed for operations, or is only being used for a low-risk evaluation.

A temporary inbox can separate a low-risk signup from the main business inbox, but it is not a substitute for a company mailbox. The distinction between an email alias and a temporary address can help when deciding how to handle optional registrations. For accounts that only need an isolated signup address, the guide to protecting your email when signing up offers another way to think about the trade-off. For an account tied to transactions, customer history, or business recovery, use a durable address the business can access over time.

The tables are a prioritization aid, not a claim that every platform offers these exact fields. Account labels and settings vary. Check the official help material for each service before changing a field that could affect sign-in or recovery.

Customer and supplier communication: update both the address and the reply path

A domain change is visible to customers if old contact details remain on a storefront, invoice, support page, order message, or email signature. Review each place where a customer or supplier might copy an address. Update it only after the replacement mailbox is active and monitored.

Then send a message to the new address from an independent mailbox you control, or ask a trusted business contact to send a normal test message. Confirm receipt, check the displayed recipient, and reply to verify that outbound messages use the intended sender address. This does not prove universal deliverability, but it can catch basic configuration mistakes such as an incorrect address or an unattended inbox.

Keep these functions distinct:

• Receiving address: Where incoming customer or supplier messages arrive.
• Sending address: The address shown when staff reply.
• Account login: The address used to access a platform or service.
• Recovery address: The channel used to regain access or verify identity.

A change to the public contact address may not change the login or recovery address. Also review saved templates, signatures, website contact pages, and any customer-service instructions that direct people to the old domain. If multiple staff handle replies, make sure they know which address is now responsible for each type of conversation.

SaaS accounts: update tools according to business consequences

Sort SaaS accounts into two groups. The first contains tools that remain part of daily operations: for example, systems handling inventory, orders, customer support, accounting, or marketing workflows. Update those to a long-term business-controlled address, especially if they contain business data, renew automatically, or use email for recovery.

The second group contains evaluation accounts that no longer support a current decision. Before changing them, check whether the business still needs access to saved data, invoices, renewal notices, or a cancellation confirmation. If the evaluation has ended and the account can be closed without losing needed records, document the decision and follow the provider’s instructions. If access may still be needed, update the address rather than assuming the old mailbox can stay available.

A SaaS login email does not necessarily update when the company’s domain changes. Google Workspace documents the scope and conditions for changing a primary domain and separately describes how changing a user’s email can affect services. Microsoft 365 also provides specific administrator instructions for changing a user name and email address. These instructions concern those services and their stated conditions; they do not establish a universal rule for third-party SaaS accounts. Check each tool’s own account settings.

How can you confirm store and billing notices reach the new address?

Use an account register rather than relying on memory or a shared inbox search. Give every account one row, and track the email fields separately. A compact register can include:

Use this checklist for each account, not just once for the whole migration:

• [ ] Record the account’s business purpose and the person responsible for it.
• [ ] Identify the login, public contact, billing, notification, and recovery addresses that are actually configured.
• [ ] Read the provider’s current instructions for changing the relevant field.
• [ ] Change the address and complete any confirmation the provider requires.
• [ ] Check that the new mailbox receives the relevant notice.
• [ ] Sign out only when appropriate, then confirm that the new address works for the next authorized sign-in or recovery check.
• [ ] Update customer-facing pages, signatures, templates, and supplier records that still show the old address.
• [ ] Record whether the old address must remain available and who is responsible for monitoring it.

If the business uses Google Workspace or Microsoft 365, distinguish changes made in the organization’s email administration from changes held inside third-party services. The administrator’s domain configuration may affect user addresses or connected applications under specific conditions, but it does not establish that every store, payment service, or SaaS account updates its own stored email. Check each account register entry against the relevant platform documentation.

How long should you keep the old address?

There is no safe universal retention period to apply to every company domain change. The old mailbox’s availability depends on the email provider, domain arrangements, and the organization’s own configuration. Account recovery requirements also differ by platform. Don’t set a retirement date based on a general rule or assume that forwarding from the old address will work indefinitely.

Keep the old channel available while high-priority accounts still depend on it, or while the business has not verified where their security and recovery messages go. Before closing or changing service for the old domain, ask the email provider what happens to the mailbox, aliases, and any forwarding configuration. Treat forwarding as a possible continuity measure only when the provider confirms that it is configured and available; it is not proof that every message will be delivered or that every platform will accept it.

The old address can be considered for retirement only after the account register shows that critical login, billing, customer, security, and recovery functions have been reviewed and the replacement route has been tested. If an account still sends an essential message to the old address, resolve that dependency first or assign a responsible person to monitor the old mailbox under the provider’s rules.

A clean handoff is more reliable than a rushed shutdown

The migration is complete when the business knows which address serves each function, has verified the new route for important accounts, and has assigned responsibility for any remaining old-domain mail. That is more useful than simply seeing the new domain on a company website.

For critical store, payment, customer, and account-recovery access, keep using a durable mailbox controlled by the business. For a one-off, low-risk signup that should not add marketing mail to that operational inbox, OrbForward may be a convenient separate receiving option. It is not a company-domain migration tool or a guarantee of account recovery. Once the essential account updates are documented, the remaining short-lived signups can be handled separately without exposing the main business address by default.