Seamless IT Integration for Mergers and Demergers

When considering the applications in the project scope, every one will have different considerations and potentially require different methods.

As an example, a migration of user mailboxes between two Microsoft Exchange platforms (whether on-premises or Online) will require the Quest On-Demand Migration platform .

If the data is in SharePoint or Teams, this might need to be extracted and merged into another SharePoint platform, which can also be processed using the Quest platform, or can be supplemented by using a third-party tool such as Sharegate or even custom scripts.

Modern, software-as a service applications, which are linked to user and group identities, will need to be considered during mapping activities. In all cases, changes are necessary to ensure access and functionality is maintained.

Conversely, a migration of a third-party application may require a more manual approach of data extraction and import. There may also be a requirement to manipulate the data during the process and this may require custom scripts to be developed.

As part of the analysis stage of the project, we look at each of the in-scope applications, determine the options available to complete the required activity and plan the approach accordingly.

If you have data stored in SharePoint Online, Teams, Planner, or on file servers this will need to be extracted and migrated to the target platform.

In many cases, the security of this data may be critical, so the process has to account for and manage this aspect. We always try to use a standard process and tools to meet with the needs of data migration which may include considering hybrid, cloud, or on-premises data workloads.

In all cases, the migration of data is dealt with in the most efficient, secure and effective way, retaining the existing security artifacts to ensure access to existing data is preserved.

In most cases, unless brand new devices are deployed, there may be a requirement to manage the migration or transfer of devices as part of the project. These could be desktops and laptops or mobile devices and each will use different methods.

Modern working also plays into the migration of these workloads, as typically, it cannot be assumed that a device is office-located anymore and, instead any device needs to be considered internet- connected (be that at home or somewhere else).

This provides a challenge and needs to be considered alongside VPNs, passwordless logon methods and retention of user device personas. Again, because we have experience and knowledge of these areas, we have selected an appropriate tool and have developed robust processes.

Automation is used in all cases to ensure consistency. In some cases, modern device management practices and solutions, such as Windows Autopilot, will also be used as part of a wider automation process to link users and devices.