Schemas
Lobster can build structures directly from XSD schemas, so that the schemas of your BizTalk solution can be used as a starting point.
Platform change
BizTalk migration to Lobster, while operations keep running
Microsoft BizTalk Server 2020 will be the last version of BizTalk. Microsoft’s mainstream support ends in April 2028 and extended support in April 2030, and for BizTalk Server 2016, extended support already ends in January 2027. We move your integration flows from BizTalk to Lobster, partner by partner, while BizTalk keeps running.
This page covers Microsoft’s timetable, what a BizTalk solution consists of, and how to migrate from BizTalk to Lobster with us.
Timetable
BizTalk’s end of life: when does support end?
Microsoft has announced that BizTalk Server 2020 will be the last version. There will be no new BizTalk to upgrade to, and support for the existing versions is time-limited. The dates below come from Microsoft’s lifecycle pages for each version, such as the one for BizTalk Server 2020:
| Version | Mainstream support until | Extended support until |
|---|---|---|
| BizTalk Server 2020 | April 2028 | April 2030 |
| BizTalk Server 2016 | January 2022 | January 2027 |
| BizTalk Server 2013 R2 | July 2018 | July 2023 |
For BizTalk Server 2020, mainstream support includes both security updates and other fixes. During the extended period you receive security updates and support, while other fixes have to be purchased separately. When extended support ends, there are neither updates nor support.
Microsoft has already extended mainstream support for BizTalk Server 2020 once, from January 2024 to April 2028. But no new versions are coming, and support has an end date.
Consequence
What does your BizTalk Server version mean for you?
How urgent it is for you depends on which version you run:
- BizTalk Server 2016 or older. Extended support for 2016 ends in January 2027, and 2013 R2 has been without support since July 2023.
- BizTalk Server 2020. You have mainstream support until April 2028 and extended support until April 2030. Microsoft expects to end sales of BizTalk Server 2020 on 31 March 2027.
- Paid transition support. Within the extended period, between April 2028 and April 2030, Microsoft plans to offer paid transition support for fixes beyond security updates. It is intended as cover while you migrate, will not include everything, and the terms and prices are not yet final.
If you use Business Activity Monitoring (BAM), the ESB Toolkit, older adapters or BizTalk-specific development tools, Microsoft recommends planning early, because those are expected to fall outside the paid transition support.
Microsoft’s own recommendation is Azure Logic Apps. We move BizTalk solutions to Lobster Data Platform, and the rest of this page is about how that works.
Assessment
Which BizTalk capabilities need to move?
A migration starts by mapping what the BizTalk solution consists of: schemas, maps, orchestrations, pipelines, bindings, business rules, custom code, endpoints, adapters and certificates. This is how each is handled in Lobster:
Maps
Lobster can run XSLT transformations. Whether an existing map can be reused is decided map by map during the assessment.
Orchestrations, pipelines and rules
The logic is mapped and rebuilt in Lobster, so that it can be seen and changed instead of living in code.
Bindings, endpoints and adapters
The connections to partners and systems, for example AS2, OFTP and SFTP, are moved to Lobster. Lobster’s AS2 is Drummond certified.
EDI formats
Lobster has functions for EDIFACT and EANCOM and can check X12 files.
Custom code and certificates
Custom code, assemblies and certificates are reviewed one by one in the assessment, so that they are not forgotten when BizTalk is shut down.
In our experience, the EDI flows with customers and suppliers often carry the most weight, because each partner has its own formats and special rules. Read more about how we build EDI integration with trading partners.
Process
How a migration from BizTalk works
- Assessment. We review the flows, partners, formats, protocols and the special rules that have built up over the years.
- Rebuilding and testing. The flows are rebuilt in Lobster and tested against real production files, not just against the documentation. Lobster can save test cases with real files and show whether the result changes.
- Partner by partner. Partners are moved over one at a time while BizTalk keeps running, so you do not have to switch everything overnight.
- Shutdown. When the last connection has moved, BizTalk is shut down, and you are left with one integration platform and all your monitoring in one place.
Lobster’s AI assistant Pathfinder can suggest mappings, including function chains, from a test file. This requires Lobster’s AI licence, and the suggestions are tested like everything else before they go into operation.
After the migration, you can run the integrations in Lobster yourself or have us do it as managed integration services.
Do you run BizTalk today? Then we start by assessing your solution.
Get your BizTalk solution assessedOther platforms
Are you coming from a VAN provider or another platform?
The method is the same when the starting point is a VAN provider that charges per message, a managed EDI service or a custom-coded solution that only a few people understand. We map, rebuild, test and move the partners one at a time.
If you are coming from a managed service, the switch is rarely about something being broken. It is about who owns the integration platform. With Lobster, the mappings and partner connections live in your own environment, and the same layer also handles APIs and file transfers.
Why Lobster?
Flows that others can read too
Flows modelled visually in Lobster can be read and taken over by others, instead of living in code that only the original developer understands.
One of our senior consultants, Søren Bohn, has led migrations from BizTalk, in one case while the customer was also replacing its core system. Meet the team on About us.
FAQ
Frequently asked questions about BizTalk migration
Is BizTalk Server 2020 reaching end of support?
Yes, support has a fixed end date. Microsoft BizTalk Server 2020 is the final release of BizTalk. Mainstream support ends in April 2028 and extended support in April 2030. After that, there will be no updates or support.
What replaces BizTalk: Azure Logic Apps or Lobster?
Microsoft’s own recommendation is Azure Logic Apps. We move BizTalk solutions to Lobster Data Platform, where EDI, APIs and file transfers sit in the same integration layer.
Can BizTalk continue running while we migrate?
Yes. Partners are moved over one at a time while BizTalk keeps running, and BizTalk is only shut down when the last connection has moved.
Can we reuse our schemas and maps?
It depends on the individual solution. Lobster can build structures from XSD schemas and run XSLT transformations, but whether an existing map can be reused is decided map by map during the assessment.
We run BizTalk Server 2016 or earlier versions. What does that mean?
Extended support for BizTalk Server 2016 ends in January 2027, and mainstream support ended in January 2022. BizTalk Server 2013 R2 has been without support since July 2023. If you run 2016 or earlier, the assessment is the first step, wherever you end up.
What does a migration from BizTalk cost?
It depends on how many flows, partners and special rules the solution has. You receive a specific quote after the assessment.
Shall we map your BizTalk solution?
Tell us what runs on BizTalk today and which version you have. We will then come back with a proposal for how the move can be carried out.