Before moving business email to Proton Mail, confirm how each person will sign in, recover access and use their preferred application. This guide addresses the email part of a Proton Workspace project; other applications need their own migration and acceptance plan.
Inventory the source and destination
List mailboxes, aliases, domains, shared workflows and automated senders. Record which data must move, including older messages, contacts, calendars and local archives. Confirm the selected plan and the administrator responsible for the organization.
Proton offers Easy Switch migration workflows for supported sources. Choose the instructions matching your source and account type. For example, its Microsoft 365 business migration guide requires administrative access to both services and a cloud-hosted Microsoft source. Do not assume every source supports the same data types or permissions.
Prepare recovery before the move
Set up multifactor authentication and the recovery methods agreed with your administrator. Identify who can assist if a user loses a phone or cannot sign in. Store recovery material securely, separately from the account it protects, and verify the process before the change window.
Do not send passwords, recovery phrases or encryption keys in a support request. A screenshot of an error should exclude account secrets and unrelated personal information.
Choose the supported application path
Test the Proton web or mobile application first. If the user needs a desktop mail client such as Outlook, Thunderbird or Apple Mail, review Proton Mail Bridge requirements. Bridge requires a paid plan that includes Proton Mail, runs on supported desktop systems and is not a mobile IMAP configuration.
Follow the Bridge setup instructions for the chosen client. Use the configuration supplied by Bridge; do not copy cPanel mail-server settings into the Proton account. Website forms and scanners are a separate sending requirement to confirm with the administrator.
Run a pilot and plan delivery
Import a representative mailbox and inspect old messages, folders and attachments. Review the import report and separately test any contacts and calendars included in the chosen method. An import result and successful delivery of new messages are different checks.
Agree on the domain cutover, sender authentication records and a recovery plan before changing DNS. Test incoming and outgoing messages with an external account and all important addresses. Retain the old service until missing data and exceptions are resolved; changing DNS back does not reconcile messages between services.
Confirm what ongoing support covers
Record the working applications, recovery contact and accepted migration results. Define any retention, export or backup requirement explicitly. An imported mailbox is not proof of an independent backup, and a backup option for another provider does not establish Proton coverage.
Discuss your Proton project with Nuagerie with the source service, number of users and required applications. The agreed mandate determines migration and ongoing administration responsibilities.