DGTLMS & LMSDISPATCHER Guide

Administration

Migrate a 360Learning platform to DGTLMS

Taking over a 360Learning platform — users, groups, paths, sessions, enrolments and results — is available on request, after a study of your project with the DGTCONCEPT team.

Administrator, decision-maker30-minute appointment to study the projectAdvanced

What it is for

You are moving from 360Learning to DGTLMS and want to keep your learners, the organisation of your courses and their history. The migration reads your platform through the official 360Learning API, read-only, and recreates this data in DGTLMS, with no duplicates. It can be run again as many times as needed until the switchover.

It is available on request: the share of your courses built in the 360Learning editor makes a big difference to the work involved (see « Warning »). We therefore study your platform with you first.

  • Book an appointment at calendly.com/dgtconcept to study your data migration project.
  • Ask an administrator of your 360Learning platform to create API v2 credentials (API administration panel) with read-only rights: users, groups, courses, paths, statistics.
  • If possible, identify the courses imported as SCORM into 360Learning and locate their original SCORM files (.zip).
  • Know how your users log in: 360Learning password or SSO (Microsoft Entra ID, Google, Okta…).

Steps

  1. Study the project

    During the appointment, we review your platform: volumes, how groups are organised, course types, sessions, and how users log in.

  2. Take the inventory

    A first read through the API, with no writes at all, counts what will be taken over: users, groups, paths, courses by type, sessions, enrolments and statistics. You approve the list of paths to take over.

  3. Take over the content

    SCORM courses are installed from your original files; courses built in the 360Learning editor are rebuilt using the approach agreed during the study.

  4. Run a trial migration

    The migration is first carried out on a DGTLMS staging platform: you check your courses, your accounts and the results of a few learners.

  5. Switch over

    A final run picks up whatever changed on 360Learning since the trial, and your users then log in to DGTLMS.

What is taken over

360LearningDGTLMS
UsersAccounts: email, username, last name, first name, language, status, job title, organisation, managers
Groups (and sub-groups)Groups or sites, depending on your organisation
Paths and their stepsCourses and their modules, in path order
Path sessionsSessions: name, dates, instructors
EnrolmentsSession enrolments
Path statisticsResults per course and per session: status, score, progress, time spent, dates
Course statisticsResults per module, attempt by attempt
Classrooms (face-to-face, virtual classroom)Slots, registrations and attendance
Tags and custom fieldsTopics and custom fields
Certificates earnedLearners' PDF certificates
  • The migration only uses read rights: it never changes your 360Learning platform.
  • If your users log in through SSO, connect DGTLMS to the same identity provider: the switchover is seamless for them.
  • No notifications are sent during the migration: no emails, no certificates.
  • Course content is not provided by the 360Learning API, only its description (title, duration, authors, languages). Courses imported as SCORM are taken over from your original files; courses built in the 360Learning editor have to be rebuilt in DGTLMS (DGT Studio, AI-assisted creation from your documents…). The preliminary study estimates this work.
  • Passwords are not provided by 360Learning: without SSO, each user receives a link to set their DGTLMS password at switchover.
  • Detailed answers to questions are not provided: the history taken over is the status, score, progress and time spent for each attempt.

See also