Migration et intégration
Vos anciennes données ne doivent pas devenir un obstacle à votre transformation numérique
Years of student history are the reason most institutions postpone changing systems. The migration is therefore treated as a project with its own stages, its own validation and its own reversibility — not as a data load performed the weekend before go-live.
Le parcours de migration
Six stages. The institution validates the result before anything becomes authoritative, and the previous system stays available until it does.
Diagnostic
Audit of the existing data, applications and constraints: what exists, where it lives, what quality it is in, and what must be preserved for legal or accreditation reasons.
Préparation
Cleaning, normalisation and the rules that govern the transfer — how duplicates are resolved, how incomplete records are treated, what is deliberately not migrated.
Migration pilote
Import into a test environment, so the result can be examined before any decision is irreversible.
Validation
Checks and formal acceptance by the institution. Counts, spot checks against the source, and confirmation by the services that own each dataset.
Bascule
Progressive move into production, service by service or cohort by cohort rather than all at once.
Accompagnement
Training, support and stabilisation through the first full cycle — the period in which the questions that matter actually arise.
D’où proviennent les données
Institutions rarely have one source. A typical migration draws on four or five of these at once, each maintained by a different service.
Fichiers Excel et CSV
The most common starting point — one file per service, each with its own conventions.
Anciennes bases de données
Direct extraction from an existing schema, mapped onto the target model.
ERP existants
Export-led migration where the incumbent system permits it.
Plateformes d’apprentissage (LMS)
Users, courses and enrolments from an existing LMS.
Logiciels de scolarité
Registry, enrolment history and academic records.
Applications internes
In-house tools built around one service, often undocumented.
Systèmes financiers
Fee schedules, payment history and outstanding balances.
Intégrations
Available today and planned, kept strictly apart. Nothing below is described as operational before it has been validated technically.
Disponible aujourd’hui
Synchronisation of users, courses and enrolments with an existing Moodle installation.
Account provisioning and single sign-on for institutions on Microsoft 365.
Single sign-on for institutions using Google Workspace.
Guided import with column detection, for students, teachers and other registries.
Dans la feuille de route — non disponible aujourd’hui
Push of fee and payroll data into an external accounting system.
Reporting to ministry or regulator platforms.
Online tuition payment collected directly through the platform.
If an integration you depend on is in the second list, say so when you request a demonstration. It changes the shape of a deployment plan, and it is better established before a contract than after one.
Voyez-le sur votre propre établissement
La démonstration est préparée autour des modules dont vous avez réellement besoin : parlez-nous de votre établissement et nous construirons la séance sur cette base.