If you’re reading this, you’ve probably already had the conversation with your IT director: the Legistar contract is up for renewal, the price went up again, and someone on the council is asking why the city is paying more for agenda software than for the city attorney’s retainer.
Replacing Granicus Legistar is doable. It’s also rarely as hard as the incumbent vendor will tell you it is. Here’s what migration actually looks like for a small-to-mid-sized California city.
What you actually have in Legistar
The first surprise for most clerks evaluating migration is how little of Legistar they actually use. The platform was built around a comprehensive legislative model — departments, files, sponsors, history, motion tracking, attachments, multi-version language. Big cities use most of it. You probably use about 20%.
Inventory before you migrate. The categories that matter:
- Active agendas and meetings — the next 60 days of scheduled meetings.
- Historical agendas and minutes — usually 5–15 years of records.
- Legislation/file history — ordinances and resolutions with their action history.
- Attachments — staff reports, exhibits, supporting documents (often the largest single chunk by file size).
- Video recordings — usually hosted by Granicus separately, often the stickiest piece.
What migrates cleanly, what doesn’t
Three things migrate well: meeting metadata (date, body, type), published agenda PDFs (just files), and historical minutes (also just files). These are essentially export-and-reimport operations.
Two things are messy: file/legislation history with full action chains, and embedded video. Legistar uses a proprietary file structure for legislation; recreating action histories in a different platform is possible but takes work. Video, if you’ve been using Granicus’s hosted video, is exportable but you’ll need to decide whether to re-host it (cost) or just keep historical video on Granicus (cheap, but you maintain a deprecated account forever).
The pragmatic answer for most cities: migrate the last 5 years of agendas and minutes as searchable PDFs into the new system, leave older history archived as static files on the city website, and decide on video case-by-case. You don’t need every 2009 study session to be live in the new platform.
The actual timeline
If you start the conversation in January, you can be off Legistar by July. The work breaks down roughly:
- Month 1: Vendor selection and contract. Two weeks of demos, two weeks of negotiation. Don’t skip the demo with your real data.
- Month 2: Parallel running. The new platform runs alongside Legistar. Clerk publishes the same agenda in both systems for 4–6 meetings. This is the most important phase — the only way to surface workflow gaps is to actually do the work.
- Month 3: Historical migration. Bulk import of past agendas, minutes, attachments. Most modern vendors will do this for you.
- Month 4: Cutover. One meeting in the old system, the next meeting in the new. The week between is when you announce to the public.
- Month 5–6: Cleanup and contract wind-down. Cancel the Legistar renewal, archive what needs archiving, redirect old URLs.
Things vendors will warn you about (that don’t actually matter)
“You’ll lose your URL structure.” This is true and almost completely irrelevant. Modern platforms generate their own URLs and you can put 301 redirects on the old ones. The number of people who deep-link to specific Legistar agenda items is approximately zero.
“Your search index will be gone.” Also true, also fine. New platforms index from the imported PDFs. Search comes back; it just looks different.
“Your council will be confused.” They will be, for one meeting. Modern platforms have a learning curve measured in minutes for council members, who mostly just need to see an agenda and click on items. The clerk is the only one with a real learning curve, and that’s what the parallel-running month is for.
Things that actually matter
The transition committee meeting. Get the city manager, clerk, IT, and the council’s liaison in one room before you sign anything. Confirm everyone agrees on the timeline and the cutover meeting. Surprise transitions destroy clerk trust faster than any technical issue.
The first meeting in the new system. Don’t pick the controversial budget hearing. Pick a routine meeting with a known, calm agenda. The first meeting will surface problems; you want to surface them on a low-stakes night.
Public communication. Tell residents the URL is changing and why. A 200-word post on the city homepage two weeks before cutover prevents 90% of “where did the agenda go” calls.
What you save
For a typical 10K–30K California city, Legistar plus Granicus video runs $18K–$35K per year. Modern alternatives serving the same use case run $1K–$8K per year, depending on plan and feature mix. The licensing savings alone usually pay for the migration project in the first year.
The bigger savings are operational. Clerks at cities that have migrated typically report 4–8 hours saved per meeting cycle, mostly on minutes and posting. That’s 100–200 hours of clerk time per year.
How to start
Three concrete steps:
- Pull your last Legistar invoice. Check what you’re actually paying versus what was budgeted.
- Ask your clerk how much time the current workflow takes. Get specific numbers per meeting cycle.
- Demo two or three modern platforms with your real data. The differences become obvious in 10 minutes.
Most clerks who’ve been on Legistar for a decade are surprised at how much better the workflow looks on a platform built in the last five years. The work is real but it’s manageable, and the cities that have done it almost universally describe the post-migration experience as “wish we’d done this years ago.”