How to Migrate 2006(not R2) projects to 2013

Hi,

I am new to 2013 biztalk and migration. Could you please tell me how to migrate projects to 2006(not 2006R2) to 2013?

I have read some sites says that, intermediate step need to follow like 2006 to 2010 and 2010 to 2013.

Can any one elaborate and help to do the activity?

February 18th, 2015 2:50pm

As far as I recall you need 2009 (Visual Studio 2008) as the intermediate step, when dealing with 2006 (not R2) (R2 can be migrated directly).

Depending on the number of projects/solutions and artifacts, it is sometimes easier to create new projects in Visual Studio 2012 (2013 if using BizTalk Server 2013 R2) and the add existing items for the Schemas, Maps, Orchestrations and Pipelines).

Morten la Cour

Free Windows Admin Tool Kit Click here and download it now
February 18th, 2015 2:55pm

Hi Sasi,

For BizTalk 2006 to 2013, you need to migrate from 2006 to 2009 and then 2009 to 2013.

Step1 : Steps for migrate from 2006 to 2009:

Goto following document download page:

BizTalk Server 2009 Installation and Upgrade Guides

And download Upgrading to BizTalk Server 2009 from BizTalk Server 2006.docx in the list for details steps involved in this intermediatory migration.

Step 2: Steps for migrate from 2009 to 2013:

Goto following document download page

BizTalk Server 2013 (and 2013 R2) Installation document

And download Upgrading to BizTalk Server 2013 from BizTalk Server 2010-2009.docx in the list for details steps involved in the final leg of migration.

Regards,

M.R.Ashwin Prabhu

February 18th, 2015 4:39pm

It has to be two step process.

1>BT 2006  to BT 2009

or

BT 2006 to BT 2010

2>BT 2009/2010 to BT 2013

The code migration happened automatically when you open the VS 2005 solution in higher equivalent  version of VS. The deployment is next thing. Also the port bindings / HIS configuration has to be redone. BT 2006 had a adapter for SOA which is being used under WCF in higher version. Those kind of communication protocals has to be considered if you are planning to migrate.

Also consider a fresh approach toward routing/exception handing: BRE frame work/ESB itinerary provides way to have a loosely coupled architecture. You may want to evaluate those as well while migrating.

Free Windows Admin Tool Kit Click here and download it now
February 18th, 2015 6:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics