Application Migration

Since applications are the tools used by the end-user to run the company business, every migration involving them could have a significant or very high impact on the business. Our goal is to support every migration with clear and defined objectives and with the minimum amount of effort.

An Application migration is mostly done together with the migration from one OS to another, but is not always the case.

In general, Raynet supports the following migration strategies:

a) Migration of client applications with or without updating the application version
b) Migrating legacy applications, which are known to be incompatible or assumed to become incompatible from being locally installed to virtual environments.

An example:

Customer uses MS Access 97 macro applications and will migrate to Access 2012. A parallel installation and use of different Access versions on a single computer shall be avoided. The customer IT may not have detailed information about individual Access 97 applications, its usage, and dependencies. On the other hand, the user organization has no chance to migrate them as long as they don’t have the new Access version or additional computers. Therefore, Access 97 will be deployed on to a virtual environment (MS App-V, Citrix XenApp or others) – or vica versa. The key advantage of this strategy is that the organization and users of Access 97 makros gain more time for the migration of their individual apps to Access 2012. Once achieved, the virtualized version can be removed.

Raynet provides full migration support from planning all the way through the preparations and software packaging. Once the bulk migration is done, typically the customer takes over the packaging or hires the Virtual Package Factory of Raynet to provide future packages according to the client design of the customer.

Depending on the requirements and risk assessment, a migration can be a single package order or a larger migration project. Every application migration project is guided by one of Raynet’s highly qualified, experienced and Prince2 certified practitioners. The complete project will be managed according to the Prince2 project management principles and in close cooperation with the customer.

Our migration projects encompass the following steps that are needed for a successful execution:

  • Project preparation (roles, responsibilities, resources)
  • Communication plan
  • Project Planning (timeline, reporting)
  • Design or adoption of policies and guidelines for:
    • Packaging Framework
    • Software Deployment Framework
    • Packaging Tools
    • Application Packaging Policies and Guidelines
    • Quality requirements and acceptance criteria
  • Setup of the customer specific Virtual Packaging Factory (physical, virtual)
    • Definition and setup of computer images as reference
    • Integration of policies or linking to corporate environment (VPN network)
  • Setup of Package Order process, including
    • Provision of requirements and sources
    • Evaluation
    • Application compatibility check (OS- and Browser compatibility checks)
    • Package documentation
    • User acceptance
    • Deployment / handover

The migration of a single application or creating one installation package just needs the package order process. Raynet’s packaging process is supported by workflows and a great suite of products and interfaces engineered by one of the world’s best packaging companies - Raynet. 

Windows Migration Deployment Migration

Windows-Migration

Deployment-Migration

SAM System Migration Application Migration

SAM System Migration

Application-Migration