A data cutoff is the moment when work stops in your old system so the final data can be copied to the new one. The freeze is the window between that cutoff and the moment users start working in the new system. Planning both carefully is what makes a migration feel smooth to your staff and clients.
This guide explains how to choose a cutoff, how to handle work during the freeze, and what to communicate to your team.
Why a cutoff matters
Data keeps changing as long as people are working. If staff keep updating the old system while the final migration runs, those changes can be missed. A clear cutoff gives everyone a single point in time: everything before it moves to the new system, and everything after it happens in the new system.
How to choose your cutoff date and time
- Work backward from go-live. Your cutoff should leave enough time to run the final migration, validate the results, and fix any issues before users log in. Your test loads show how long that takes.
- Choose a quiet period. Many firms choose the end of the workday before a weekend, so the migration can run when fewer people are working.
- Avoid holidays and deadlines. Don’t schedule go-live around holiday weekends, month-end billing, or major filing deadlines.
- Check who’s available. The people who validate data and support users need to be available through go-live and the days after.
- Make it a firm decision. Confirm the cutoff with leadership and the project team, then treat it as fixed.
Full freeze or delta migration?
There are two common approaches, and many projects combine them.
Full freeze: Staff stop working in the old system at the cutoff, and nothing changes until the new system is live. It’s simpler and lower risk, but it works best when the migration window is short, such as over a weekend.
Delta migration: Most data is migrated ahead of time, then only the records that changed since that first load are moved at cutoff. This shortens the freeze for large data sets, but it adds complexity and requires reliable tracking of changes.
Your migration team should recommend an approach based on your data volume and how long a full load takes in testing.
What happens to work during the freeze
Law firms can’t simply stop. Plan how urgent work will be handled while neither system is available for normal use:
- Intake: Decide how new leads will be captured, such as a simple form or shared log, and who will enter them into the new system after go-live.
- Deadlines and calendars: Export or print upcoming deadlines so nothing is missed during the window.
- Documents: Tell staff where to save anything they create during the freeze.
- Client communication: Make sure staff know how to reach case information if a client calls.
- Read-only access: If possible, keep the old system available in read-only mode, so staff can look things up without making changes.
Turn off automation during the load
Before the final data loads, automation and integrations in the new system (such as workflows, notifications, and connections to other systems) are usually turned off, so that loading thousands of records doesn’t trigger emails, tasks, or updates by mistake. Once the data is loaded and validated, they’re turned back on and tested. Make sure your project plan names who is responsible for each step.
What a typical go-live weekend looks like
Every project is different, but a weekend go-live often follows a rhythm like this:
- Before the weekend: final preparation, a go/no-go check, and reminders to staff about the cutoff.
- Cutoff: work stops in the old system, and the final data and document migration begins.
- Migration and deployment: data and documents are loaded, and the final configuration is deployed to production.
- Validation: the project team and your validators check counts, sample matters, documents, and reports.
- Release: users receive access, with support ready for the first day.
- The first weeks: daily check-ins, an issue tracker, and quick fixes as the firm settles in.
What to tell your staff
Clear communication prevents most go-live stress. At least two weeks before cutoff, tell everyone:
- The exact cutoff date and time, and what to finish before it.
- What to do during the freeze, and who to contact with urgent questions.
- When and how they’ll get access to the new system.
- Where to find training materials and how to get help after go-live.
Send a reminder a few days before and again on the day of the cutoff.
Have a fallback plan
Decide in advance what happens if validation finds a serious problem: who makes the go or no-go decision, how long you can delay, and how staff will keep working in the old system if needed. Most projects never use their fallback plan, but having one makes the decision faster and calmer if something goes wrong.
For the full picture of what comes before cutover, see our law firm data migration checklist and Litify implementation timeline, or talk to our data migration team.
Frequently asked questions
What is a data cutoff?
A data cutoff is the point in time when work stops in the old system so the final data can be copied to the new one. Everything before the cutoff is migrated, and everything after it happens in the new system.
What is a data freeze?
A data freeze is the window between the cutoff and go-live, when the old system is no longer updated and the new system isn’t yet in use. Firms plan how urgent work will be handled during this time.
What is a delta migration?
A delta migration moves most data ahead of time, then moves only the records that changed since that first load at cutoff. It shortens the freeze for large data sets.
Why do go-lives often happen on weekends?
Weekends give the team time to migrate, deploy, and validate while fewer people are working, so users can start fresh in the new system at the beginning of the week.
