Merger, Acquisition & Divestiture Services
- Integrated Messaging
- Email Branding
- Merge Windows Networks
- Migrate Documents
- Migrate Servers, Data and Applications
- Integrated ERP
- Integrated Telecommunications
Why Strategic SaaS?
Cloud integration experience
Capacity to move
your project forward
M&A Blogs – Bringing Infrastructure Together
Before Migration of Messaging
Staged Migration: A forest trust allowed us to migrate, rename, and rebrand users in batches while preserving attributes, passwords, and ACL s. Remote mailboxes could then be created, data copied, and mail routed, all without interrupting service for users. Each bat ch required a multi-step process featuring the Active Directory Migration Tool, custom PowerShell scripts, and BitTitan Migration Wizard.
During Project Migration
Pre-migration: Both source (genband.com) and target (sonus.com) environments utilized Exchange Hybrid, but only the source had active mailboxes on premises. The target utilized all Lync Hybrid features, which cemented a requirement that all migrated user mail boxes (full-time, seasonal, contractor) must have an on-premises account in order to get voice service. The source utilized ADFS and single sign-on for a number of cloud apps, but it was decided that SSO and ADFS were no longer a requirement post migration and that genband.com would be converted to a managed domain during cutover. This project was also a rebrand and cleanup opportunity, so a new child domain (rbbn.com) was to be configured in the target forest as a destination for valid, rebranded, and renamed AD objects. To validate our strategy as a platform for a potential AD migration, migrated users were to retain their attributes, passwords, and access to the genband.com resource forest during staging and potentially long-term
Post cutover: After all objects had been migrated, a cutover date was set for a tenant to tenant migration of the genband.com vanity domain. Both Genband and Sonus had continuity accounts with the same cloud filtering provider, so these were leveraged to capture mail sent to the old domain during the 17 hour transition. The end result was a single filtering account, a single Microsoft Hybrid Commun ications forest, two resource forests, all mailboxes in cloud, and all users rebranded in the rbbn.com child domain with enhanced voice service. At no time throughout the engagement were users without service to their primary account due to this process.