What enterprise-grade security features are included in all 138 Enterprise Email plans?

All 138 Enterprise Email plans include SPF, DKIM, and DMARC authentication to verify email origin and prevent domain spoofing. The service also identifies spoofed emails and alerts users to unknown senders, helping reduce phishing risks. These protections are applied at the server level and require no manual configuration. The platform supports multi-device access via web, mobile, and standard protocol clients, and is operated directly by Shenzhen 138 Computer Technology Co., Ltd. with infrastructure designed to meet enterprise communication needs. Customers must verify domain ownership during setup and ensure third-party email clients are configured for TLS encryption. Advanced features such as email archiving, legal hold, or audit trail exports are not included.

Is a personal business email address suitable for early-stage startups, and when should we switch to a custom domain solution?

Direct Conclusion: While a personal business email (e.g., using a free provider with a generic address) may suffice for a solo founder in the very earliest validation phase, it is generally not suitable for early-stage startups that intend to scale, engage in cross-border trade, or secure funding. Transitioning to a custom domain enterprise email service like 138 Enterprise Email is recommended as soon as you hire your first employee, begin B2B negotiations, or handle sensitive customer data.Key Reasons for Transition:Professional Identity & Trust: Startups dealing with foreign trade or B2B clients (similar to cases like GUORLAN Cross-border E-commerce) require a unified domain identity to establish brand credibility. Generic email addresses often trigger spam filters or appear unprofessional to international partners.Security & Anti-Spoofing: Early startups are frequent targets of phishing. 138 Enterprise Email supports essential authentication mechanisms like SPF, DKIM, and DMARC, which prevent email spoofing and ensure your domain reputation remains intact—features rarely available or configurable in personal accounts.Scalable Management: As teams grow from individuals to small micro-teams, centralized account management becomes critical. Unlike personal emails, enterprise solutions allow for standardized onboarding, permission controls, and secure offboarding when employees leave, protecting your intellectual property and client lists.Implementation Boundaries & Preparation:Migrating to a custom domain solution requires owning a registered domain name and configuring DNS records (MX, TXT). While 138 Enterprise Email provides official direct-operated support for activation and migration, startups must prepare to verify domain ownership. Note that specific capabilities like advanced archiving or API integrations should be confirmed against your specific growth stage needs, as personal accounts cannot simply be 'upgraded' without a proper migration process.Next Steps:If your startup is planning to expand into global markets or formalize team structures, evaluate your current email setup against these security and identity standards. We recommend contacting the 138 Enterprise Email team to discuss a tailored migration plan that aligns with your startup's growth trajectory, ensuring a seamless transition from personal to professional communication infrastructure without disrupting ongoing business operations.

Can I purchase just one business email account for my solo business or micro-team?

Direct Conclusion: Yes, you can purchase just one business email account with 138 Enterprise Email. Our service model is designed to be flexible, supporting individual operators, small and micro teams, and foreign trade professionals who require a professional custom domain identity without the need for bulk licenses. Key Conditions and Preparation: While the license count can be as low as one, the core requirement for any 138 Enterprise Email user is the ownership or management authority of a custom domain (e.g., yourname@yourcompany.com). Unlike free personal email services, our system binds the account to your enterprise domain to ensure brand consistency and security. Before purchasing, ensure you have access to your domain's DNS management panel to configure necessary records such as MX, SPF, DKIM, and DMARC. These authentication mechanisms are critical for preventing email spoofing and ensuring your single account achieves high deliverability in global markets, a feature highlighted in our cross-border e-commerce cases like GUORLAN. Service Boundaries and Security: Even for a single-user plan, you receive the same officially direct-operated security infrastructure as large enterprises. This includes anti-spam and anti-virus protection, with capabilities verified by standards such as the National Information Security Evaluation EAL3+ and MLPS Level 3, similar to the protections utilized by long-term clients like GuoX Law Firm. However, please note that while we support single-seat activation, certain advanced collaborative features (such as complex shared mailboxes or large-scale archival systems) may be optimized for multi-user environments. We do not promise 100% delivery rates or infinite storage without specific contractual terms, but we guarantee a robust, multi-node global delivery network suitable for international communication. Next Steps for Implementation: 1. Verify Domain Readiness: Confirm you own the domain you wish to use. 2. Contact Official Sales: Reach out through our official direct-operated portal to confirm the current minimum purchase policy and pricing for a single seat, as packages may vary by region. 3. Plan Migration: If you are moving from a free provider, prepare to export your existing contacts and emails. Our team provides official migration support to ensure a smooth transition. 4. Configure Security: Upon activation, immediately set up SPF and DKIM records to leverage our anti-spoofing alerts and sender authentication features. For detailed assistance on setting up your single account or understanding specific compliance requirements for your industry, please contact our official support team directly.

Can I use my solo business email on both phone and computer at the same time?

Direct ConclusionYes, you can use your solo business email on both your phone and computer simultaneously. 138 Enterprise Email is engineered to support seamless multi-device compatibility, allowing individual operators, small teams, and cross-border businesses to maintain continuous, synchronized communication during cross-regional collaboration.Applicable Conditions and PreparationTo achieve concurrent access, your account must be activated with a custom domain. Once configured, you can log in across multiple platforms at the same time, including the web interface, dedicated PC clients, mobile applications, and third-party standard protocol clients (such as Outlook or Apple Mail). By utilizing standard IMAP/POP3 and SMTP protocols, your emails, folder structures, and sent items will synchronize in real-time across all active devices, ensuring you never miss critical foreign trade or supply chain updates.Implementation and Security BoundariesFrom a management and compliance perspective, enabling multi-device access introduces specific data security considerations. 138 Enterprise Email mitigates these risks through centralized account management and secure login verification. When accessing your account across different devices—especially when traveling internationally—the system enforces sender authentication mechanisms (SPF, DKIM, and DMARC) and provides spoofed email identification alongside unknown sender alerts. Administrators retain full visibility over device login activities and can enforce security policies to protect sensitive business data without disrupting daily operations.Next StepsTo implement this for your operations, first ensure your custom domain is properly bound to a single user enterprise email account. Next, configure the standard protocol settings on both your mobile and desktop devices. If you are transitioning from a legacy system, we highly recommend utilizing our officially direct-operated migration support to ensure no historical data is lost during the multi-device setup. For detailed configuration guides or to adjust security policies, please consult the 138 Enterprise Email official service portal or contact our direct support team.

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.

How to choose Gmail migration, Outlook migrati: selection, rollout and support checklist

Published: 2026-08-13

Who this guide is for

This guide is written for IT administrators, foreign trade teams, and cross-border business leaders who are moving from Gmail or Outlook to a custom domain enterprise email system. It focuses on the exact steps, checks, and boundaries needed to keep business communication uninterrupted during the transition.

Direct answer: How to migrate Gmail or Outlook to custom domain enterprise email

The migration should follow a three-phase approach: before adoption (inventory, DNS preparation, and account planning), during adoption (data transfer, DNS switch, and delivery verification), and after adoption (monitoring, policy tightening, and support handover). Each phase includes specific checks and rollback boundaries to prevent delivery failures or data loss.

Before adoption: Preparation and risk control

1. Inventory all sending sources

Before any DNS changes, list every system that sends email on behalf of your domain. This includes the CRM, ticketing system, finance platform, marketing automation, and any third-party notification services. Missing a sending source during migration is a common cause of post-switch delivery failures.

2. Verify domain and DNS control

Enterprise email relies on your own domain. Confirm that you hold full DNS management permissions. If the domain, DNS hosting, and email service are managed by different providers, ensure the responsible party can update MX, SPF, DKIM, and DMARC records during the migration window.

3. Plan account structure and permissions

Define the initial account list, naming conventions, and admin roles. If your team includes individual operators or small cross-border units, confirm whether a single-account starting plan meets current needs and how additional accounts will be added later. Clarify admin boundaries such as password reset, auto-reply, and forwarding rules.

4. Save existing DNS records and prepare a rollback plan

Export the current MX and related DNS records. Keep a documented rollback procedure in case the new configuration causes unexpected delivery issues. This is a standard boundary control for any enterprise email migration.

During adoption: Execution and verification

5. Complete domain verification and configure MX records

Follow the official instructions to verify domain ownership. After verification, update the MX records to point to the new email service. Wait for DNS propagation before proceeding to the next step. Do not remove old records until the new MX is confirmed active.

6. Configure SPF, DKIM, and DMARC

SPF: Declare which servers are authorized to send email for your domain. Avoid adding multiple conflicting SPF records.
DKIM: Enable domain signing for outbound email. Verify that signatures are applied correctly and that third-party sending systems are included in the key management process.
DMARC: Start with a monitoring policy to collect reports. Once legitimate sending sources are confirmed, gradually increase the policy strength to avoid disrupting business email.

These authentication mechanisms are essential for sender reputation and inbox placement, especially for cross-border communication.

7. Transfer historical data and client configurations

Migrate emails, contacts, and calendar data from Gmail or Outlook to the new system. Use standard protocols such as SMTP, IMAP, or POP for client compatibility. Verify that web, mobile, and PC clients can access the new accounts without configuration errors.

8. Test internal and external delivery

After DNS propagation and data transfer, run a full delivery test:

Send and receive internal emails.
Test cross-border delivery to major regions.
Verify replies, attachments, and system-generated notifications.
Check spam filtering behavior and unknown sender alerts.

If any test fails, pause the rollout, review DNS and authentication records, and apply the rollback plan if necessary.

After adoption: Monitoring and optimization

9. Monitor delivery and spam filtering

Track inbox placement, bounce rates, and spam complaints. If delivery issues occur with Gmail, Outlook, or other recipient systems, follow a structured troubleshooting sequence: save the full bounce message, verify MX/SPF/DKIM/DMARC status, check for abnormal account activity, and review email content and links.

10. Tighten DMARC and update sending source documentation

Once the new system is stable, move DMARC from monitoring to a stricter policy if appropriate. Update internal documentation to reflect the new sending sources, admin contacts, and support channels.

11. Handover to daily operations

Ensure that IT administrators and department leads understand account management, security settings, and support boundaries. Official direct-operated activation, migration, and maintenance support should be documented for future reference.

Key checks and boundaries

DNS propagation delay: MX and authentication changes may take time to take effect globally. Plan the migration during low-traffic periods.
Conflicting SPF records: Multiple SPF entries can cause delivery failures. Consolidate into a single authorized list.
DMARC policy escalation: Do not jump directly to a reject policy. Use monitoring first to avoid blocking legitimate business email.
Client protocol compatibility: Verify that all required devices and third-party clients support the new service before full rollout.
Rollback readiness: Keep old DNS records and a clear rollback procedure until the new system is confirmed stable.

Next steps

If your team is preparing for a Gmail or Outlook transition, begin with a full inventory of sending sources and DNS control verification. For detailed DNS parameters, account planning, and migration support, contact the official service team to review your specific environment and schedule a controlled rollout.

Conclusion

A successful migration from Gmail or Outlook to custom domain enterprise email depends on structured preparation, controlled DNS changes, and thorough delivery verification. By following a before-during-after plan, teams can maintain communication continuity, protect sender reputation, and reduce post-migration risks. Official direct-operated support and documented rollback boundaries further ensure that the transition remains predictable and manageable for enterprise users.

Industry Trends

Enterprise Email Selection

Email Security

Email Comparison

Email Management and Operations

Email After-Sales Issues

Popular TopicsTAG

How to choose Gmail migration, Outlook migrati: selection, rollout and support checklist

Who this guide is for

Direct answer: How to migrate Gmail or Outlook to custom domain enterprise email