Is it mandatory to build solution on (intermediate step) BizTalk 2010 when migrating to BizTalk 2013.

Is there any microsoft offical guide to migrate BizTalk 2006 to BizTalk 2013 ?

I have guide for BizTalk 2009/BizTalk 2010 to BizTalk 2013.

How to migrate BAM and BRE. Do we need intermediate BizTalk 2010 step ?

 refer below links

http://andreikos.wordpress.com/2014/03/07/biztalk-2006-r22009-to-biztalk-2013-migration-approach/

http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

• Edited by Singh AK 23 hours 20 minutes ago

BizTalk Server 2006 R2 supported .Net 2.0/3.0 (for WCF related services were just about introduced). BizTalk Server 2013 on the other hand works with .Net 4.0/4.5.

BizTalk Server 2006 R2 worked with Visual Studio 2005 while the project templates for BizTalk Server 2010 work only with Visual Studio 2010. In the migration of the project templates you may need an intermediate setup of BizTalk 2009 Developer Tools and Visual Studio 2008 where you'd need to convert the project templates into the appropriate format before bringing them up to the level required for BizTalk 2013.

As far as BAM is concerned, the BAM Definition File (not the live workbook) .XLS will need to be moved from the Excel 2003 version to the Excel 2013 version with the plug-in installed. A BAM Export (.xml) file however would be directly usable in 2013 [ the BAM architecture has just not changed :)]. Even your BAM Data should be directly importable across the different versions of the SQL databases.

Regards.

• Marked as answer by TarunGarg AKG 22 hours 1 minutes ago

How BRE will migrate ?

BizTalk Server 2006 R2 supported .Net 2.0/3.0 (for WCF related services were just about introduced). BizTalk Server 2013 on the other hand works with .Net 4.0/4.5.

BizTalk Server 2006 R2 worked with Visual Studio 2005 while the project templates for BizTalk Server 2010 work only with Visual Studio 2010. In the migration of the project templates you may need an intermediate setup of BizTalk 2009 Developer Tools and Visual Studio 2008 where you'd need to convert the project templates into the appropriate format before bringing them up to the level required for BizTalk 2013.

As far as BAM is concerned, the BAM Definition File (not the live workbook) .XLS will need to be moved from the Excel 2003 version to the Excel 2013 version with the plug-in installed. A BAM Export (.xml) file however would be directly usable in 2013 [ the BAM architecture has just not changed :)]. Even your BAM Data should be directly importable across the different versions of the SQL databases.

Regards.

check article by andrei, where he have coverted most of artifact mirgaration. It do include BRE & BAM.

http://andreikos.wordpress.com/2014/03/07/biztalk-2006-r22009-to-biztalk-2013-migration-approach/

BRE has also not changed. You will need to export your rules and vocabularies and import them into the new environment. If you're accessing DB based facts and services then you'd need to ensure that the databases are either migrated to SQL Server 2008 R2 or 2012 because the SQL Client for 2012 will not support connection to SQL Server 2005 (only 2 prior versions which would be 2008/2008 R2)

Regards.

To answer you specific questions:

No, you can open a BizTalk Server 2006 R2 Project directly in Visual Studio 2012.

No, not for that specifically, but you can follow the 2009 guide found here: http://download.microsoft.com/download/E/9/7/E97E3B84-1C1E-4D95-A1B8-FEB0A814CFBB/Upgrading%20to%20BizTalk%20Server%202013%20from%20BizTalk%20Server%202010-2009.docx

Same as above.

No.  BAM and BRE Artifacts should migrate smoothly.

Parties are the only thing that will require some specific migration steps.

Of course, test thoroughly.

 refer below links

http://andreikos.wordpress.com/2014/03/07/biztalk-2006-r22009-to-biztalk-2013-migration-approach/

http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

Migration of BRE Policies and Vocabularies from BizTalk 2006 R2 to BiTalk 2013 via BRE Policies and Vocabularies Export/Import may work but is not supported by Microsoft. The business rules may have to be build from scratch on the BizTalk 2013 environment. "

thats the reason I am searching microsoft recommendation on this ?

The same statement gives the Microsoft recommendations as "The business rules may have to be built from scratch on the BizTalk 2013 environment."

Given that you can create your own fact retrievers which would have been .Net 2.0 code or your own vocabularies using static support which would have been again .Net 2.0 code, you'd be required to rebuild that and maybe change the version numbers in which case the import would reference the earlier unsupported versions so not work.

Given the scope of the migration you would eventually have to setup a pilot environment and then assess the methodologies for yourself given the extensibility of the BizTalk Framework such as custom components, functoids, fact retrievers, helper libraries, etc., etc.

Regards.

• Marked as answer by TarunGarg AKG 22 hours 2 minutes ago

No, that is not the case and I have no idea what he's referring to. The BRE has not changed notably since 2006 R2.  Besides, it doesn't really matter.

Once you import the Vocabulary and Policies, you're done. If you're using a lot of .Net based Facts, you may have some issues due to the .Net Framework upgrade but that wouldn't be a BizTalk or BRE specific thing.

Don't worry about it.  You won't be 'unsupported' simply because the rules originally came from 2006 R2.

 refer below links

http://andreikos.wordpress.com/2014/03/07/biztalk-2006-r22009-to-biztalk-2013-migration-approach/

http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

• Edited by Singh AK Monday, April 21, 2014 11:07 AM

 refer below links

http://andreikos.wordpress.com/2014/03/07/biztalk-2006-r22009-to-biztalk-2013-migration-approach/

http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

• Edited by Singh AK Monday, April 21, 2014 11:07 AM

 refer below links

http://andreikos.wordpress.com/2014/03/07/biztalk-2006-r22009-to-biztalk-2013-migration-approach/

http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

• Edited by Singh AK Monday, April 21, 2014 11:07 AM

 refer below links

http://andreikos.wordpress.com/2014/03/07/biztalk-2006-r22009-to-biztalk-2013-migration-approach/

http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

• Edited by Singh AK Monday, April 21, 2014 11:07 AM

BizTalk Server 2006 R2 supported .Net 2.0/3.0 (for WCF related services were just about introduced). BizTalk Server 2013 on the other hand works with .Net 4.0/4.5.

BizTalk Server 2006 R2 worked with Visual Studio 2005 while the project templates for BizTalk Server 2010 work only with Visual Studio 2010. In the migration of the project templates you may need an intermediate setup of BizTalk 2009 Developer Tools and Visual Studio 2008 where you'd need to convert the project templates into the appropriate format before bringing them up to the level required for BizTalk 2013.

As far as BAM is concerned, the BAM Definition File (not the live workbook) .XLS will need to be moved from the Excel 2003 version to the Excel 2013 version with the plug-in installed. A BAM Export (.xml) file however would be directly usable in 2013 [ the BAM architecture has just not changed :)]. Even your BAM Data should be directly importable across the different versions of the SQL databases.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

BizTalk Server 2006 R2 supported .Net 2.0/3.0 (for WCF related services were just about introduced). BizTalk Server 2013 on the other hand works with .Net 4.0/4.5.

BizTalk Server 2006 R2 worked with Visual Studio 2005 while the project templates for BizTalk Server 2010 work only with Visual Studio 2010. In the migration of the project templates you may need an intermediate setup of BizTalk 2009 Developer Tools and Visual Studio 2008 where you'd need to convert the project templates into the appropriate format before bringing them up to the level required for BizTalk 2013.

As far as BAM is concerned, the BAM Definition File (not the live workbook) .XLS will need to be moved from the Excel 2003 version to the Excel 2013 version with the plug-in installed. A BAM Export (.xml) file however would be directly usable in 2013 [ the BAM architecture has just not changed :)]. Even your BAM Data should be directly importable across the different versions of the SQL databases.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

BizTalk Server 2006 R2 supported .Net 2.0/3.0 (for WCF related services were just about introduced). BizTalk Server 2013 on the other hand works with .Net 4.0/4.5.

BizTalk Server 2006 R2 worked with Visual Studio 2005 while the project templates for BizTalk Server 2010 work only with Visual Studio 2010. In the migration of the project templates you may need an intermediate setup of BizTalk 2009 Developer Tools and Visual Studio 2008 where you'd need to convert the project templates into the appropriate format before bringing them up to the level required for BizTalk 2013.

As far as BAM is concerned, the BAM Definition File (not the live workbook) .XLS will need to be moved from the Excel 2003 version to the Excel 2013 version with the plug-in installed. A BAM Export (.xml) file however would be directly usable in 2013 [ the BAM architecture has just not changed :)]. Even your BAM Data should be directly importable across the different versions of the SQL databases.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

BizTalk Server 2006 R2 supported .Net 2.0/3.0 (for WCF related services were just about introduced). BizTalk Server 2013 on the other hand works with .Net 4.0/4.5.

BizTalk Server 2006 R2 worked with Visual Studio 2005 while the project templates for BizTalk Server 2010 work only with Visual Studio 2010. In the migration of the project templates you may need an intermediate setup of BizTalk 2009 Developer Tools and Visual Studio 2008 where you'd need to convert the project templates into the appropriate format before bringing them up to the level required for BizTalk 2013.

As far as BAM is concerned, the BAM Definition File (not the live workbook) .XLS will need to be moved from the Excel 2003 version to the Excel 2013 version with the plug-in installed. A BAM Export (.xml) file however would be directly usable in 2013 [ the BAM architecture has just not changed :)]. Even your BAM Data should be directly importable across the different versions of the SQL databases.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

BizTalk Server 2006 R2 supported .Net 2.0/3.0 (for WCF related services were just about introduced). BizTalk Server 2013 on the other hand works with .Net 4.0/4.5.

BizTalk Server 2006 R2 worked with Visual Studio 2005 while the project templates for BizTalk Server 2010 work only with Visual Studio 2010. In the migration of the project templates you may need an intermediate setup of BizTalk 2009 Developer Tools and Visual Studio 2008 where you'd need to convert the project templates into the appropriate format before bringing them up to the level required for BizTalk 2013.

As far as BAM is concerned, the BAM Definition File (not the live workbook) .XLS will need to be moved from the Excel 2003 version to the Excel 2013 version with the plug-in installed. A BAM Export (.xml) file however would be directly usable in 2013 [ the BAM architecture has just not changed :)]. Even your BAM Data should be directly importable across the different versions of the SQL databases.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

BizTalk Server 2006 R2 supported .Net 2.0/3.0 (for WCF related services were just about introduced). BizTalk Server 2013 on the other hand works with .Net 4.0/4.5.

BizTalk Server 2006 R2 worked with Visual Studio 2005 while the project templates for BizTalk Server 2010 work only with Visual Studio 2010. In the migration of the project templates you may need an intermediate setup of BizTalk 2009 Developer Tools and Visual Studio 2008 where you'd need to convert the project templates into the appropriate format before bringing them up to the level required for BizTalk 2013.

As far as BAM is concerned, the BAM Definition File (not the live workbook) .XLS will need to be moved from the Excel 2003 version to the Excel 2013 version with the plug-in installed. A BAM Export (.xml) file however would be directly usable in 2013 [ the BAM architecture has just not changed :)]. Even your BAM Data should be directly importable across the different versions of the SQL databases.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

The same statement gives the Microsoft recommendations as "The business rules may have to be built from scratch on the BizTalk 2013 environment."

Given that you can create your own fact retrievers which would have been .Net 2.0 code or your own vocabularies using static support which would have been again .Net 2.0 code, you'd be required to rebuild that and maybe change the version numbers in which case the import would reference the earlier unsupported versions so not work.

Given the scope of the migration you would eventually have to setup a pilot environment and then assess the methodologies for yourself given the extensibility of the BizTalk Framework such as custom components, functoids, fact retrievers, helper libraries, etc., etc.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

The same statement gives the Microsoft recommendations as "The business rules may have to be built from scratch on the BizTalk 2013 environment."

Given that you can create your own fact retrievers which would have been .Net 2.0 code or your own vocabularies using static support which would have been again .Net 2.0 code, you'd be required to rebuild that and maybe change the version numbers in which case the import would reference the earlier unsupported versions so not work.

Given the scope of the migration you would eventually have to setup a pilot environment and then assess the methodologies for yourself given the extensibility of the BizTalk Framework such as custom components, functoids, fact retrievers, helper libraries, etc., etc.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

The same statement gives the Microsoft recommendations as "The business rules may have to be built from scratch on the BizTalk 2013 environment."

Given that you can create your own fact retrievers which would have been .Net 2.0 code or your own vocabularies using static support which would have been again .Net 2.0 code, you'd be required to rebuild that and maybe change the version numbers in which case the import would reference the earlier unsupported versions so not work.

Given the scope of the migration you would eventually have to setup a pilot environment and then assess the methodologies for yourself given the extensibility of the BizTalk Framework such as custom components, functoids, fact retrievers, helper libraries, etc., etc.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM

The same statement gives the Microsoft recommendations as "The business rules may have to be built from scratch on the BizTalk 2013 environment."

Given that you can create your own fact retrievers which would have been .Net 2.0 code or your own vocabularies using static support which would have been again .Net 2.0 code, you'd be required to rebuild that and maybe change the version numbers in which case the import would reference the earlier unsupported versions so not work.

Given the scope of the migration you would eventually have to setup a pilot environment and then assess the methodologies for yourself given the extensibility of the BizTalk Framework such as custom components, functoids, fact retrievers, helper libraries, etc., etc.

Regards.

• Marked as answer by TarunGarg AKG Monday, April 21, 2014 12:25 PM