---
title: Archive a module
description: >-
  Retire modules from day-to-day use without deleting versions or history, and
  understand the impact on selectors, curricula, and linked courses.
sidebar:
  order: 6
  hidden: true
---

Archiving retires a module from day-to-day use without deleting its data. Archived modules can be restored later if needed. Use archive when a unit of study is no longer offered as an active catalog entry — not when you only need a revised configuration for the same unit (prefer a [new version](/docs/fuxam-web/cms/academic-structure/modules/manage-module-versions) in that case).

:::warning
Archiving hides a module from default lists and selectors. Existing curriculum items, cohort study plans, linked courses, and enrollments that already reference it are **not** removed automatically. Review dependencies first.
:::

## Why it matters

Academic catalogs accumulate modules that programs no longer run. Leaving them active clutters selectors for curriculum editors, planners, and staff linking courses. Archiving reduces that noise while preserving the historical record: versions, past curriculum references, and configuration remain available for audit and restoration.

Unlike permanent deletion, archive is designed for institutions that must retain academic history. Students and cohorts that already referenced a module version are not automatically stripped of those references when you archive.

## Archive vs. delete vs. version

Fuxam supports **Archive** for modules — not permanent deletion from the Modules table. Archiving:

- Hides the module from default module lists and selectors.
- Preserves all versions, historical links, and configuration data.
- Can be reversed with **Unarchive**.

| Goal | Prefer |
|---|---|
| Stop offering the module entirely | **Archive** after reviewing dependencies |
| Change ECTS or exams for a future year | [Create a new version](/docs/fuxam-web/cms/academic-structure/modules/manage-module-versions) |
| Replace with a differently coded unit of study | [Create a module](/docs/fuxam-web/cms/academic-structure/modules/create-a-module), migrate curricula, then archive the old one |

## Before you start

- Search curricula and planning for the module (and its versions) still in active use.
- Decide whether a replacement module or a new version is needed first.
- Communicate the retirement to program coordinators and planners who may still select it.
- Confirm whether any [module group](/docs/fuxam-web/cms/academic-structure/modules/module-groups) membership should be updated so catalogs stay accurate.

## Archive a module

1. Go to **Campus Management → Database → Modules**.

2. Select one or more modules using the row checkboxes.

3. Open the selection actions menu and choose **Archive**.

4. Confirm the action. Fuxam marks the selected modules as archived.

Fuxam prompts: archived modules will not be visible to users, and you can unarchive them later.

## View archived modules

Use the archived filter on the Modules table to include archived modules in the list. From there you can review retired modules or select **Unarchive** to make them active again.

## Worked example — retire after replacement

**Scenario:** `Legacy Statistics` (`STAT100`) is replaced by `Statistics for Social Sciences` (`STAT110`) with a new code and handbook entry.

1. Create and configure `STAT110` (versions, ECTS, exams).
2. Place `STAT110` in the new curriculum version; keep older cohorts on `STAT100` until they finish.
3. When no active curriculum needs `STAT100` for *new* placements, archive `STAT100`.
4. Historical study plans that still reference `STAT100` versions remain for audit; the module no longer appears in default selectors.

Do **not** archive `STAT100` merely because ECTS changed from 5 to 6 — that is a [versioning](/docs/fuxam-web/cms/academic-structure/modules/manage-module-versions) case on the same module.

## Best practices

- Archive only after curricula and planning no longer need the module for *new* placements — even though existing references remain.
- Prefer versioning over archiving when the academic unit continues under a new configuration.
- Keep a short internal note of why a module was archived (program closure, merge into another code, and so on) for future staff.
- After archiving, verify that default module lists and selectors no longer offer the retired entry to casual pickers.
- Coordinate with staff who maintain [module groups](/docs/fuxam-web/cms/academic-structure/modules/module-groups) so retired modules do not linger in organizational groupings that look "current."

## Common pitfalls

- Archiving a module that is still the only placement in an active curriculum version — students and planners may still depend on those references even though the module is hidden from default lists.
- Archiving instead of versioning when you only meant to retire an old ECTS configuration.
- Forgetting that **Unarchive** restores visibility — use it when a program is reactivated, not as a substitute for careful dependency review at archive time.
- Assuming linked courses or curriculum rows disappear on archive — they do not.

## FAQ

**Does archiving delete versions and links?**

No. Archiving preserves all versions, historical links, and configuration data. It hides the module from default lists and selectors.

**Are enrollments and curriculum items removed?**

No. Existing curriculum items, cohort study plans, linked courses, and student enrollments that already reference the module or its versions are not automatically removed.

**Can I undo an archive?**

Yes. Use the archived filter on the Modules table, select the module, and choose **Unarchive**.

**Should I archive or create a new version?**

Create a new version when the unit of study continues with updated settings. Archive when the module should leave the active catalog entirely.

## Related pages

**[Create a module](/docs/fuxam-web/cms/academic-structure/modules/create-a-module)**

Add a replacement module before archiving an outdated one.

**[Manage module versions](/docs/fuxam-web/cms/academic-structure/modules/manage-module-versions)**

Create a new version instead of archiving when only configuration changed.

**[Add modules to curriculum](/docs/fuxam-web/cms/academic-structure/curricula/add-modules-to-curriculum)**

Verify curriculum dependencies before archiving.

**[Modules overview](/docs/fuxam-web/cms/academic-structure/modules)**

Catalog concepts and related Database workflows.
