Every table. Every row. Every field.
Approved before anything moves.

Thirty years of SAP landscapes prove the extraction problem never actually gets solved — it gets re-solved, per table, per system, per client, from scratch, every time.

DataXover runs as native ABAP inside your SAP system. It reaches any table, computes the exact dataset before extraction, and moves nothing without two-stage approval, field-level encryption, and a compliance gate. No RFC saturation. No outside-in log scraping. No custom development per engagement.

It's your data. Use it how you need to, not how you are told to.

30 million records. Three tables. 15 minutes. Decade-old ECC.

That's not a benchmark — that's Tuesday.

The tools the market has relied on for twenty years — outside-in connectors built on SAP's ODP RFC API — were quietly never permitted for third-party use. In February 2024, SAP Note 3255746 made that restriction explicit. The recommended alternative is approximately 10x slower at production scale. The incumbents are scrambling. Multiple vendors have deprecated their SAP CDC connectors in response.

DataXover never used that door. It doesn't reach into SAP from outside. It lives inside SAP, reads SAP's own change documents, and pushes data out through the standard ABAP framework. Note 3255746 doesn't apply. The competitive landscape cleared while the patents were already in place.

SAP ECC 6.0 EhP7+ S/4HANA all releases No HANA required One transport Outbound only

The Problem

You already know what doesn't work.

Every approach requires significant custom development per engagement. Different tables. Different systems. Different client requirements. The same problems get solved from scratch every time.

The tools exist. The problem doesn't go away.

OData / BTP

Built for transactions, not extraction. Page-by-page retrieval with rate limits and gateway overhead. At serious volume it doesn't fail gracefully — it was never designed to get there.

RFC-Based Extraction

Saturates dialog work processes. Background jobs consuming work processes at scale is a Basis conversation nobody wants to have. Everyone who has attempted bulk extraction via RFC at enterprise volume has this story.

Fivetran / HVR / Database CDC

Sit outside the SAP application layer. They read database transaction logs. They can tell you a row changed. They cannot tell you what business event caused it, who initiated it, or what it means in SAP context. SAP's business logic — and its authoritative change record — lives in ABAP. Not in database logs.

BODS / Informatica

Batch ETL. Custom development per project. No native change tracking. Usually retired when the implementation ends.

The Solution

Native ABAP. One transport. Data flows.

DataXover runs inside your SAP system — not middleware calling from outside. Install through your standard change management process. Configure profiles. Activate. Background jobs only. Dialog work processes untouched.

One platform. Bulk and delta. From the same transport.

Explore the technology →

The Platform

What DataXover does.

Large Table Seeding

BSEG. Billions of rows. Tables that every other tool fails on. DataXover seeds them in chunks across maintenance windows — pause, resume, no data lost. When seeding completes, CDC takes over automatically.

Explore Seeding →

Change Data Capture

SAP's own change documents — not database logs. The authoritative record of what changed, who changed it, and when. Business events, not storage events.

Explore CDC →

OneScope

Only the fields you need. Only the records that qualify. Only the related data that belongs. Computed inside SAP before anything moves.

Explore OneScope →

Data Protection

Six protection modes per field — from passthrough to dual-output encryption that enables B2B joins without exposing raw data. Enforced at the source, before data leaves SAP.

Explore Data Protection →

B2B Platform

A marketplace where ISVs publish SAP data products and customers activate from inside their own SAP system. A market that doesn't exist yet. Whoever builds it, owns it.

Explore B2B Platform →

Enterprise Governance

Outbound only. Landscape refresh protection. Full audit trail. Compliance-gated data movement for domestic, international, and B2B flows. Built for the data SAP customers actually run.

See the FAQ →

Market Validation

This is a proven market. Companies have built substantial businesses in it.

Established companies serving thousands of SAP customers with outside-in extraction architectures have validated the demand, the budgets, and the enterprise willingness to pay for SAP data movement.

Theobald Software

Stuttgart · Founded 2004 · PE-backed

4,000 enterprise SAP customers. Twenty years building extraction tooling. AWS Marketplace presence.

SNP Group

Heidelberg · Founded 1994 · Publicly traded

3,000 enterprise customers. 1,600 employees across 23 countries. €297M revenue in FY2025, growing 19% year over year.

Both companies reach into SAP from outside using architectures affected by SAP Note 3255746. DataXover serves the same market from inside SAP, using native ABAP with patent-protected methods that make engineering competitive products at this layer a significant challenge. The market doesn't need to be created. It needs a better architecture.

We're being selective about who gets early access.

DataXover is pre-launch. We're not taking all comers. We're looking for SAP shops with real extraction problems and the technical maturity to know what they're looking at.

If that's you — tell us about your landscape.