BizTalk Migrations

Our team has implemented hundreds BizTalk migrations. We provide strategies for business continuity during migrations. Aidant’s experts can recommend software consolidation for budget efficiency and provide architecture guidance.

 

Migration Services

Our experienced teams can support change management and help mitigate risks associated with migrations and upgrades. The migration implementations utilize a proven methodology that allow for migration of legacy software as well as side-by-side installations with current production environment. We tune server performance from the first day of production environment use.

Migrations And Upgrades

  •  Migrate out-of-support BizTalk versions latest version

  • Migrate current expensive Middleware to BizTalk

  • Upgrade Visual Studio, SQL Server and Windows Server

  • Upgrade .NET framework

Implement or Migrate to Microsoft BizTalk Server 2020

The Aidant team recently got hands-on experience with BizTalk 2020. They completed a POC for an existing customer who will be now migrating from BizTalk 2016 R2. The target was an aggressive five* days! 

A lot has changed in BizTalk 2020. However, Microsoft is keeping the promise it made in 2015 to keep BizTalk on-premise alive while adding features to bring it closer to Azure (a.k.a. Cloud). 

FAQ! Here are some frequently asked questions for those considering migrating to, or starting brand new, with BizTalk 2020.

*Five days does not include installation, configuration, and end to end testing. Includes unit testing.

Q1: What are the software requirements/support for BizTalk 2020?

A. Windows 10, Windows Server 2016 or 2019 

B. SQL Server v.2016 SP2, v.2017, v.2019

C. Visual Studio 2019 (.NET Framework 4.7)

D. Office Excel 2016 or 2019

E. SharePoint (optional) 2016, 2019 or SharePoint Services Online

F. IBM MQ Series version 8 and 9 supported (if used)

Q2: Will my existing BizTalk integrations work, or is there a lot to retrofit?

Answer: YES

However, there are some variations depending on your current setup. Based on Aidant’s extensive
experience with BizTalk migrations, we can grade each of the following scenarios on a scale of 1 to 10,   1   being the easiest and shortest migration, and  10  being the longest and hardest.

2 - Currently running BizTalk 2013 or higher

In-place migration possible, but not recommended.

4 - Currently running BizTalk 2010

.NET framework and deprecated functions in C# or VB .NET to be re-written. Adapters need to be switched. Testing with external partners is key.

6 - Currently running BizTalk 2006, 2006R2, 2009

In-place upgrade not recommended and not fully supported anymore. However, the migration is less painful compared to “Grade 9” below.

9 - Currently running BizTalk 2002 or 2004

We need to evaluate inventory of integrations running and create a migration checklist. Our team has developed tools to access and auto-migrate maps. This type of migration is accelerated using the Aidant DI.Platform.

Q3: Will I be able to leverage old and existing code?

Answer: YES

We take what you have, migrate it over, and improve the implementation in the process before testing.

Q4: Will there be special training required for existing BizTalk staff?

Answer: NO

Special training is not required. The look and feel remains similar, so teams usually adapt easily and quickly. The Aidant team specializes in cross-training and highlighting what needs to be focused on going forward.

Q5: Will we be Cloud-ready after implementing BizTalk 2020?

There are exceptional new features in this version that will bring you closer to Cloud or Azure implementations. However, Microsoft has done a great job of keeping the choice with the customer. You’ll be able to decide how much you want to be on Cloud versus on-premise. We recommend a hybrid approach based on individual needs.