TimeXtender

Your TimeXtender instance is worth more than its tooling.

It holds a layered structure, documented transformations and field-level lineage: the work most projects never formalised. We take it over, we keep it running, or we transpose that work into Microsoft Fabric.

Domain at a time, in parallel: 1
Expert consultants: 11
Of scoping to decide: 2 h
Projects delivered since 2019: 100+

3
Paths: take over, broaden, transpose: 1
Domain at a time, alongside the existing estate: 100 %
Of the design work carried across: 2 h
Free scoping workshop to decide

Three situations

Where you are, and what we do about it

What TimeXtender brings

An abstraction layer that keeps you free

TimeXtender’s most durable quality is its abstraction layer: the preparation logic is described independently of the engine that executes it. That is what lets you change infrastructure without rewriting the rules, and it is a genuine asset for a company that wants to keep control of its hosting.

Automatic generation of the layers saves considerable time on the repetitive part of a project: structures, historisation, dependencies. Teams concentrate on the business rules, which are the only genuinely specific part.

Field-level lineage is the third asset, and the most underrated. Knowing where a figure comes from and which transformations it passed through is what allows a project to be picked up years later without its author, or migrated calmly.

That is why these instances transpose well. The design was done, it is written down, it was validated. Moving to Fabric means changing tooling, not starting again.

The sequence

How a transposition runs

Inventory
Connected sources, transformations in place, exposed datasets, dependent reports.
First domain
Usually sales: the scope where a discrepancy shows up immediately.
Comparison
Your teams check both platforms against their own figures.
Progressive move
Domain by domain, at the pace the facts justify.

Frequently asked

What people ask us about TimeXtender

Can you take over an existing TimeXtender project?

Yes. We start with an inventory of the instance: connected sources, transformations in place, exposed datasets and the reports that depend on them. That map is useful whether you stay on the tool or not, it belongs to you, and it is often the first complete documentation the team has had since it went in.

TimeXtender or Microsoft Fabric?

Both automate data preparation so it is not repeated in every report. TimeXtender does it through an abstraction layer that stays independent of the storage engine, which is a real asset when the infrastructure has to remain open. Fabric integrates storage, preparation and Power BI in one environment with a single bill. The choice turns on your ecosystem and your hosting constraints, not on the quality of the tools.

What do we keep when migrating to Fabric?

The modelling, which is the essential part. A TimeXtender instance holds a layered structure, documented transformation rules and field-level lineage. That work transposes directly into a medallion architecture: the layers carry different names and the same intent. The migration is about tooling, not design.

Can the two run side by side?

Yes, and that is how we most often proceed. We load a first domain into Fabric while TimeXtender keeps serving the rest, then compare on real data. The pace that follows is decided on what your teams observe, not on a calendar fixed in advance.

If you transpose

One domain at a time

Each domain moves across one after the other while the existing platform keeps serving. The overlap lets your teams compare the two platforms on their own figures before deciding what comes next.

One domain at a time, never everything at once

The existing platform keeps serving while each domain moves across, which lets your teams compare on their own figures.

The overlap is the heart of the method: it is where your teams put the two platforms side by side on real data. The pace of what follows is decided on what they observe, not on a calendar fixed in advance.

Let us open your instance and see what is inside.

Eleven expert consultantsSaint-Priest, near Lyon, France

Two hours with a consultant, free of charge. We inventory your sources, your transformations and the reports depending on them, and we tell you what we would do: take it over, broaden it, or transpose it into Fabric, domain by domain.

Request a scoping workshop

Scoping workshop · 2 hours · free · near Lyon or remote