Backoffice overhaul
With Forest, move the processes your team runs off the legacy backoffice one at a time. The data stays where it is; only the team's workspace changes.
Forest is where your team and your AI agents migrate from a legacy backoffice process by process. Forest's templates and the team's expertise scaffold each one; your people move over when each process is ready.
Generated on your existing data
Forest reads from your databases, SaaS apps, and APIs as datasources. The workspace generates on top of what you already store. No data migration, no schema lift.
Migrate process by process
Start with the highest-pain process on Forest. Move the team to it. Retire that part of the legacy tool. Move to the next. Each cutover is contained.
Permissions and approvals from day one
Roles, approval chains, and escalation rules configure per process. Your team and your AI agents follow the governance you defined, no role-by-role recreation in code.
Agentic coverage the legacy never had
Your AI agents pick up routine cases as each process goes live. Human reviewers stay on the calls that need judgement. Coverage expands as the migration progresses.
Audit and history stay intact
Forest records every action on the new process at the record level. Legacy history stays accessible through the datasource connection; recent actions land in Forest's audit trail.
Retire the legacy tool, not the team
As each process lands on Forest, the corresponding part of the legacy backoffice decommissions. Engineering frees up; the team keeps working without retraining from scratch.

Built for a successful migration
Expertise and method from the Forest team
The Forest team has run this migration with dozens of fintech ops teams. They bring a method, templates, and the experience to call the right cutover sequence for your stack.
Governance, by design
Roles, permissions, approvals, and escalation rules apply to your team and your AI agents from the first process. One audit trail covers every action.
Your stack, connected as configured
Postgres, MongoDB, Salesforce, HubSpot, Stripe, and your other systems fully connected as datasources and MCP connectors, ready to power the processes you migrate.
Plug into your stack
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
Do I need to migrate data to use Forest?
No. Forest generates the workspace on top of your existing data. It reads from your databases, SaaS apps, and APIs as datasources. Your data stays where it is.
How does the Forest team support the migration?
The Forest team brings a migration method (process discovery, template fit, cutover plan), templates for the common fintech processes, and the experience to call the right sequence for your stack. Most teams ship the first process within weeks.
Can my AI agents work the new processes from day one?
Yes. AI agents fit in two ways. They can connect to Forest's MCP server to read operational data and trigger actions in your workflows. Or Forest workflows can call AI agents through MCP tasks for routine drafting and triage. Either way, permissions and audit apply.
How is Forest different from Retool or an in-house backoffice?
Forest is purpose-built for regulated operational work. Permissions, approvals, audit, multi-tenant support, and AI agent governance are part of the platform, not custom engineering. The workspace generates on top of your data.
What happens to the legacy backoffice during the migration?
The legacy backoffice stays in place until each process moves off it. Forest reads from the same datasources, so both can coexist for a time. When a process is fully on Forest, the corresponding part of the legacy tool decommissions.
How do you ensure customer data never leaves our environment?
The Forest backend runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record.

