Tools · Agentic Migration · Graft · First product
Available via AWS Marketplace · listing in progress

How does a migration run in weeks rather than quarters?

Graft is TBSCG's agentic migration toolchain, our first product and the toolchain the Banyan Method runs on. Five modules take the repetitive lift out of a replatform, from estate extraction to cutover, while senior engineers keep the judgement. Output is reviewed, not typed.

What it is

The product behind the method.

Migrations stall on the mechanical work: inventorying thousands of pages, rebuilding components, moving content, checking nothing broke. Graft is that work, turned into software. It was built inside real replatforms, hardened on live estates, and is the reason work that used to run across quarters now runs in weeks.

01 Born in the practice

Graft was not designed on a whiteboard. Each module exists because a live replatform needed it, and each one earned its keep on a client estate before it had a product name.

First product

02 Vendor-agnostic by design

Content leaves the legacy platform through a neutral intermediate format, not a point-to-point script. New sources and new targets are added without rebuilding the toolchain.

03 Senior engineers keep the judgement

Graft does the mechanical lift. What moves, when, and how stays with senior engineers who have run replatforms before. Every output is reviewed before it is load-bearing.

04 Weeks, not quarters

Extraction that used to take a team months runs in days. The repetitive lift is compressed at every stage, and the saved time goes into the work that needs human attention.

The five modules

Five modules, one spine.

Each module maps to a stage of the Banyan Method's five-stage spine, so the toolchain and the method move together. Discovery, Build, Transfer, Parallel, Sovereignty: one module carries the lift at each stage.

01

Estate auto-extract

Builds the content inventory and component map of the existing estate in days, not months. Senior engineers validate the map before anything depends on it.

Banyan stage: Discovery

02

Component generator

Produces component shells, templates and integration scaffolding to specification on the target platform. Reviewed, not handwritten.

Banyan stage: Build

03

Migration engine

Moves content out of the legacy platform through a vendor-agnostic intermediate format and into the new one, with structure and references intact.

Banyan stage: Transfer

04

Parity monitor

Compares old and new platforms in real time through the parallel window, so regressions surface before users notice them. This is what makes the parallel period trustworthy rather than hopeful.

Banyan stage: Parallel

05

Cutover orchestrator

Sequences the switch and the post-switch monitoring, on the client's signal rather than a vendor schedule. The moment of cutover stays yours.

Banyan stage: Sovereignty

The Graft pipeline Five modules in sequence, each carrying one stage of the Banyan Method. The cutover point carries the one lime mark
THE GRAFT PIPELINE MAPPED TO THE BANYAN METHOD MODULE 01MODULE 02MODULE 03MODULE 04MODULE 05 Estateauto-extract Componentgenerator Migrationengine Paritymonitor Cutoverorchestrator 0102030405 DiscoveryBuildTransferParallelSovereignty

Fig 1 · The Graft pipeline Five modules in sequence, each carrying one stage of the Banyan Method. The cutover point carries the one lime mark: the switch happens on your signal, not a vendor schedule.

Graft and the Banyan Method

Graft is the toolchain. The Banyan Method runs it.

The two are designed together and most often run together, but they are not the same thing. The method decides what good looks like: parallel running, the client controlling the switch, sovereignty at the end. The toolchain makes the method fast.

Graft is the toolchain
Five software modules that do the mechanical lift of a migration.
The Banyan Method runs it
The five-stage spine: parallel running, and the client choosing the moment of switch.
Senior engineers keep the judgement
What moves, when and how is decided by people who have run replatforms before.
Output is reviewed, not typed
The tooling produces; the engineers approve. Nothing is load-bearing unreviewed.
Where it applies

Built for the estates we actually meet.

Graft moves estates onto modern content platforms and off the legacy ones that have been holding programmes hostage. The intermediate format means the list below grows without the toolchain being rebuilt.

Magnolia
Target platform. Implementation and migration by a validated Magnolia partner.
Contentful
Target platform. Composable, headless estates built on partner accreditation.
Legacy CMS
Source estates. Ageing platforms with content worth keeping and risk worth leaving.
TeamSite era
Source estates. TeamSite and other OpenText-era platforms, extracted cleanly.
Route to market and platform partners
Available via AWS Marketplace · listing in progress AWS Advanced Consulting Partner Magnolia Contentful
Questions

Frequently asked questions.

Is Graft a product or a service?

A product, and TBSCG's first. Graft is a licensed toolchain with a roadmap and a release cadence. Most clients meet it inside a Banyan Method replatform, run by the practice that built it, but it can also be licensed for a migration programme your own team runs.

Does Graft replace the engineers?

No. The five modules do the mechanical lift: extraction, generation, transfer, comparison and sequencing. Senior engineers decide what moves, when and how, and every output is reviewed before it is load-bearing. Output is reviewed, not typed.

Which platforms can Graft move?

Graft moves estates onto Magnolia and Contentful, and moves them off legacy CMS estates including TeamSite and other OpenText-era platforms. Content travels through a vendor-agnostic intermediate format, so new sources and targets are added without rebuilding the toolchain.

How long does a migration with Graft take?

Weeks rather than quarters. Estate extraction that used to take a team months runs in days, and the repetitive lift across every stage is compressed. The one thing never shortened is the parallel window, which is sized to your risk appetite, because that is where confidence is earned.

Is Graft on AWS Marketplace?

Graft is available via AWS Marketplace, with the listing in progress. Procurement runs through the AWS relationship your estate already has once the listing is live. Until then, talk to us and we will set up the route that fits your procurement.

Where next

The toolchain in context.

Graft rarely travels alone. Here is where it most often joins the rest of the work.

Start here

Move the estate in weeks.

Tell us what your estate is running on and where it needs to go. We will show you what Graft extracts in the first days, and what the rest of the move looks like from there.