How it works
Start with scope, then prove the workflow
1
Define the portfolio
Share expected customer, domain, mailbox, storage, and support requirements.
2
Choose the model
Agree on the appropriate plan, responsibilities, migration scope, and customer support path.
3
Run a pilot
Start with a representative domain and verify DNS, mailbox access, migration, and delivery operations.
4
Expand deliberately
Add customer domains as the operational model and ownership boundaries are confirmed.
Commercial terms follow the actual scope
Discounts, support responsibilities, API access, branding, and commercial terms depend on customer volume and infrastructure requirements. They are not implied until agreed in writing.
