1. Create your organization
Create an account in the organization portal and choose a suitable plan. Enter your organization details, then invite only the people who need administrative access. Your everyday mailbox users don’t need admin membership.
2. Add and verify your domain
Add the part after the @, such as yourcompany.com.np. Follow the ownership verification instructions and add the DNS records shown in the portal. Your sending authentication records may appear after ownership verification.
If you currently receive mail elsewhere, keep your existing MX records while you prepare. DNS changes for mail authentication do not require moving your website. Review each record and the readiness checks before changing routing.
3. Create the team’s mailboxes
Create an address for each person and choose its quota within the plan. Share initial credentials privately, and encourage the user to change the password and enable two-factor authentication.
Use aliases for extra addresses that deliver to an existing mailbox, and groups for distribution addresses that reach their members. Availability and limits follow your plan.
4. Bring existing email
Use the migration tools to test the old provider’s connection before copying messages. Run imports in the background and inspect the result. For an IMAP source, run a final delta sync near the switch to catch newly arrived mail. The migration reads from the source without deleting messages there.
Contacts and calendars are separate from IMAP mail migration. Review their supported import and sync options independently.
5. Review readiness and switch
Check domain ownership, sender authentication, destination mailboxes, and routing readiness in the organization portal. When your team is ready, update your MX records according to the instructions and verify inbound and outbound email.
Sign in to the mailbox app, add a signature, check your calendar and contacts, and keep access to the old system until you’re satisfied with the migration results.