Replace what no longer works, on your timeline
The Modernization Program moves an agency off a legacy system one written phase at a time: your history converted and reconciled, your integrations kept running, both systems live in parallel, and a scope you agreed in writing before anyone started.
eCourtDate is not affiliated with, sponsored by, or endorsed by any case management vendor named on this page. Product names are used only to identify the systems discussed, and each is the property of its respective owner.
The six reasons agencies stay, answered plainly
Every one of these is a reasonable thing to worry about, and each one is a question the written scope answers before work starts.
“We will lose our history.”
You will not. Cases, parties, events, documents, financials, and notes migrate intact, and every record is reconciled by count and by content against what you sent. You get the reconciliation report, so you can show a judge or a commissioner that nothing was lost.
“Everything is wired into it.”
Then leave it wired. eCourtDate exchanges data bi-directionally with the system you are moving off, by REST API or SFTP, so the interfaces feeding your jail, your prosecutor, your state reporting, and your public portal keep running while you transition.
“We cannot survive a multi-year project.”
You should not have to attempt one. Move one case type or one division first, run both systems in parallel until your team is ready, and expand from there. There is no weekend where everything changes at once.
“We do not have the staff for this.”
The conversion is mostly automated: the pipeline profiles, maps, transforms, and reconciles. Your team reviews and approves the mapping and the sample records. It does not do the data entry, and it does not need a dedicated project office.
“We cannot get it through budget.”
Pricing is published. You can build the request before you talk to anyone, compare it against what you pay today, and take a real number to a commission or a legislature rather than waiting on a quote.
“Procurement will take a year.”
Sometimes. Many agencies buy through an existing state contract or a statewide program instead, which is a purchase order rather than a solicitation. The How to Buy page lists the paths eCourtDate supports, and your procurement team determines which applies.
How the Modernization Program runs
The system your agency chose was the right choice for the year it was chosen. The question now is only what the agency needs next. Six phases, scoped in writing before work starts. Most of the risk in a system change lives in phases 2 and 5, so those get the most attention here and the most of your team’s.
- 01
Scope the move with your team
Which case types, which divisions, which integrations, and what has to keep running. You leave this conversation with a written scope and a phase plan, not a proposal deck.
- 02
Get your data out of your current system
Your agency requests its own data under its own agreement and its state records law. We provide sample request language your counsel can adapt, and the technical specification of what we need, so the ask is precise the first time.
- 03
Convert, validate, reconcile
The pipeline profiles every field, maps it into the eCourtDate model, transforms it, then reconciles the result against your source by count and by content. Your team reviews the mapping and a sample before anything is committed.
- 04
Configure to how you actually work
Case types, statuses, workflows, forms, roles, notification rules, and calendars, set up with your administrators in the admin they will keep using afterward. Training happens on your own configuration, not on a generic sandbox.
- 05
Run in parallel
Both systems live, one scope at a time, through the parallel-run period set in your written scope. This is the phase that turns a risky cutover into an ordinary Tuesday.
- 06
Cut over, then expand
Retire the old scope when your staff say it is ready, and move to the next one. Some agencies finish in a single phase; others take a year by choice. Both are the program working as intended.
What the program includes
The specifics of scope, timing, dependencies, and price are set in your agreement, because a public agency should be able to hold a vendor to something written down rather than to a web page.
What is on this page is what the program does. What is in your agreement is what eCourtDate owes you. We would rather those two things match exactly than have the second one be smaller than the first.
- A written scope and phase plan
- What moves, in what order, with what dependency on your team and on your current vendor’s export timing. Agreed before work starts.
- Mostly automated conversion
- Profiling, mapping, transformation, and reconciliation run automatically. Your team reviews and approves; it does not re-key.
- A reconciliation report
- Record counts and key fields matched against your source, so you can prove to anyone who asks that the history came across intact.
- A parallel-run period
- Both systems live at once, scope by scope, through the period set in your written scope. No big-bang cutover.
- Coexistence for what you keep
- Bi-directional exchange with the systems staying in place, by open REST API, webhooks, or SFTP, using interfaces the other system documents or your license permits.
- Bulk export, any time
- JSON, CSV, or SQL, on demand, plus a REST API and SFTP. Export is a product capability, not a services engagement.
Who selects the system decides the path
In some states the administrative office of the courts selects the case management system for every court at once. In others an elected clerk decides for one county at a time. The same page cannot do the same job in both, so pick the path that matches your state.
If your administrative office of the courts selects the case management system
Your court runs the system the state chose. What it can still run alongside it, on its own decision, is the rest of the platform: reminders, scheduling, payments, and supervision. The statewide program path is for the AOC itself.
If your clerk’s office selects it
The move is decided county by county, and the clerk remains custodian of the record throughout. Start with the purchasing path your office can use, then see the platform on your own records.
If yours is a municipal or justice court
The clerk and the administrator are often the same person, and the decision runs through the council or the city manager rather than a commissioners court. The municipal courts page is written for that path.
The standards your agency already has to meet
They are set by federal policy and by your state, not by a vendor. eCourtDate meets the ones below, stated in each authority’s own terms, so the sentence your office takes to a board is that the platform meets the standard.
- CJIS Security PolicyFBI Criminal Justice Information Services
- CJIS compliant. Built to meet the FBI CJIS Security Policy, with fingerprint-based screening for staff who handle criminal justice information. Details
- FedRAMP High hostingFederal Risk and Authorization Management Program
- Hosted exclusively in AWS GovCloud (US), which holds FedRAMP High authorization. Details
- GovRAMPGovRAMP
- GovRAMP member, listed on the Progressing Product list. Details
- WCAG 2.2 AA and Revised Section 508W3C and the U.S. Access Board
- The staff admin and the public portals are built to WCAG 2.2 AA, with a published VPAT covering the Revised Section 508 standards. Details
- FIPS 140-2/140-3National Institute of Standards and Technology
- Encryption and key management on FIPS 140-2/140-3 validated cryptographic modules. Details
Each line above is recorded in the claims register with its source. Connections to a state e-filing manager or a records-integration standard are named for your state only once they are built and in use; they are part of scoping, not of this page.
Systems eCourtDate converts from and connects to
The conversion pipeline works from your exported data rather than from any vendor’s internal documentation, which means the list below is descriptive, not exhaustive. If your system can export its records, we can convert them, including the homegrown one that only one person understands.
Tyler Technologies Odyssey and Enterprise Justice
Case management, county and state courts
Tyler Technologies Incode
Municipal court
Journal Technologies eCourt
Case management, courts and justice partners
Thomson Reuters C-Track
Case management, appellate and trial
equivant JWorks and CourtView
Case management, county courts
Catalis
Court case management
Justice Systems FullCourt Enterprise
Case management
CentralSquare
Public safety and justice
i3 Verticals NetData
Municipal court
Cardinal Tracking, iDocket, LGS, Tech CMS
Municipal and county systems
An in-house or homegrown system
Built in-house, often with one person who knows it
Spreadsheets, paper, and a shared drive
A supported starting point
Naming a system here does not imply any relationship with, or any statement about, the company that makes it. We convert from exported data your agency lawfully provides, and we do not use vendor documentation received under confidentiality terms.
Your data belongs to your agency. Ask for it that way.
The single most useful thing an agency can do before a system change is request a complete export of its own records, in a documented format, under its own agreement and its state public records law. Do it early, because export timing is the dependency that most often sets the schedule.
We give you sample request language and the technical specification of what we need, so the request is precise the first time and does not turn into three rounds of clarification. Your counsel should review and adapt the language: it is your contract, your records law, and your relationship, and we will not pretend to read an agreement we have not seen.
eCourtDate stays out of the request chain. We do not send letters on your behalf, and we do not contact your current vendor without your written authorization naming the scope.
Buying it does not have to take a year
Work with your procurement team to choose the process that fits your agency. Explore direct purchasing, resellers, eligible contract vehicles, and competitive procurement.
See How to BuyState contracts and cooperative agreements
Minnesota agencies and CPV members can purchase through SWIFT Contract #270435, awarded for statewide mass notification and alerting services. Other paths are described on the How to Buy page.
The Minnesota programStatewide programs
The Texas Office of Court Administration runs its statewide court reminder program on eCourtDate, authorized by HB 4293. Texas courts join the program rather than procuring separately.
The Texas programYour own solicitation
If you are writing an RFP, published pricing means you can size the budget before you publish it, and a well-specified requirement produces a better outcome whoever wins it.
Build or buyWhen staying where you are is the right call
Naming these now is better than finding them during a conversion. There are four situations where switching is the wrong move.
Your current system was implemented recently, your staff are happy with it, and the operational gaps you have are ones a single eCourtDate product can fill alongside it. Start there and leave the record where it is.
You are mid-implementation on a replacement already. Finishing is almost always cheaper than switching direction, and eCourtDate will still be here.
Your agency has a statutory or contractual obligation to a specific system that has not been examined by your counsel. Get that answered first; it changes the whole analysis.
The problem you actually have is process rather than software. Some backlogs are staffing and scheduling problems wearing a technology costume, and no platform fixes those.
In the first case especially, the answer is usually to add one product alongside what you run today. Reminders, payments, portals, jury, citations, or warrants can all go live without touching your case record, and they will still be there if you decide to move it later.
Switching questions, answered
What court administrators, IT directors, and finance officers ask before committing to a system change.
What does the Modernization Program cost?
How long does a switch take?
Do we have to replace everything at once?
How do we get our data out of our current system?
What formats can you take?
What if the export takes longer than expected?
Can we keep some of our existing systems?
What happens to the integrations we already built?
Is our data secure during the migration?
Can we get our data back out of eCourtDate later?
How do we buy it?
Can you help us write the requirements?
Who does the training?
What if we start and it is not working?
Accuracy of this page
Last reviewed 9 September 2026. Every claim on this page is about eCourtDate and is recorded in our internal claims register with its substantiation. We make no claim on this page about any other company’s product, pricing, timelines, or implementation record.
If you believe anything here is inaccurate, including anything about a system named above, write to info@ecourtdate.com and we will respond within five business days. Corrections are published and dated rather than quietly edited.
Bring us a sample export
The fastest way to find out whether a switch is realistic for your agency is to put your own records in front of you inside eCourtDate. That is what the first conversation is for.