Migration
Our migration tool reads your SAP Data Services XML export and rebuilds your dataflows as Integrate.io pipelines, mapping load modes and translating common functions automatically. Our Solution Engineers validate the results and finish the move with you.
Trusted by 1,100+ data and ops teams saving millions of IT tickets with Integrate.io
SAP Data Services (BODS, formerly BusinessObjects Data Integrator) is SAP's long-standing ETL engine, often run alongside SAP BusinessObjects. Mainstream maintenance for Data Services 4.3 ends on December 31, 2026, and running it means SAP job servers, repository databases, and specialist skills. Integrate.io replaces it with a fully managed platform, and our migration tool converts your dataflows so the move starts from your existing logic.
What's changing
Mainstream maintenance for SAP Data Services 4.3 ends on December 31, 2026. After that date, support moves to customer-specific maintenance terms rather than standard fixes and updates. If you are planning around that deadline, our migration tool can convert your Data Services export to Integrate.io pipelines ahead of it.
The migration tool does the mechanical work, our Solution Engineers do the rest.
We inventory your SAP Data Services setup from an export or its configuration, so nothing is missed before the move.
Every SAP Data Services component and connection is matched to its Integrate.io equivalent.
The migration tool rebuilds your jobs and translates the logic automatically. Anything it cannot translate with confidence is flagged for a Solution Engineer.
We run both platforms in parallel and compare outputs before you commit.
Your current setup keeps running until the new pipelines are proven, then you switch over with a Solution Engineer alongside you.
Data Services 4.3 leaves mainstream maintenance at the end of 2026, so staying put means planning an upgrade path or a move either way.
Building and debugging dataflows, jobs, and lookup_ext logic in Designer takes BODS expertise that is increasingly hard to hire.
Data Services runs on job servers and repository databases that you patch, upgrade, and keep running.
The tool is designed to flag anything it cannot translate with confidence rather than guess, so a Solution Engineer gets a clear worklist. How much converts automatically depends on your export and how your jobs are built, and a free dry run shows you before you commit.
| Integrate.io | SAP Data Services | |
|---|---|---|
Pricing model | Flat $1,999/month, unlimited data, pipelines, and connectors. | SAP license and maintenance fees, plus the infrastructure to run it. |
Migration help | Automated converter plus a white-glove Solution Engineer team. We do it for you. | Manual rebuild. |
Ease of use | Visual pipeline builder, with SQL and Python when you need them. | Visual Designer, but SAP-specialist skills required. |
Deployment | Fully managed cloud, nothing to run or maintain. | Self-managed job servers and repository databases. |
The converter processes your whole export in one pass, and most Data Services migrations cut over within two to four weeks.
Free dry run
Share a sample of your SAP Data Services setup and we will run it through the migration tool and send back a migration report: what converts automatically, what a Solution Engineer finishes, and a scoped plan. No commitment.
Talk to a Solution Engineer. We will run the converter against your SAP Data Services setup and map a clean path onto Integrate.io.
FAQ
Clear answers to the questions teams ask when evaluating Integrate.io.
Still have questions?
Talk to an expert →Mainstream maintenance for SAP Data Services 4.3 ends on December 31, 2026. After that, support moves to customer-specific maintenance terms rather than standard fixes and updates.
Yes. The migration tool reads your Data Services XML export, converts dataflows that follow the common SQL transform, Query, and database target pattern into runnable pipelines, maps load modes, and translates common functions. Complex functions such as lookup_ext are flagged in a report for a Solution Engineer to finish.
No. The migration tool works from a Data Services XML export and makes no network calls, so nothing connects to your SAP environment during conversion.
