Skip to content

Operations & Administration (Control)

Move to Universe

ForAdministrationOperator

Take over users and their complete history from the previous system — people, roles, courses, enrolments, results with grades and ECTS, credentials and learning history. First a dry run with a check report, then the move in batches; every run can be undone.

Why#

A switch rarely fails because of the new platform, but because of the move: thousands of accounts, years of grades, credentials that must stay valid. The move reads the old system's exports or open exchange formats, checks everything in advance and only writes once the report is right — even with millions of records.

How it works#

Click pathAdministrationMove to Universe

  1. 1Administration: open “Move to Universe” (address /admin/migration).
  2. 2Under “New move” enter a name for the source (e.g. lms-old), the system or format and the purpose in one sentence, then “Create move”.
  3. 3Step 1: upload the export (CSV, spreadsheet, ZIP, course backup, XML or JSON) — or, for an interface, enter its URL and an access token and “Fetch”. The token is not stored.
  4. 4Step 2 (only for any table): “Suggest mapping” — the assistant maps the columns to the fields; check, correct and “Confirm mapping”.
  5. 5Step 3: “Start dry run”. The check report shows per content type how much was read, what is valid, errors with file and line, duplicates, duplicate email addresses and references into nowhere. Nothing is written.
  6. 6Step 4: “Start move”. The run writes in batches and shows its progress; faulty records are only skipped after explicit confirmation.
  7. 7Step 5: “Take over” — people with an email get an account in your own organisation (or are matched to the existing one), results go into the achievement archive with grade and ECTS.
  8. 8Step 6: after weeks of parallel operation, “Compare with source” using a fresh export; if needed “Undo” or “Delete source files now”. The log shows every step.

Settings and switches#

  • Switchable per tenantDefault: onModule: Schnittstellen
  • Per move: type “Move” or “Comparison after the move”; for a comparison, optionally mark records that are no longer in the source — nothing is ever deleted that way.
  • On take-over: “Create missing accounts” and “Take over results” can be chosen separately.
  • A quick dry run for small exports (up to 4 MB per file) checks immediately and stores nothing.

What moves#

  • People with name, email, username, student and staff number — and their roles and organisational units.
  • Degree programmes, modules and courses with term, enrolments with status and period.
  • Exams and results with grade, points, ECTS, examiner and date.
  • Credentials and badges — the original is kept unchanged so that a signature of the old issuer stays verifiable.
  • Learning history (completed, passed, score, duration) and references to files such as term papers.

Which formats#

  • Own templates: CSV or spreadsheet, one file or sheet per content type.
  • Any table with the mapping assistant — the route for reports from campus management and HR systems.
  • Open standards: SCIM 2.0, OneRoster 1.2 (CSV and interface), xAPI and cmi5, SCORM learning records, Open Badges 2.0 and 3.0, Europass credentials, ELMO achievement records, LDAP exports (LDIF).
  • Course backups and database exports of common learning platforms.

What the move promises#

  • Repeatable: every record is unique by source, content type and identifier; unchanged records are not written.
  • In batches and resumable: if a run stops, it continues with the next batch — even without an open window.
  • Reversible: new records are removed, changed ones reset to their previous state, taken-over results deleted; the most recent run of a source is always undone first.
  • Measured: one million records checked in about 21 seconds and written in about 29 seconds in 1000 batches (without the database path, test machine).

Data protection#

  • Every move states its purpose; it is recorded in the log.
  • Uploaded exports are kept in private storage in the EU and deleted 7 days after completion, at the latest 30 days after upload — immediately on request.
  • Access tokens for interfaces are not stored.

Who may do what#

A customer's administration only moves data into its own organisation and only sees its own moves. Accounts are matched by email address only within the organisation; if an address belongs to an account outside it, it is not taken over. On the main address the operator chooses the organisation.

Tips#

  • A source is one installation of the old system. Use the same name for later comparisons — that is how the move recognises what is new and what has changed.
  • Importing the same export twice changes nothing the second time.
  • For any other system: put the data into the columns of the templates (download on the page) and upload as Universe template.

Related features#