Migration from Biztalk server 2006 to 2013

Question

Hi,

There is a requirement for migrating some application present in Biztalk 2006 to 2013. Can you please let me know if there are any tools that can help me in this migration activity.

Or What are the steps that can be followed and any specific things that needs to be taken in account before starting off with the activity.

Answer 1

If you are talking about BizTalk Server 2006 (And NOT R2), then you need an intermediate step when converting your source code in Visual Studio.

BizTalk Server 2006:

Open your projects in Visual Studio 2008 first, and migrate them. Then open them in Visual Studio 2012 and migrate.

BizTalk Server 2006 R2:

Open your projects in Visual studio 2012 and migrate.

If you are using parties you will need the Party Migration Tool (this tool has several issues, so if you only have a few parties, I suggest setting them up in the new Party/Agreement setup manually).

If you are using custom .NET code, this should also be migrated using Visual Studio (note: If you have used the Party API, you may experience that some classes/methods has changed).

Morten la Cour

 

Answer 2

Also check out BizTalk Application Migration Guide, this can provide lot of useful information . 

---

Greetings,HTH
Naushad Alam

When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer
alamnaushad.wordpress.com

Answer 3

Hi,

I was just wondering whether it's the same migration path with BizTalk Server 2009 to 2013? I can just use Visual Studio 2012 conversion wizard to migrate the code?

Thanks in advance,

Alla

Answer 4

The Development and Deployment project types in 2006 were changed to Release and Debug types since 2009 (?). You find out many blogs and threads here about it.

One trick is: if your solution doesn't have a C# project (all BizTalk projects only), create one dummy C# project!

This helps you! Delete it after conversion.

 

Answer 5

Thanks Leonid,

I was trying to find at least one thread telling me how to migrate from 2009 to 2013 but failed. Most of them telling how to migrate from 2006 to 2010. So I assumed I should follow the same path as to open projects in VS2012 and use conversation wizard to do it? Is this right? Do I still need to add dummy C# project to the solutions having BizTalk projects only in BT2009 (I am a bit confused why I need to do it)? Also if you can point me to some good threads/blogs re migrating from BizTalk 2009 to 2013 it would be priceless!

Thanks heaps,

Alla

Answer 6

Migration to 2010 is the same as to 2013. There is no breaking changes. All 2010 projects can be opened without additional work in 2013, no additional C# project. 

This project automatically creates Release and Debug solution modes, so you don't need to create them manually.

 If you "Ask a Question" on this forum (here is a button on the screen top) and enter "Migration from 2006 to 2010" as a Subject and move cursor to the next field, you get many links to the similar threads. I used this method when started a big upgrade a year ago. :)

• 

  Migration from 2006 to 2010
• 

  BIzTalk migration from 2006 to 2010
• 

  Migration from BTS 2006 to BTS 2010
• 

  Migrating from biztalk 2006 R2 to 2009 or 2010
• 

  Migrating nSoftware Adapters from BizTalk 2006 R2 (V2) to BizTalk 2010 (V3)

 

---

Leonid Ganeline [BizTalk MVP] BizTalk Development Architecture