Switching Timetabling Software Without Starting Over

The biggest reason schools stick with tools they've outgrown isn't loyalty—it's the absolute dread of re-entering ten years of school data. Here’s how migration actually works, and a checklist for doing it safely.

Every school has that one piece of software.

The interface looks like it was built in 1998. The annual license is eye-wateringly expensive. And, for some reason, it only runs on that one aging PC in the back office. Every spring, someone in a leadership meeting sighs and says, "We really need to find an alternative." And every spring, the same defeatist objection wins: "But all our data is in there."

It's a fair concern. Think of all the names of teachers, subject codes, student groups, room capacities, curriculum hours, and the hundreds of tiny, manual tweaks built up over a decade. The thought of re-typing all of that from scratch into a new tool is so painful that the status quo wins by default, year after year.

But this fear is built on a misunderstanding. The question you should be asking isn't, "Do we want to manually re-enter everything?" (The answer is a hard no.) The question is: "Can the new software read what our old software wrote?"

Here is a secret the timetabling software industry doesn't advertise: your school's data isn't actually trapped. Most established tools export or store data in formats that other programs can read. Whether it's structured XML files, CSV tables, or file formats that have been thoroughly reverse-engineered after years of use, the doors are open.

This means a modern tool doesn't require you to start from a blank canvas. For instance, Arignote Timetable is built to import existing files directly from the most common programs:

• FET (the open-source standard)
• gpUntis (widely used throughout Europe)
• aSc TimeTables (one of the global commercial giants)
• Penalara GHC (common in Spanish-speaking regions)
• Additio and PlanIt (popular planning tools)

An import like this handles the massive, boring foundation of your school. In a matter of seconds, your teachers, subjects, rooms, student groups, and the lessons linking them are brought into the new system. The only things you'll need to review by hand are the subjective details—like teacher preferences, availability windows, and pinned slots. Those are policies, not structure.

If you're thinking about switching, you don't have to take a leap of faith. You can test the waters in parallel without changing a single thing about your current process. Here is a sane, step-by-step checklist to guide you:

1. Grab an export today. Don't wait until you're ready to switch. Licenses expire, hard drives fail, and the one person who knows how to export the files might retire. Save a clean export file from your current software in a safe, shared folder. Consider it cheap insurance.
2. Run a test import. Load that export file into the new tool and do a quick head count. Do the number of teachers, rooms, and class groups match? Spot-check one or two complex cases—like a part-timer who only works mornings, or a shared science lab. A ten-minute audit will tell you exactly how well the import worked.
3. Generate a draft and compare. Let the new solver build a schedule using your imported data, then place it side-by-side with your current timetable. This is the fun part. Sometimes, the new solver will instantly find a cleaner, tighter layout than you’ve ever had. Other times, it will throw errors that reveal rules which existed only in the head of your timetabler and were never written down. Both results are incredibly valuable.
4. Run a parallel cycle. For the ultimate test of confidence, build next term's schedule in both tools. The real value of software isn't on a feature checklist; it's how it handles your school in week three when a teacher goes on leave or a classroom floods.
5. Archive the old file. Once you're fully satisfied and ready to decommission the old system, keep the final export file archived. It's your school's history in a tiny file.

A migration is only worth doing if the destination makes your daily life noticeably better. Here is what you should expect from a modern scheduling tool:

• Speed: Getting a complete, conflict-free schedule in minutes rather than days. This lets you experiment with different ideas instead of committing to the very first grid that doesn't break.
• Modern Accessibility: Having native apps that run beautifully on macOS, Windows, Linux, Android, and iPad. No more queuing up to use the designated "timetabling computer" in the office.
• Safety Net: Live conflict detection while you edit by hand, ensuring you don't accidentally schedule a teacher in two places at once.
• Sophisticated Handling of Hard Cases: Effortless management of double periods, synchronized option blocks, room categories, and staff meetings.
• One-Click Publishing: Exporting beautiful, printable timetables in PDF, HTML, or Excel format. You can generate custom posters for classrooms, teachers, and students in seconds.
• A Localized Interface: Arignote, for example, runs natively in eight languages (English, Spanish, Catalan, French, German, Italian, Estonian, and Portuguese).

Every time we stick with outdated tools because "our data is in there," we are choosing a different kind of pain. We pay for it in expensive annual maintenance fees, hours of manual double-checking, and the anxiety of relying on ancient software that only one person knows how to run.

"All our data is in there" is the perfect reason to export your data—not a reason to stay locked in.