Deleting Moodle accounts looks like routine offboarding, until the grades and certificates tied to those users suddenly matter again. Many teams treat account removal as a single button, when it is really three separate decisions. Moodle’s own guidance is blunt: deletion is not reversible, and records you meant to keep can vanish with the profile.
For continuing education providers, private schools and professional associations, that lost history can breach a retention rule or fail an audit. So this article gives you a decision framework, not a click path. We will cover when to remove, when to suspend, and what survives each choice. We will also match that cleanup to the records your accreditor expects when deleting Moodle accounts.
What Each Outcome Actually Keeps
| What you are deciding | Delete | Suspend | Archive |
|---|---|---|---|
| Login access | Gone for good | Blocked across the site | Unchanged until you also suspend |
| Grades | Recoverable only by re-enrolling, course by course | Intact and visible in reporting | Preserved in whatever you exported |
| Enrolments, profile, group and cohort membership | Removed and not recoverable | Intact | Intact on the live site |
| Forum posts and assignment files | Remain, with no live account behind them | Remain, still attributed | Remain, plus a copy held outside the site |
| Undo | Partial database repair only | Reversible at any time | Nothing to undo |
This table compares what the platform itself keeps under each outcome, judged for administrators running routine offboarding on a current Moodle release. It does not describe what your own retention policy requires. Archive is not a native account state in Moodle at all: it names an export-then-suspend practice rather than a setting you can switch on.
Suspend by default. Deleting Moodle accounts is the right call only when no retention rule covers the record and nobody will need to read it again. Suspension fits every case where the history still carries institutional value, which is most of them. Archive first whenever the record has to outlive the live site.
I recently migrated my site to Mindfield from another host, and the experience couldn’t have been better. Mindfield kept working until they were certain that my site was operating as well as it was before, and they even helped clean up a few issues to improve my site’s performance – issues my prior host never mentioned. I also found Mindfield’s communication to be excellent. Before the migration, they prepared me for what to expect, and during the migration they kept me well-informed.
Jim Benedek
review Source: Google Reviews
Outline
- Deleting Moodle Accounts: Delete, Suspend or Archive
- What Happens to Grades, Posts and Certificates
- Who Owns an Instructor’s Content After They Leave
- Suspended Learners and Access to Their Own Work
- Matching Cleanup to Your Retention Rules
- Handling Offboarding Cleanup with Expert Support
- Frequently Asked Questions (FAQs)
Deleting Moodle Accounts: Delete, Suspend or Archive
Most offboarding mistakes start by collapsing three outcomes into one “remove the account” decision. In reality, delete, suspend and archive do very different things to a user’s record. Before touching anything, answer the question that should actually drive the choice: whose record is it, and who still needs to read it later? A learner’s completion history often belongs as much to the institution as to the learner, so the answer is rarely “just delete it.”
Deletion Is Permanent and Only Partial
Deletion is not a clean purge and it is not a safety net. It strips some data for good while leaving other data behind under a broken identity. Moodle’s own documentation on managing user accounts is blunt about it: deleting an account results in user data being permanently deleted. Because it cannot be undone from any settings screen, treat it as a last resort rather than a default.
The following are removed and not recoverable once you remove the account:
- Profile details: name, contact fields and custom profile data.
- User preferences: personal settings tied to the login.
- Enrolments: the links that place the user in courses.
- Group and cohort membership: any group-based access or reporting.
By contrast, some data survives but loses its owner. Forum posts stay in their discussions, and files attached to submitted assignments remain in place. However, the username is not preserved; Moodle stores a hashed value in the email field instead.
As a result, a mistaken removal can only be partly repaired by a database-level fix. This is developer work, not an admin toggle.
Suspension Keeps the Record Intact
Suspension is the retain option, and Moodle’s guidance says so directly: if you want to keep any data, suspend the account instead of deleting it. A suspended account cannot log in and cannot use web services. Meanwhile, its data stays intact, and it remains enrolled and visible in course reporting. That makes suspension the safe default whenever a record still has value to the institution.
Archiving Is a Strategy, Not a Button
Archiving is not a native account state, so do not expect a single switch to produce it. Instead, archiving means preserving the record outside active use before you cut access. In practice, teams reuse the same backup and migration strategies for Moodle they rely on for disaster recovery. Others export grade and completion reports, or store issued certificates as files. Therefore, when someone says “archive the account,” clarify whether they mean suspend, export, or both.
What Happens to Grades, Posts and Certificates
The most expensive offboarding surprises involve grades and certificates, because those records outlive the person’s relationship with you. When the account behind them goes, each type of data behaves differently. Knowing the differences up front prevents a support ticket six months later from an alumnus who needs proof of completion.
Grades Are Recoverable, but Only by Hand
Grades are not wiped outright when an account is removed. However, they are not automatically restored either. Recovery is possible by re-enrolling the user into each course and choosing the option to recover their old grades.
That is a manual, per-course action, so recovering a cohort of many learners becomes real staff time. For that reason alone, suspension usually beats removal when grades still matter.
Forum Posts Survive but Lose Attribution
Forum posts remain after deletion, which is good for discussion continuity and bad for attribution. The content stays readable, yet the account behind it no longer exists and the profile details that identified the author are gone for good. Consequently, a thread that once led back to a live contributor now points at a record you cannot restore. For assessed discussions, that change can complicate a later academic integrity or grade review.
Certificates Depend on Where the Record Lives
Certificates are only as durable as the way you stored them. A certificate that exists purely as a live, account-linked record depends on that account still being present. By contrast, a certificate exported as a file survives independently of the login. So does one captured in the kind of Moodle student engagement report you already run. So before removing any account, confirm that proof of completion lives somewhere independent of the user record. An exported file works. So does whatever your Moodle certificate plugin keeps of what it issued.
Who Owns an Instructor’s Content After They Leave
Course content authored by a departing instructor does not leave with them, and that surprises many managers. Course activities and their content belong to the course, not to the teacher’s account. Therefore, deleting Moodle accounts does not delete the courses those accounts built. The complication is attribution, not existence.
The Course Stays; the Credit Shifts
When you remove an instructor’s account, the pages, activities and structure they created stay available to the next teacher. They also travel with the course through a Moodle course copy, backup or restore. However, the artefacts that carry a user id are where attribution changes. In particular, these items lose their clean link to the author:
- Forum posts: announcements and discussion replies the instructor wrote.
- Question bank entries: quiz questions authored under their account.
- Uploaded files: resources tied to their user record.
As a result, the content still works, but its history reads as authored by a missing user. For any course you plan to keep running, suspend the instructor rather than remove them. Hold that position until ownership of these artefacts is reassigned, or until it stops mattering.
Suspended Learners and Access to Their Own Work
Account suspension and enrolment suspension are two different levers, and confusing them causes most access complaints. One controls a single course; the other controls the whole site. Choosing the wrong lever either locks a learner out too broadly or leaves a door open you meant to close.
Two Levers, Two Blast Radiuses
The distinction is simple once named. Suspending an enrolment removes access to that one course, while the account can still log in and reach other courses. Suspending the account blocks login across the entire site. So a learner who finished one program but continues in another should have the enrolment suspended, not the account. Where a whole group has finished, it is often cleaner to reset a course for a cohort than to touch any accounts at all.
What Survives Once Enrolment Ends
A learner’s own work does not disappear when their enrolment ends or their account is suspended. Submissions, posts and grades stay recorded and visible in course reporting. The learner simply loses the ability to reach them through their own login.
Consequently, if a former learner later needs a transcript, your team can still produce it from the intact record. This is exactly why suspension protects both sides.
Matching Cleanup to Your Retention Rules
Operational cleanup and regulatory retention pull in opposite directions, and the account you are tempted to remove is often the one a rule requires you to keep. So the safe sequence is to source the retention requirement first, then decide the technical action. Deleting Moodle accounts before you know the rule is how audits go wrong.
Source the Requirement Before You Touch Anything
Do not guess how long a record must live; confirm it. The obligation almost never comes from the LMS itself. Sector rules drive it instead, much as they do for Moodle compliance for BC private training institutions. Instead, gather it from the people and documents that own the policy:
- The accreditor’s records policy: what your accrediting body requires you to retain.
- The registrar: internal rules on student and completion records.
- Your institution’s retention schedule: the master document that sets timelines.
Once you have those, reconcile them against what Moodle actually keeps. Deletion destroys enrolments and profile data. So a record you are obligated to hold should be suspended or exported, never removed. Leave it that way until its retention window closes. Privacy law pulls the other way, and balancing the two is the same problem that FIPPA, PIPEDA and HIPAA compliance in Moodle turns on.
Use the Governed Deletion Path, Not Ad Hoc Removal
Moodle has a governed privacy workflow that ties removal to defined retention periods, and it is far safer than manual cleanup. In it, a privacy officer defines categories and purposes that each carry a retention period. The system then lists data that is past its period, awaiting approval before anything is deleted. Retention is measured from the course end date for data inside an activity. For a user who is no longer enrolled or already removed, it runs from last login. You can confirm the current behaviour in the official Moodle data privacy documentation before setting policy.
The Defaults Trap With Older Data
One detail catches many teams: retention defaults apply only to newly created instances. Anything created before you set those defaults is not covered by them. Therefore, turning on a retention policy today does not retroactively govern last year’s courses and users.
As a result, historical records still need a deliberate review of their own before you trust a retention policy to cover them.
Handling Offboarding Cleanup with Expert Support
Getting offboarding right means balancing permanent deletion, reversible suspension and regulated retention. That balance is easy to misjudge under time pressure, especially across grades, certificates and instructor content. Mindfield’s Moodle specialists can design the decision framework and configure the governed retention workflow. We handle safe cleanup end to end, so nothing you are obligated to keep is lost. Deleting Moodle accounts at scale is where the mistakes get expensive, so we help you separate the outcomes before anyone touches a live account. Book a free consultation and we will map your retention rules to what your platform actually keeps.
Frequently Asked Questions (FAQs)
This article may contain conceptual illustrations to help support the article content.
