+33 670 330 003 contact@omniscol.com
Contact us Request a demo

Migrating from Hyperplanning (Index Education)

Hyperplanning (Index Education) is the most widespread timetable management program in French higher education. Migrating to Omniscol means bringing over your existing data (users, structures, current timetables) and adapting it to Omniscol concepts. This page summarizes the correspondences and the known pitfalls.

What maps directly

Hyperplanning Omniscol
Promotion (common core) Class
Partition of a promotion Disjoint groups; a division if those groups share the same time slot (simultaneous tutorials/labs)
Tutorial/lab subgroup (from a partition) Group in a division
Option Group
Regroupement (grouping) Group of groups (or an alignment across different classes/promotions)
Course Course (and its lessons)
Subject / module (UE, EC) Subject (often customized)
Calendar / periods Calendar mode (dated timetable, Premium); date windows to include/exclude periods
Room Room (specialization to carry over)
External instructor / adjunct Teacher marked as "external" (Premium option)

What needs attention

  • Alignments: in Hyperplanning, having tutorial or option groups from several promotions attend the same course at the same time is done through a shared course (often built with a grouping). When this shared course forces the same time slot, the same room and the same teacher onto groups from different classes, that is the Omniscol alignment. See Group alignments.
  • Groupings: a Hyperplanning grouping brings several groups together to attend the same course; in Omniscol this is a group of groups (available on all plans). See Groups of groups. Depending on the case, a grouping across different classes or promotions may instead be the alignment described above.
  • Associated lessons (alternating half-groups): Omniscol handles this natively through associated lessons. See Complex lessons.
  • Teaching service: pedagogical continuity (the same resources from one lesson to the next) is reproduced by keeping the same teacher and the same room on the lessons of a course — there is no dedicated entity.
  • Calendar-based courses: if you use Hyperplanning in calendar mode for modules with precise dates, Omniscol covers the same needs with its calendar mode, included in the Premium plan.
  • Hyperplanning vs Aurion: if your institution uses Hyperplanning and Aurion, the migration only concerns the scheduling side; Aurion keeps feeding the administrative structure. See Synchronization with external systems.

How-to

  1. Retrieve the data from Hyperplanning into a spreadsheet — lists of instructors, students, rooms and courses. Depending on your version, this is done by copy-pasting a list or through its export; refer to the Hyperplanning documentation.
  2. Prepare the Omniscol files in the import format: users CSV, courses CSV. See Preparing your data for a mass import.
  3. Create a sandbox Omniscol account to test the import risk-free.
  4. Import in several passes:
  5. Rebuild the complex courses (alignments, associated, alternating) by hand if the import flattened them.
  6. Check the diagnostic and fix the detected inconsistencies.
  7. Run a test generation to validate feasibility.
  8. Snapshot before switching over to the production account.

Migrating users smoothly

Good practice: import users into Omniscol as inactive first. You validate the data, you switch the configuration over (SSO if applicable), and you activate the accounts in a single pass when everything is ready. This prevents users from receiving a premature invitation.

What does not migrate

  • Hyperplanning history beyond the current timetables — to keep the history, keep Hyperplanning as a read-only archive rather than migrating everything.
  • Hyperplanning visual customizations — rebuild them in Omniscol according to your visual identity. See Panel customization.

How-to

Hyperplanning → Omniscol migration

  1. Migrating from Hyperplanning: the 8-pass sequence follows the order export → prepare → sandbox → multi-pass import → fixing complex courses → diagnostic → test generation → switchover.

  2. Pass 1 — Retrieval from Hyperplanning: get the lists (instructors, students, rooms, courses) out into a spreadsheet. Depending on the version, by copy-pasting a list or through its export — see the Hyperplanning documentation. The cleaner the source side, the faster the rest goes.

  3. Passes 2-3 — Prepare + sandbox: adapt the columns to the Omniscol template (see Preparing your data). Create a sandbox Omniscol account to test the import with no risk to production.

  4. Pass 4 — Multi-pass import in this order: users → classes and groups → subjects → courses via the mass import. The order matters: courses reference the classes and teachers, which must already exist.

  5. Pass 5 — Complex courses: alignments (courses shared by several promotions on the Hyperplanning side → Omniscol alignments), associated lessons (alternating half-groups), A/B alternating weeks. The import often flattens them — rebuild them by hand via the complex icons on the course card.

  6. Passes 6-7 — Diagnostic + test generation: let the diagnostic run, fix the inconsistencies. Run an automatic generation to check overall feasibility before migrating to production.

  7. Pass 8 — Switchover: create a snapshot before switching. Activate the user accounts (imported as inactive until now). Publish. Keep Hyperplanning as a read-only archive — the migration does not carry over history beyond the current timetables.

    If you also have Aurion: the migration only concerns the scheduling side, Aurion remains the administrative source. See Synchronization with external systems.

See also

See also