Migration from another program — Overview

Are you coming to Omniscol from another timetable management program? Several paths exist depending on the source program and how rich the available export is.

Available approaches

1. Native format importers

For two programs, Omniscol reads the native export file directly, without going through an intermediate spreadsheet: you select the file or files from the Import/Export screen (the UnDeuxTEMPS import, made of several .DBF files, sits in the French formats section).

For the other programs (Hyperplanning, EDT / Pronote, ADE), the migration goes through the spreadsheet mass import described in point 2: you export your data from the source program, you shape it in a spreadsheet, then you import it. Each page below details the correspondences and the pitfalls specific to the program concerned:

• From Hyperplanning (Index Education)
• From EDT / PRONOTE (Index Education)
• From ADE / ADE Campus

Aurion and Auriga are ERPs (school administrative management), not scheduling programs. Omniscol interfaces with them but does not replace them. See integrations.aurion and integrations.auriga for the integration modes.

2. Generic spreadsheet import

If your source program has no native importer, or if you prefer to control the formatting yourself: extract your data into a spreadsheet (Excel, Google Sheets, Numbers, Calc) and use the Omniscol mass import. See Mass import of courses from a spreadsheet.

3. Direct API

For an automated migration (for example if you want to synchronize during a transition period between two programs), you can write a script that pushes the data through the Omniscol API. See Omniscol API.

4. Manual re-entry

For small institutions or partial migrations, manual entry remains possible. Allow a few hours to a few days depending on the size.

Recommended migration strategy

1. Map your data — before anything else, take stock of what you want to transfer: teachers, students, rooms, subjects, class structure, current timetable, availabilities, absences.
2. Decide on the scope — often, not everything is transferred. Students can stay in the SIS and be synchronized afterwards. Historical timetables can remain archived separately.
3. Run a partial test import — on a subset (one class, one cohort) to validate the quality of the transfer.
4. Set the timeline — often, the switch happens at the start of the next school year rather than mid-year, to avoid managing continuity.
5. Train the users — Omniscol has conventions that differ from competing programs. Plan for training time, especially on the domain concepts (Class division, Group alignment, Group of groups).

Terminology specifics by source program