A mid-size firm’s guide to

Switching Document Automation Platforms

Switching Document Automation Platforms

Switching Document Automation Platforms

How mid-size firms move off first-generation automation without a big IT project or a dedicated automation team. Plan the switch, bring your lawyers with you, and see what actually changes.

How mid-size firms move off first-generation automation without a big IT project or a dedicated automation team. Plan the switch, bring your lawyers with you, and see what actually changes.

~20x

faster drafting

1,200

templates in 12 months

77%

of a legacy library retired

Lawyer holding a tablet, from the guide cover

Foreword

If you’re reading this, perhaps something’s already broken.

If you’re reading this, perhaps something’s already broken.

HotDocs, Contract Express, PatternBuilder: whichever tool your firm built its templates on has become the bottleneck. In a mid-size firm, that usually means one person knows how to change a template, and everyone else waits.

What firms rarely see until they’re mid-migration is how much the old platform was costing them. Not just in licence fees, but in the hours your best people spend on maintenance, workarounds and templates nobody dares touch.

This guide is for the partners, knowledge leads and IT managers running that switch with a small team. Every section draws on real migrations with real clients. Most of them wish they’d done it sooner.

“The best migrations are the ones nobody notices. The templates work. The integrations hold. The lawyers draft as they always have, just on better infrastructure.”

“The best migrations are the ones nobody notices. The templates work. The integrations hold. The lawyers draft as they always have, just on better infrastructure.”

From the foreword · A Mid-Size Firm’s Guide to Switching Document Automation Platforms, Avvoka

01 Why firms are switching now

01 Why firms are switching now

Most mid-size firms don’t decide to switch. They reach a point where staying costs more than moving.

Most mid-size firms don’t decide to switch. They reach a point where staying costs more than moving.

~20x faster

SFA drafting time drops from 3 hours to 10 minutes at a firm that moved off their legacy platform.

Hours to 10 minutes

SPA production time at a firm that migrated off Contract Express, without rebuilding their precedent library.

6 hours saved per deal

Document assembly time recovered at a European firm, from the very first template they migrated.

The real cost

Licence cost is rarely the whole bill. Add consultants, hosting, training and the lawyer hours lost to maintaining complex templates, and the total cost of ownership quietly balloons. For a mid-size firm, that’s budget you could be spending on growth.

The one-person problem

In most mid-size firms, automation sits with one person, often a lawyer doing it on the side. Everyone else waits. When that person leaves or gets busy, the queue builds. Practice groups stop asking. Lawyers go back to manual drafting.

“We have just one person who is basically responsible for building documents.”

Head of Technology, UK firm

The platform is falling behind

The legacy platforms haven’t really changed in years. The way lawyers work has. They now expect their tools to talk to each other, to plug into the systems they already use, to make the most of AI, and to feel as easy to use as everything else on their desktop.

First-generation automation was never built for any of that, and the workarounds have run out of road. That gap is what most teams are really moving away from.

Case snapshot

The integration story we hear weekly.

The integration story we hear weekly.

A large global law firm was paying £100,000+ a year in middleware just to keep their automation tool connected to their DMS. Within three months of moving to Avvoka, the middleware was retired. The integration now runs through a single API connection, owned by their in-house team. The saving paid for the migration in year one.

→

Middleware cost eliminated

→

Integration owned in-house, not by a third-party consultancy

→

DMS handoff reduced from hours to seconds

02 Planning a lean migration

02 Planning a lean migration

From template audit to go-live: how to plan a migration your team can run alongside client work.

From template audit to go-live: how to plan a migration your team can run alongside client work.

Start small. Move fast.

It’s tempting to move everything at once: “Let’s switch every template before the licence renews.” In practice, big-bang migrations stretch a small team too thin, testing becomes unmanageable, and when something goes wrong there’s nobody free to fix it.

Firms that succeed do it in phases. They start with a handful of high-use templates, move those first and learn as they go. Early wins build momentum with partners. Then they move the next batch.

The template audit: 80/20, housekeeping and prioritisation

Before anything moves, audit what you have. For each template, ask: is it actually being used? Is it the best version? Could it be merged with another? Around 20% of a firm’s templates produce most of its documents. The rest are edge cases, old variations and things nobody touches.

Try it · template audit
How much of your library is dead weight?
Slide to your firm’s template count. We start from the ratio we saw at a top-tier European firm; drag the navy bar if you think yours differs.
Templates in your library300
Share in genuine use · drag the navy bar22%
~67
likely in genuine use (22%). Migrate these, starting with the high-usage ones.
~233
candidates to consolidate or retire: edge cases, old variations, templates nobody touches.
Illustrative only. At that firm, 312 of 1,400 templates (22%) were in use and an 18-month project finished in 7. Your audit will tell you your real number.

Use the moment

Migration is the best chance you’ll get to clean house. A platform change gives you cover to retire templates people have quietly protected for years, merge variations and give each practice area clear ownership. Raise those questions in planning, not mid-migration.

Case snapshot · top-tier European firm

1,400 templates in. 312 out.

1,400 templates in. 312 out.

A top-tier European firm came to us believing they needed 1,400 templates migrated. After audit, just 312 were genuinely in use. The remaining 1,088 were retired during migration. An 18-month project completed in 7.

→

77% of the legacy library retired as dead weight

→

Migration timeline cut by more than half

→

Practice groups re-engaged with their own template ownership for the first time in years

How to run it

How to run it

Three things decide whether a migration succeeds: what you move first, who’s on the team, and how you roll it out.

What to move first

Action
Consideration
High-usage templates from your busiest practice areas
Your first advocates.

Who you need

Sponsor

A partner who holds the budget and can clear blockers fast.

Template owners

Lawyers or PSLs who know how templates are used day to day.

End users

Partners and associates who draft daily.

IT

Security and integrations, in-house or your IT provider.

Vendor

Brings the playbook, tooling and people, so you don’t need extra headcount.

How you roll it out

1

Run old and new systems in parallel for 2–4 months.

2

Monitor adoption, output quality and support volume live.

3

Fix bugs and answer questions in real time.

4

Retire the old system only when the new one has earned it.

Each group has different success metrics. Plan for that, don’t hope they align on their own. A migration is a rare chance to fix what is broken, which means you rebuild rather than reproduce.

How Avvoka helps

Our Customer Success team runs this playbook with you, from template audit through to switch-over, so you don’t need to hire for the project. You bring the legal knowledge. We bring the migration expertise.

Case study · the same playbook, at scale

Template migration at scale.

Template migration at scale.

Top-tier law firm: 1,200 templates off two legacy automation platforms in 12 months.

1,200

templates

S 480 · M 420 · L 210 · XL 90

4

Avvoka FTE

Dedicated automation specialists

30+

years combined

Legacy-platform veterans

100

days to priority

All revenue-critical templates live

The approach

A decade of automation, from one-page letters to facility agreements with hundreds of conditional branches, spread across two legacy platforms.

Two waves: roughly 350 revenue-critical templates first, then the remaining 850 in rolling batches by size. Every template went through five stages: consolidate, convert, QA, early release, general release. A rebuild, not a lift-and-shift.

Outcome

100% of priority templates live by day 100.

The full 1,200-template portfolio migrated, consolidated and QA’d within 12 months.

Example programme · a large library

What you’d see, and when. Smaller libraries move faster.

Day 30–100: Revenue-critical templates on Avvoka; lawyers using them on live deals.
Priority wave · ~350 revenue-critical templates · ~100 days
Consolidation
Conversion
QA
Early release
General release
Remaining 850 · rolling batches by size (S to XL) · ~9 months
Consolidation
Conversion
QA
Early release
General release
ConsolidationConversionQAEarly releaseGeneral release
Illustrative programme, based on the 1,200-template migration above. Pick a phase, a month or a point on the chart to see what you’d see, and when.

03 What changes for your lawyers

03 What changes for your lawyers

What actually changes for your lawyers, your IT support and your bottom line, in plain English.

What actually changes for your lawyers, your IT support and your bottom line, in plain English.

Rebuild, don’t lift-and-shift

Your lawyers open a document, fill in the fields, get the output. That part doesn’t change. What changes is behind the scenes: the template that used to need a specialist can now be edited by the template owner in minutes, not weeks. No developer, no waiting, no backlog.

Rebuilding takes more effort up front than a straight copy-across. The payoff is a template library your own people can maintain, without relying on one specialist or an outside consultant.

See the migration from each seat in the firm:
What you’re movingWhat happens in migrationWhat your lawyers notice
In migration
Rebuilt cleanly
Your lawyers notice
Same document, same fields. No retraining.
Your team notices
Template owners can update without a specialist.

04 Driving adoption

04 Driving adoption

Why the best technology fails without the right rollout, and what the firms who got it right did differently.

Why the best technology fails without the right rollout, and what the firms who got it right did differently.

Technology is the easy part

Most legacy automation projects didn’t fail on technology. They failed because lawyers didn’t use them.

A tool that’s slow, hard to navigate or unpredictable will be abandoned for manual drafting every time. It happens quietly, then it happens permanently. A migration is the chance to break that pattern, but only if the rollout is treated as seriously as the technical work.

Lawyer smiling at his phone, from the guide

Case snapshot · global law firm

One template. Six practice groups.

One template. Six practice groups.

A leading global law firm adopted Avvoka across six practice groups after a proof of concept proved ROI with just one template, saving 6 hours per transaction on a live deal. Get the solution in front of partners and show the time to execution drop in real time.

→

6 hours saved per transaction on the pilot template

→

Six practice groups adopted following the proof of concept

→

Internal advocacy grew organically from the pilot cohort

Prove the value in the first 30 days

Advocacy doesn’t build on promises. It builds on visible wins. Track them out loud: hours saved per matter, time to close, errors caught before they leave the building. In a mid-size firm, one partner saying “this saved me three hours on the last deal” does more than any rollout plan.

Training is not one-size-fits-all

01

Most lawyers

Just want to generate documents: fill in fields, click a button, get clean output. Keep their training simple with a few example templates, step-by-step instructions and a support email.

02

Template owners and power users

Want to go deeper into template logic, conditional branches and hands-on editing. They need a different curriculum.

Two audiences. Two curricula. Even with a small team, the firms that get adoption right treat them separately from the start.

05 Why Avvoka?

05 Why Avvoka?

Built for modern legal work. Easy for a lean team to run.

Built for modern legal work. Easy for a lean team to run.

Built for the work you’re doing now

The legacy platforms in this guide were built for a different era, without APIs, cloud infrastructure, AI or non-technical users in mind. Avvoka was built from the ground up for modern legal work: cloud-native, every function available via API, and ready for AI. No servers to host and no specialist coders needed. ISO 27001 certified, SOC 2 Type II, full audit trails.

Legacy tool problem
How Avvoka addresses it
Template authoring sits with one person
True no-code authoring: your template owners maintain their own templates. No developers or consultants required.

“One of the best platforms I have implemented in my career.”

Head of IT, CLS Holdings

Proven migration experience

The approach in this guide comes from working through these same problems across dozens of firms moving off HotDocs, Contract Express, PatternBuilder, DocAssemble and Berkeley Bridge. We know how to structure the migration, phase the rollout and support lawyers through it, so a small team isn’t left to work it out alone.

06 Integrations

Connect Avvoka to the tools your lawyers already use.

Integrations · headless drafting

Use it where you work.

Use it where you work.

Your lawyers already draft with an AI assistant. Headless drafting brings your firm’s templates, clauses and rules into Claude, Copilot, Harvey and Legora, while the control stays in Avvoka. No extra platform for your team to learn.

See it working

Drafting from your Avvoka templates inside Claude.

Drafting from your Avvoka templates inside Claude.

A 2-minute tour of the Avvoka connector in action: search the template library, draft with the details filled in and export the finished file, all without leaving the chat.

The full guide · PDF

Take the full guide with you.

Take the full guide with you.

Every section, case study and checklist in one PDF, ready to share with your partners, practice leads and IT.

Every section, case study and checklist in one PDF, ready to share with your partners, practice leads and IT.

Cover of A Law Firm's Guide to Switching Document Automation Platforms

Looking to learn more?

See Avvoka in action with our virtual walkthrough. Or go straight to the number crunching with our ROI calculator.

This paper is provided for informational purposes only and does not constitute legal advice. Each firm’s migration path will be unique and should be tailored to your specific requirements, infrastructure and goals.