CBS migration
With Forest, customer-facing workflows keep running through a CBS cutover. Reads and writes go to both the old and new core; the audit lives in the workspace.
Forest is where your team and your AI agents keep handling customer work while engineering migrates the core. Reads and writes go to both cores; the audit trail stays in the workspace.
Read from both cores
Customer records, accounts, balances, and transactions stream from the old and the new core into the same case view. Your team works from one screen, not two.
Write to both cores
Account updates, status changes, limit edits, and servicing actions route to the right core based on cutover rules. Dual-write with checks until each customer is fully on the new core.
Cutover rules per cohort
Migrate customers by segment, product, or jurisdiction. Configure which cohort runs on which core, when. Forest applies the routing per case.
Reconciliation as a workflow
Continuous comparison between the old and the new core surfaces breaks as cases routed to a reviewer with the source data attached. Migration discrepancies do not pile up unseen.
Agentic continuity
Your AI agents keep clearing routine servicing, refunds, and case handling through the migration window, under the rules you set per cohort. Human reviewers handle the migration-specific edge cases.
Audit stays in Forest
Every customer action, every dual-write, every reconciliation decision is recorded at the record level. The audit trail belongs to Forest, independent of either core.

Built for a core swap
Read and write on both cores
Reads consolidate from the old and the new core. Writes route to the right core per cohort. Your team works from one screen, regardless of which core holds the record.
Reconciliation as you go
Forest runs continuous comparison between the old and the new core. Breaks land as cases routed to a reviewer with the source data attached. Discrepancies do not pile up.
Audit independent of either core
The customer action history lives in Forest, not in the core. The regulator-ready bundle stays consistent before, during, and after the migration.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
How does Forest connect to both my old and new core?
Forest reaches both cores through datasources (for customer, account, and transaction data) and through MCP connectors (for write actions). Dual-read is the default during cutover; dual-write applies per cutover rule you configure.
Can I migrate customers in cohorts?
Yes. Forest supports cohort-based migration: configure who runs on which core, when. Each cohort is a workflow rule; Forest routes reads and writes accordingly until every customer is on the new core.
How is reconciliation handled during the migration?
Forest provides a reconciliation workflow template you customize to your cores. Breaks surface as cases with the source data attached; your team reviews and your AI agents can clear the routine ones under the rules you set.
What happens to the audit trail through cutover?
The audit trail lives in Forest, independent of either core. Every customer action, dual-write, and reconciliation decision is recorded at the record level. The regulator-ready bundle stays consistent through the migration.
Does Forest replace my core?
No. Forest sits above the core as the workspace where your team and your AI agents operate. The core handles ledger, balances, and payments rails. Forest handles the workflows, the cases, the audit, and the operational surface.
How long does a CBS migration on Forest take?
It depends on scope. The Forest team brings template workflows for the common cores (Mambu, Thought Machine, 10x Banking, Tuum) and helps configure the dual-read, dual-write, and reconciliation patterns. Cohort-based migration keeps each phase contained.

