Migration scenarios
Global Mailbox can be configured for high availability by deploying it in multiple data centers. To take advantage of the capabilities of Global Mailbox to provide high availability, migrate services and adapters, and configurations from other systems.
The following types of systems are typical migration scenarios:
- Sterling B2B Integrator to Global Mailbox
- You can migrate mailboxes, virtual roots, permissions, and routing rules from the traditional Sterling B2B Integrator mailbox realm to the Global Mailbox realm.
- Global Mailbox to Global Mailbox
- You can migrate from one Global Mailbox to another. This is useful when you want to create a test environment, create your mailboxes, virtual roots, and event rules, then move them to a production environment when you are satisfied with your data.
- Sterling File Gateway to Global Mailbox
- For Sterling File Gateway partners, you convert them to use Global Mailbox, but do not migrate them. The partners continue to be administered in Sterling File Gateway.
Important: Do not export Sterling File Gateway mailboxes to Global Mailbox by using Sterling B2B Integrator
Resource Manager. Sterling File Gateway mailboxes cannot be imported
successfully to Global Mailbox. The partner resources
to support the mailboxes are not created by importing.