Built for Enterprise Scale

This is the only time that will require manual intervention. An admin needs to update the MX records or mail gateway routing rules to point inbound mail traffic to your standby environment (Google Workspace). Users log into their secondary accounts via their standard email clients or webmail and then work normally on the standby system.

Yes. What is required in advance is proper user provisioning and account mapping: each Microsoft 365 user who needs continuity access must have a corresponding Google Workspace account, and the synchronization service must know which Microsoft account maps to which Google account.

For a true continuity setup, those Google Workspace accounts should have an independent sign-in path, so access to the standby environment does not depend on the Microsoft identity layer that may be affected by the incident.

Once the service is running, administrators can access selected Google Workspace accounts at any time to verify that mailbox items, calendars, contacts, and documents are available and up to date. This is the basic technical validation: it confirms that synchronization is working and that the standby environment contains the expected data.

For a broader BCP exercise, the standby environment can be included in the same type of controlled scenario testing you would use for any continuity capability. For example, a pilot group or department can be asked to operate from Google Workspace for a defined period, validate recent email and calendar data, send and receive messages, open critical documents, and confirm that the agreed working procedures are usable.

Where appropriate, the exercise can also simulate Microsoft 365 unavailability for that pilot group by temporarily restricting their access to Microsoft 365 during the test window.

The test can also cover the operational steps around the technology: how failover is declared, how users are informed, how mail routing or access instructions are handled, how support is provided during the exercise, and how users are instructed to return to Microsoft 365.

The result is evidence not only that the data is synchronized, but that the standby environment can support the continuity process defined in your BCP. Typical test records would include the scope of the exercise, users involved, access restrictions applied, data checked, access times, issues found, and any updates made to the runbook.

During failover, users will be working in Google Workspace. As soon as Microsoft 365 becomes available again, the fallback mechanism will start automatically, and email sent and received during failover will be synchronized back to Microsoft 365. The process will continue in the background until the items available in both systems are the same.

Once the primary environment (Microsoft 365) stabilizes, the software’s bidirectional sync automatically catches up the primary site with the changes made during the outage. You simply redirect your MX/gateway records back to the primary environment at your convenience, with no rushed cutover. When users go back to the primary environment, all their documents and mailbox items from before and during the outage will be there with no data lost.

Yes, absolutely. It is available as SaaS (Software as a Service), with our safe cloud at your disposal. Our SaaS platform offers data residency in two distinct geographic locations: the United States of America and the European Union. You choose where your data will be stored based on your preferences for regulatory or policy reasons.

Yes. Because it operates at the mailbox layer rather than the underlying infrastructure layer, it natively supports multi-region setups across geographically distributed data centers.

If the email addresses or UPNs differ between the primary and standby environments, administrators can define custom mapping rules (using Excel/CSV imports or manually) to match a primary mailbox (A@company.com) to a completely different standby mailbox (B@backup-domain.com).

Yes. This is done by adjusting the polling interval.

You can choose between two models:

• Subscription license (per sync pair, per month or year) – best for flexibility and OPEX budgeting, available for SaaS deployments.
• Perpetual license (one-time purchase per sync pair) – best for long-term ownership and CAPEX budgeting, available for self-hosted deployments.

A sync pair is a group of 2 users participating in a synchronization. Or simply put: a pair of email addresses whose features need to be synchronized.

License activation is straightforward: after installation, you request a license, and then activate it.