Unlike schemas that you will be able to directly take your BizTalk Server schemas and use them in you Azure BizTalk Services solution, BizTalk Maps needs to be migrated because despite the Transform Designer (mapping tool used for Azure BizTalk Services)
and the BizTalk Mapper Designer looks mostly the same in terms of layout and user experience, they are quite different and the underlying map format is different. Basically when we are using BizTalk Mapper Designer the transformation are created using XSLT,
however with Transform Designer the transformation are created using Extensible Application Markup Language (XAML).
Because of all this reasons you cannot directly use a BizTalk map in Azure BizTalk Services.
The BizTalk Map Migration Tool is available in the tools zip file of the
Microsoft Azure BizTalk Services SDK (it used to be on Codeplex at
BTM Migration Tool but this is now a dead link). This is a command line tool, provided by Microsoft that takes the following inputs
And that will try to produces the new mapper (.trfm) file as an output. But before you use this tool you need to know that:
I’m saying “that will try” because there are many limitations present like:
At the end this tool will generate a conversion process report (Report.txt) listing out the failed conversions.
So let’s try change this to get only the female sex present in the input message. It seems an extremely easy change to make… we just need to go to the Logical Operation present in each MapEach Loop Operation and change the condition:
So as a final note, even if the migrator tool did a decent job, you should always try to identify some bottlenecks, problems or overlaps and simplify it.
Migrating maps from BizTalk Server solutions to Azure BizTalk Services could be one of the more complex artifacts to migrate (depending on map complexity)… or not!
The good news is that, you don’t necessary have to remake or migrate our BizTalk map to BizTalk Service map. As I mention earlier BizTalk Service maps support custom XSLT code, you can use a custom external XSLT file, similar to the “Custom XSLT Path” map grid
properties in BizTalk Server to override BizTalk Service map and use custom XSLT to make the entire map transformation.
And because we are migrating a BizTalk Server map we already have the XSLT, so for me there is no point spending a few and in some case many hours trying to remake the same transformation in a different editor.