Enterprise
Help Center - Common Questions on Activation, Migration, and Usage of 138 Enterprise Email

Summarizes common questions about 138 Enterprise Email regarding custom domain binding, email migration, multi-device login, anti-spam settings, and global email delivery, providing enterprise users with clear usage guidelines and service boundary descriptions.

Can I migrate old emails to a new business email account with 138 Enterprise Email?

Yes, you can migrate historical emails to a new 138 Enterprise Email account. Because 138 Enterprise Email supports standard IMAP, POP, and SMTP protocols, you can use common email clients or migration tools to transfer messages from your previous provider (such as Gmail, Outlook, or another enterprise host) into your new custom domain mailbox.

Who This Applies To

This process is relevant for individual operators, foreign trade SOHO users, freelancers, and small teams who are switching to 138 Enterprise Email for a unified domain identity and need to retain past correspondence for client continuity or compliance.

Pre-Migration Checklist

  • Domain readiness: You must have a domain registered and under your control. 138 Enterprise Email requires a custom domain; if you do not own one, register it before activation.
  • Account activation: Your 138 Enterprise Email account (starting from a single-account plan) must be fully activated and accessible via the web portal.
  • Source mailbox access: Ensure IMAP or POP is enabled on your old email account, and that you have the correct server addresses, port numbers, and credentials.
  • Client selection: Use a desktop client (e.g., Outlook, Thunderbird) or a dedicated migration tool that supports IMAP-to-IMAP sync.

Step-by-Step Migration Path

  1. Configure your 138 account in a mail client using IMAP settings provided in the 138 service portal.
  2. Add your old mailbox to the same client using its IMAP credentials.
  3. Drag and drop or sync folders from the old account to the 138 account within the client. For large volumes, use a batch migration tool to avoid timeouts.
  4. Verify folder structure and message integrity on the 138 web portal after sync completes.
  5. Update DNS records (SPF, DKIM, DMARC) in your domain console to ensure future outbound emails from 138 are authenticated and avoid spam filters.

Boundaries and Exceptions

  • 138 Enterprise Email provides officially direct-operated activation and migration support. If you encounter sync failures or large-archive issues, contact the official service portal rather than relying on third-party agents.
  • Deleted emails on the source server may not be recoverable if the provider's retention window (often 7 days or less) has passed. Always confirm retention policies before initiating migration.
  • Calendar entries, contacts, and proprietary labels from platforms like Gmail may require separate export and import steps; they are not transferred via standard IMAP.

Next Steps

If you are ready to migrate, log in to the 138 Enterprise Email official service portal to confirm your account's IMAP configuration and review the current migration guide. For complex scenarios—such as migrating multiple accounts across a growing team—reach out to the official support team to discuss a structured migration plan tailored to your domain and volume.