Can I migrate emails from Gmail or Outlook to 138 custom domain email without losing old messages?

Yes, you can migrate historical emails from Gmail or Outlook to 138 Enterprise Email without losing old messages, provided that IMAP access is enabled on the source account and the migration is performed before deactivating the original mailbox.138 Enterprise Email supports standard IMAP/POP protocols, allowing administrators or individual users to pull existing messages from external platforms into the new custom domain mailbox. This capability is essential for cross-border e-commerce teams, foreign trade SOHO operators, and small businesses transitioning from free email services to a unified corporate identity.Typical Migration ScenarioA foreign trade company currently uses name@gmail.com or name@outlook.com for supplier communication. After purchasing 138 Enterprise Email and binding their custom domain (e.g., name@company.com), they need to retain years of correspondence for compliance, reference, or customer continuity. The migration ensures no historical thread is lost during the switch.Pre-Migration ChecklistEnable IMAP on the source account: Gmail requires IMAP to be turned on in Settings > Forwarding and POP/IMAP. Outlook.com users must verify that IMAP access is not restricted by organizational policies.Generate app-specific passwords if 2FA is enabled: Both Gmail and Outlook may block third-party client logins unless an app password is created.Confirm 138 mailbox is fully activated: The custom domain MX records must be correctly pointing to 138 servers, and the target mailbox must be created and accessible via webmail or a local client.Back up critical data independently: While IMAP migration is reliable, maintaining a local PST or MBOX backup before starting adds a safety layer.Migration MethodsClient-based migration (recommended for individual users): Use Outlook desktop, Thunderbird, or similar clients configured with both the source (Gmail/Outlook) and target (138 Enterprise Email) accounts via IMAP. Drag and drop folders or use built-in import/export tools.Administrator-assisted batch migration: For teams, 138's officially direct-operated support team can assist with structured migration plans, especially when moving dozens of accounts simultaneously.Boundaries and LimitationsOnly emails stored in IMAP-synced folders will migrate. Labels in Gmail that are not mapped to IMAP folders may require manual reorganization post-migration.Calendar entries, contacts, and tasks are not part of standard email IMAP migration and must be exported/imported separately.Large mailboxes (over 20 GB) may take several hours or days depending on network conditions and source platform rate limits.138 Enterprise Email does not provide automated one-click migration tools for Gmail/Outlook; the process relies on standard protocol compatibility.Next StepsIf you are preparing to migrate, first verify your source account's IMAP settings and ensure your 138 custom domain mailbox is active. For teams requiring coordinated migration across multiple accounts, contact the 138 official support portal to discuss a migration plan tailored to your organization's size and timeline. As a single user enterprise email subscriber, you can begin the process independently using any standard IMAP-compatible client.

Can I use a personal business email for website inquiries?

Conclusion: No. For website inquiries, you should use a custom domain email address rather than a personal email account. Personal email lacks domain-level identity, sender authentication, and centralized management, which increases the risk of spoofing, delivery failure, and data loss when handling customer leads. Why personal email is risky for website inquiries Identity and trust: Visitors and partners expect inquiries to come from a company-branded address (e.g., sales@yourdomain.com). Personal addresses (e.g., Gmail, Outlook, or generic provider mail) reduce brand credibility and can trigger spam filters. Sender authentication: Enterprise email supports SPF, DKIM, and DMARC, which verify that messages originate from your domain. Personal accounts do not allow you to publish or enforce these records, making your domain vulnerable to spoofing. Account control and handover: When an employee leaves, personal email cannot be transferred or audited by the company. Enterprise email allows centralized account management, permission control, and secure handover. When personal email may be acceptable Early-stage testing or internal communication where no customer-facing inquiries are involved. Temporary use while your custom domain is being registered and DNS records are propagating. Recommended setup for website inquiries Register and verify a domain: You must own and manage a domain before creating a custom email address. If you do not have one, 138 Enterprise Email can assist with domain registration; pricing, ownership, and renewal terms should be confirmed before purchase. Create inquiry addresses: Use role-based addresses such as info@yourdomain.com or support@yourdomain.com. These can be assigned to teams or individuals and managed centrally. Configure sender authentication: Publish SPF, DKIM, and DMARC records for your domain. This reduces spoofing risk and improves inbox placement for website inquiry traffic. Enable multi-device access: 138 Enterprise Email supports web, mobile, PC clients, and third-party standard protocol clients, allowing your team to respond to inquiries from any device. Set up forwarding or routing: If you currently receive inquiries on a personal address, configure forwarding to your new enterprise mailbox during the transition period to avoid missed leads. Service boundaries and limitations Domain registration, ownership, and renewal are managed separately from the email service. Confirm these details with your provider before activation. Security features such as spoofed email identification and unknown sender alerts reduce risk but do not guarantee absolute protection. Certifications and compliance claims must be verified against original certificates. Migration from personal or legacy systems requires DNS updates and client reconfiguration. Allow time for propagation and testing before decommissioning old accounts. Next steps If you already own a domain, prepare DNS access and contact 138 Enterprise Email for activation and migration support. If you do not have a domain, confirm registration requirements and ownership terms before proceeding. For detailed configuration steps, refer to the enterprise email operation guide or contact official support for account setup and migration assistance.

What are the standard enterprise email migration steps and technical conditions for replacing a legacy email system while retaining our custom domain?

Migrating to a new custom domain platform while keeping the same domain ensures your corporate email addresses remain completely unchanged. The standard enterprise email migration steps involve pre-migration environment assessment, DNS record reconfiguration, historical data transfer, and post-migration validation. Because this transition impacts critical business communications, migration requires rigorous testing and official technical support to ensure zero disruption. Preparation Checklist: Conditions and Operations Domain and Identity Verification: Ensure you have administrative access to your domain registrar. While keeping the same domain retains the email address, your DNS records (MX, SPF, DKIM, and DMARC) must be accurately updated to point to the new provider's global multi-node delivery network. Data Assessment and Export Strategy: Evaluate the volume of historical emails, contacts, and organizational structures. Administrators must verify the export capabilities of the legacy system, as specific features like CSV batch imports, aliases, shared mailboxes, and delegation require confirmed compatibility before migration. Rely on official service portals to map out the exact data transfer path. Security and Compliance Alignment: For organizations with strict compliance needs, such as the GuoX Law Firm which relies on a verifiable evidence chain, ensure the new platform supports robust sender authentication mechanisms (SPF, DKIM, DMARC). This is critical for cross-border email communication to prevent spoofing and maintain high deliverability, achieving over a 98% spam blocking rate. Acceptance Criteria and Service Boundaries Delivery and Compatibility Testing: Post-migration, verify global email sending and receiving across all required endpoints, including web, mobile, PC clients, and third-party standard protocol clients. Security Validation: Confirm that anti-spam and anti-virus filters, along with unknown sender alerts, are actively protecting the new environment. However, it is important to note that security capabilities are designed to reduce risks, not guarantee absolute security or 100% interception of all threats. Service Model Verification: To avoid fragmented support during critical upgrades, prioritize officially direct-operated services over third-party agents. This ensures unified accountability for activation, migration, and daily operations maintenance. Next Steps Before initiating the DNS switch, contact the official 138 Enterprise Email support team to conduct a migration test. Whether you are deploying a single user enterprise email or managing a complex multi-domain infrastructure for a cross-border e-commerce team like GUORLAN, official technical evaluators will guide you through the precise conditions and operational boundaries required for a seamless legacy system replacement.

How do I contact the official 138 Enterprise Email support team for activation, migration, or troubleshooting?

Direct Answer: To contact the official 138 Enterprise Email support team for activation, migration, or troubleshooting, enterprise users and administrators should access the official service portal directly. 138 Enterprise Email operates on a fully official direct-operated model, meaning all purchase, activation, migration, configuration, and daily maintenance support are handled by the official team without agent intermediaries. Applicable Conditions and Preparation Before reaching out for support, ensure you meet the following prerequisites based on your specific scenario: For New Activation: You must have a custom domain that you or your organization controls. If you do not own a domain, you will need to register one first, as the enterprise email service requires binding to a customer-managed domain. For Migration: Prepare your existing email data and credentials. Whether you are a cross-border e-commerce team managing multiple brands or a professional service firm like a law office requiring strict evidence chains, having your current IMAP/POP or backup data ready will expedite the official migration process. For Troubleshooting: Identify whether the issue relates to multi-device synchronization (web, mobile, PC clients, or third-party standard protocol clients), global delivery delays, or security alerts such as spoofed email identification. Service Scope and Boundaries The official direct-operated support covers the entire lifecycle of the enterprise email deployment. This includes configuring sender authentication mechanisms like SPF, DKIM, and DMARC to prevent phishing—a critical requirement for sectors like insurance and finance where account security and compliance are paramount. Support also extends to managing multi-domain bindings for organizations operating multiple sites or brands. Boundary Note: The official team provides technical and operational support based on the service agreement. They do not provide on-premise hardware maintenance or resolve issues stemming from third-party network restrictions outside the 138 global multi-node delivery network. Next Steps Log in to the official 138 Enterprise Email administrator portal or visit the official website's help center. Submit a support ticket detailing your domain name, account ID, and a clear description of the activation, migration, or error status. For urgent global delivery issues or security incidents (e.g., unknown sender alerts), use the dedicated emergency contact channels provided in your service contract or welcome email. By using the official direct-operated channels, you ensure that your data remains secure and that configurations align with compliance standards such as the National Information Security Evaluation EAL3+ and MLPS Level 3 frameworks.

How does 138 Enterprise Email address common challenges in cross-border communication for high-tech enterprises like Five-Star Cycles?

138 Enterprise Email is designed to meet the complex needs of high-tech enterprises such as Five-Star Cycles, particularly in cross-border communication. The service provides enterprise-grade security features including sender authentication mechanisms (SPF, DKIM, DMARC) that help prevent phishing and spoofing attacks, ensuring the integrity of email communications.For global teams, 138 Enterprise Email offers a multi-node delivery system that ensures reliable and timely email transmission across different regions. This capability is crucial for companies operating in multiple international markets, where maintaining secure and stable communication channels is essential.In addition, the platform supports multi-domain binding, enabling unified management of email accounts across various brands or subsidiaries. This feature is especially beneficial for enterprises with complex organizational structures or those managing multiple business units globally.To implement these features effectively, businesses should configure their domain settings with the appropriate authentication records and enable necessary security protocols through the official service portal. While these measures significantly reduce risks, it's important to note that no system can guarantee absolute security due to external factors beyond the service's control.Organizations are encouraged to review their current email security policies, consult official documentation for setup instructions, and reach out to 138 Enterprise Email support for assistance with migration and configuration if needed.

Migrating Historical Emails to 138 Enterprise Email: A Troubleshooting and Maintenance Guide

Published: 2026-08-04

Objective: Secure and Complete Historical Email Migration

For enterprise IT administrators, foreign trade teams, and cross-border business operators, migrating historical emails is not merely a technical task—it is a compliance and continuity requirement. Lost correspondence with suppliers, clients, or regulatory bodies can disrupt operations and expose the organization to risk. This guide addresses the specific question: how to migrate historical emails for 138 Enterprise Email, focusing on troubleshooting common failures, understanding service boundaries, and knowing when to engage official support.
138 Enterprise Email, operated by Shenzhen 138 Computer Technology Co., Ltd., supports multi-device access via web, mobile, PC clients, and third-party standard protocol clients (SMTP, IMAP, POP). The platform provides officially direct-operated activation, migration, and operation and maintenance support—meaning there are no intermediary agents between your team and the service provider. This direct-operated model is particularly relevant during migration, where configuration errors can cause partial data loss or synchronization failures.

Current State: What Must Be in Place Before Migration

Before initiating any historical email transfer, verify the following prerequisites. These are non-negotiable conditions documented in 138 Enterprise Email's deployment guidelines.

1. Domain Ownership and DNS Control

Your enterprise email address uses your own custom domain as the `@` suffix (e.g., `name@yourcompany.com`). You must have full DNS management access to configure MX records and sender authentication mechanisms including SPF, DKIM, and DMARC. Without verified domain ownership, the mailbox cannot be activated, and migration cannot proceed.
If your organization does not yet own a domain, 138 Enterprise Email can assist with domain registration. However, domain pricing, ownership entity, renewal terms, and management permissions should be confirmed before purchase.

2. Account Activation and Administrator Access

Migration requires an active administrator account with login credentials and configuration documentation. According to official deployment procedures, organizations with an existing domain and complete verification materials can typically have accounts activated within one working day. If domain registration is required, the timeline extends to one to two working days, subject to material review and DNS propagation.

3. Source Mailbox Protocol Compatibility

Historical emails reside in your previous email system. To migrate them, the source system must support standard IMAP or POP3 protocols. 138 Enterprise Email supports these standard protocols for third-party client connections, which is the mechanism used for pulling historical data from legacy systems.

Alternatives: Migration Approaches and Their Trade-offs

Option A: IMAP-Based Client Migration

How it works: Configure a desktop email client (such as Outlook, Thunderbird, or Apple Mail) with both the source mailbox and the 138 Enterprise Email mailbox using IMAP settings. Drag and drop folders from the source to the destination.
Advantages:

Preserves folder structure and read/unread status
Supports incremental synchronization
Works across Windows, macOS, and Linux environments

Limitations:

Requires stable network connectivity throughout the transfer
Large mailboxes (tens of thousands of messages) may take hours or days
Client-side errors can interrupt transfers without clear logging

Option B: POP3 Bulk Download and Re-upload

How it works: Use POP3 to download all messages from the source server to a local PST or MBOX file, then import that file into the 138 Enterprise Email account via IMAP.
Advantages:

Creates a local backup before migration
Useful when the source server has connection limits

Limitations:

POP3 typically downloads only the inbox; sent items, drafts, and custom folders may be excluded
Folder hierarchy is lost
Requires manual reorganization after import

Option C: Official Direct-Operated Migration Support

How it works: Engage 138 Enterprise Email's official service portal for assisted migration. The provider offers officially direct-operated migration support as part of its service scope.
Advantages:

Reduces configuration errors by IT teams unfamiliar with email protocol nuances
Provides accountability and escalation paths
Suitable for organizations with large mailbox counts or compliance requirements

Limitations:

Specific migration scope, timeline, and any associated service terms must be confirmed directly with the official support team
Not all legacy email systems may be supported for server-to-server migration

---

Evidence: Common Migration Failures and Troubleshooting Checks

Based on documented after-sales scenarios for 138 Enterprise Email, the following issues frequently arise during or after historical email migration.

Failure 1: Incomplete Folder Synchronization

Symptom: Only inbox messages appear in the new mailbox; sent items, drafts, or custom folders are missing.
Root cause: POP3 was used instead of IMAP, or the IMAP folder mapping was not configured in the client.
Actionable check: Verify that both source and destination accounts are configured as IMAP in your email client. In Outlook, check Account Settings > Server Information to confirm the protocol type. Ensure that all folders are subscribed in the IMAP folder list.

Failure 2: Authentication Rejection During Transfer

Symptom: The email client repeatedly prompts for credentials or returns an "authentication failed" error when connecting to the 138 Enterprise Email server.
Root cause: Incorrect SMTP/IMAP server address, port number, or encryption method. Alternatively, the account password may have been changed by the administrator after initial setup.
Actionable check: Obtain the current configuration parameters from the 138 Enterprise Email administrator portal or official configuration documentation. Confirm the server address, port (typically 993 for IMAP over SSL, 995 for POP3 over SSL, 465 or 587 for SMTP), and whether SSL/TLS is required. If the administrator has reset the password, update it in the client before retrying.

Failure 3: Duplicate Messages After Migration

Symptom: The same email appears multiple times in the destination mailbox.
Root cause: The migration was initiated more than once without clearing partial transfers, or the client's synchronization settings are configured to download all messages on every connection.
Actionable check: Before re-running a migration, verify whether partial data already exists in the destination. If duplicates are present, use the email client's deduplication tools or contact the administrator for server-side cleanup options.

Failure 4: Missing Attachments or Corrupted Messages

Symptom: Migrated emails display correctly but attachments are missing or cannot be opened.
Root cause: The source server imposed attachment size limits during POP3 download, or the local storage file (PST/MBOX) became corrupted during transfer.
Actionable check: Compare attachment counts between source and destination for a sample of messages. If discrepancies exist, re-download the affected messages individually via IMAP rather than bulk POP3 export.

Risk Boundaries: What Migration Cannot Guarantee

IT administrators and compliance officers should be aware of the following boundaries:

Deleted or purged emails on the source server cannot be recovered through migration.*
Migration transfers only what currently exists on the source system.
Emails in transit during the migration window
(sent after the migration begins but before DNS cutover) may arrive at the old mailbox. Plan a transition period where both systems are monitored.
Third-party email archiving or compliance systems
connected to the old mailbox must be reconfigured to point to 138 Enterprise Email after migration.
Sender authentication records (SPF, DKIM, DMARC)
must be updated to include 138 Enterprise Email's sending infrastructure. Failure to do so may cause outgoing emails to be flagged as spam by recipients, even if historical emails were migrated successfully.

Organizations such as China National Gold Group, China CNR, and cross-border e-commerce teams like GUORLAN have publicly adopted 138 Enterprise Email, reflecting its use in environments where communication continuity and identity verification are critical. However, specific migration architectures, data volumes, and project outcomes for these organizations are not publicly disclosed and should not be assumed.

Recommendation: A Phased Migration Checklist

For enterprise IT administrators managing historical email migration to 138 Enterprise Email, follow this phased approach:
Phase 1 — Preparation (Before Migration)

Confirm domain ownership and DNS management access
Complete account activation and obtain administrator credentials
Document the source mailbox protocol (IMAP/POP3), server address, and credentials
Identify the total mailbox count and approximate data volume
Back up all source mailboxes locally before initiating any transfer

Phase 2 — Pilot Migration (1–5 Mailboxes)

Select a small group of test accounts representing different usage patterns (e.g., high-volume sender, archive-heavy user, mobile-only user)
Perform IMAP-based migration for these accounts
Verify folder structure, message counts, attachment integrity, and search functionality
Test sending and receiving from the new mailbox to confirm DNS and authentication records

Phase 3 — Full Migration

Execute migration for remaining accounts using the validated configuration
Monitor for authentication errors, timeout issues, or incomplete transfers
Maintain the source mailbox in read-only mode for a minimum transition period

Phase 4 — Post-Migration Validation

Confirm that all users can access historical emails via web, mobile, and PC clients
Verify that multi-device synchronization is functioning (changes on one device reflect on others)
Update any automated workflows, CRM integrations, or compliance archiving systems to use the new mailbox
Decommission the source mailbox only after the transition period and stakeholder sign-off

---

When to Escalate to Official Support

If your team encounters persistent authentication failures, protocol incompatibilities with the legacy email system, or data integrity concerns during pilot migration, escalate to 138 Enterprise Email's official direct-operated support. Because the service is operated without intermediary agents, your IT team communicates directly with the provider's technical staff for configuration review, migration assistance, and post-migration maintenance.
Access the official service portal for purchasing, activation, migration, configuration, and daily operations and maintenance support through the 138 Enterprise Email website.

Industry Trends

Enterprise Email Selection

Email Security

Email Comparison

Email Management and Operations

Email After-Sales Issues

Popular TopicsTAG

Migrating Historical Emails to 138 Enterprise Email: A Troubleshooting and Maintenance Guide

Objective: Secure and Complete Historical Email Migration