What it is for
The Migration from Cegid LMS page reads a Cegid LMS platform through its web services and recreates its content in DGTLMS. It never changes the Cegid platform: it only reads from it.
A migration can be interrupted and restarted as many times as needed: whatever has already been migrated is not created again, and an object that already exists in DGTLMS (same username, same site name) is linked without being changed.
- Be a DGTLMS super administrator (the page does not appear for other profiles).
- On the Cegid side, authorise the IPv4 address of the DGTLMS server in the web services access configuration (list of authorised addresses). It must be the IPv4 address: without it, every call is refused ("accès refusé par Cegid", access refused by Cegid).
- If the Cegid platform requires authentication on its web services, have the WS username and password.
- To migrate the module files, have a Cegid super administrator account (username and password): it is used to open Cegid's "Export a course" page.
- Database update 173 must be applied (
Administration → Update); otherwise the page tells you so.
Steps
Open the page
Administration → Integrations & Connectors → Migration from Cegid LMS.Connect to Cegid
Enter the platform address (for example
client.elmg.net;https://is accepted) and the WS credentials if needed, then click Connect and read the inventory. The credentials stay in your session: they are not saved.Choose the scope
The inventory shows the number of sites, users, groups, sessions and courses. Tick the sites to migrate, the sessions not linked to any site, and the Outside sessions box (courses, users and groups that belong to no session); each box shows what it brings. The list of courses only shows those of the ticked boxes — a course assigned directly (outside sessions) to a user or group enrolled in a session follows that session's site —: untick the ones you do not want to migrate (test courses…), then click Save selection. To have the client approve the list, Exporter (Excel) or Exporter (HTML) (the page is in French: « Export ») downloads every course in the inventory with its Cegid ID, title, number of modules, date, number of sessions and enrolled learners, sites, choice (kept or not) and DGTLMS ID once migrated. Enrolled learners are those of the sessions (directly or through a group) and of the direct assignments read during the inventory; direct assignments of users enrolled in no session are not counted.
Start the migration
In "3. Migration", click Start the migration and keep the page open. The nine steps run one after the other, each with its progress bar: sites, users, groups, members and sub-groups, courses and modules, sessions (enrolments and session courses), groups enrolled in sessions, direct assignments, results and answers to questions. Interrupt stops after the current batch; Start the migration resumes where it stopped.
Migrate the files automatically
The web services do not transmit the module files (SCORM, videos, documents). In "4. Module files", enter the Cegid super administrator account, click Check the account, then Download and install the missing files: each course is downloaded from Cegid's "Export a course" page, then installed.
Or migrate them manually
Export the courses from Cegid's "Export a course" page (
export_<id>.zipfiles, without renaming them) and upload them with Install the archives. For an archive too large for the browser, drop it by SFTP into the folder shown on the page, then click Install the archives uploaded to the server.Check the modules
The table in section 4 shows, for each course, the number of launchable modules and the status: complete, partial or to import. Above it, modules that do not launch are counted by cause, with what to do; the À vérifier (to check) column lists them course by course, each with a link to open it in the player.
Check the summary and the log
"5. Summary" counts the objects created and linked to existing ones; the log lists what needs your attention (see below).
What is migrated
| Item | Migrated into DGTLMS |
|---|---|
| Sites | The site and its drop zone (the Cegid site's default session is linked to it); not its site administrators |
| Users | Learners, instructors and administrators, with their level. Username, last name, first name, email, dates, language, active status, custom fields, password (users log in with the one they had on Cegid) |
| Groups | Members (all levels), sub-groups and parent groups, delegate |
| Courses | Title, description, keywords, custom fields, visual, modules (threshold, prerequisites, weight, elimination, visual) |
| Sessions | Dates, options, welcome text, enrolled users (learners and instructors), enrolled groups, courses in the Cegid order |
| Assignments | Courses assigned directly to a user or a group |
| Results | By module, by course and by session (status, score, time spent, progress, dates) |
| Answers to questions | The last answer to each question, visible in the answer details |
Read the log
Each line has a level: info (step finished, files installed), warning (to check, the migration continues) or error (item not migrated). The most common messages:
- "accès refusé par Cegid" (access refused by Cegid) — the server's IPv4 address is not authorised on the Cegid side, or WS credentials are required.
- "Login … déjà présent dans DGTLMS : compte existant rattaché, non modifié" (username already in DGTLMS: existing account linked, not changed) — the DGTLMS account receives the Cegid enrolments and results; its details do not change.
- "super-administrateur sur Cegid, créé administrateur" (super administrator on Cegid, created as administrator) — for security, no super administrator is created; raise the account manually if needed.
- "niveau personnalisé Cegid … non repris" (custom Cegid level not migrated) — the account has been given the matching standard level (learner, instructor, administrator).
- "nom déjà pris dans DGTLMS, créée sous … (Cegid)" (name already taken in DGTLMS, created as … (Cegid)) — a session with the same name already existed: the migrated session gets the suffix "(Cegid)".
- "… SCO dont les fichiers restent à importer" (SCOs whose files still need importing) — normal after the Courses step: move on to "4. Module files".
- "fichier de lancement absent" (launch file missing) — the course archive has not been installed (or does not contain this module): install it.
- "lien vers le dossier d'un autre parcours (« ../ »)" (link to another course's folder) — on Cegid, this module used the files of another course. As soon as that course is migrated and its archive installed, DGTLMS copies the files into the course and fixes the link ("fichiers repris du parcours Cegid #…").
- "module Flash, illisible dans les navigateurs actuels" (Flash module, unreadable in current browsers) — no browser plays Flash any more: ask the module's author for an HTML5 version.
- "lien repris en https" / "lien externe non sécurisé" (link switched to https / insecure external link) — an external
http://link is switched tohttps://when the site answers there; otherwise it opens in a new tab. Check that the site still exists. - "fichier(s) exécutable(s) écarté(s)" (executable file(s) discarded) — server files (PHP, .htaccess…) found in the archive were not installed, for security.
- "Cegid a refusé la connexion" (Cegid refused the login) / "page Exporter un parcours inaccessible" (Export a course page unavailable) — check the Cegid super administrator account (password, intermediate screen to confirm on Cegid).
- No notification is sent during the migration: no email, no certificate, no automation. Results are migrated as Cegid calculated them.
- Migrated courses are active, even if the publication workflow creates new courses as drafts: otherwise their assignments would be put on hold.
- Restarting is safe: "Start again from the beginning" goes through all the steps again and only fills in what is missing (a newly ticked site, courses added to the selection, answers to questions not yet migrated…).
- Passwords are migrated: at their first login, users enter the one they had on Cegid, and DGTLMS immediately converts it to its own secure format. A Cegid account using LDAP authentication is migrated as LDAP: connect DGTLMS to the same directory before the switchover.
- A file that already exists is never replaced, and a visual already chosen in DGTLMS is kept.
- A module whose files are missing no longer shows a blank page: the learner reads "Content unavailable", and an administrator also sees the cause and the expected path. No result is recorded for that launch.
- Site administrators are not migrated (Cegid does not expose them): appoint them in
Administration → Site managementafter the migration. - An administrator is not enrolled in any session (DGTLMS rule: they see all sessions). As they often belong to no Cegid session, they are only migrated if the Outside sessions box is ticked.
- A learner who had started a module without finishing it will resume it from the beginning: the module's internal progress state (suspend data) is not exposed by Cegid.
- Only the last answer to each question is migrated, not the history of all attempts.
- Cegid custom levels are not recreated.
- An IPv6 address changes regularly: always declare the server's fixed IPv4 address on the Cegid side.