Archiving Models
This article explains how to archive models in Model Reef and when to use archiving as part of your modelling workflow.
You will learn:
What archiving does.
When to archive instead of delete.
How to organise active vs archived models.
How to restore archived models if you need them again.
Archiving helps you keep your workspace tidy without losing important historical work.
What archiving a model means
When you archive a model:
It is removed from your main list of active models and folders.
It is moved into an Archive area in your workspace.
All of its content is preserved, including:
Branch structure.
Variables and drivers.
Data Library entries.
Dashboards and reports.
Notes, tags and attachments.
An archived model is not deleted. It is simply parked out of the way.
When to archive vs delete
Use archiving when:
A project or engagement is finished but you may need to refer back to the model.
A particular version of a model has been superseded but remains an important reference.
You want to keep your active workspace focused on current live models.
Use deletion only when:
A model was created by mistake or is clearly no longer needed.
You have taken any required backups or exports.
You are sure no one else relies on the model.
Archiving is usually the safer default. It preserves history and reduces the risk of accidental loss.
Common archiving workflows
Some typical patterns:
Project completion
When a transaction closes or a project ends, archive the final signed off model.
Keep a lighter operational model active if ongoing monitoring is required.
Yearly planning cycles
At the end of a financial year planning cycle, archive the final approved model.
Use a new model (possibly cloned from the template) for the next year.
Major structure changes
Before making significant structural changes to a live model, duplicate it.
Archive the pre change version as a reference point.
Work in the new version going forward.
Accessing and restoring archived models
To work with an archived model again you can:
Navigate to the Archive section of your workspace.
Open the archived model in read only or editable form, depending on your permissions.
Restore it to the active model list if you want it to reappear alongside current models.
Optionally duplicate the archived model to create a new working copy while keeping the archived snapshot intact.
Restoring does not break any of the model's internal logic. It returns to exactly the state it was in when archived.
Organising archives
For larger workspaces, it helps to:
Adopt naming conventions for archived models, for example appending
(Archived YYYY MM)or similar.Use folders or tags in combination with archiving to indicate client, entity or project.
Periodically review archived models and remove ones that are definitively obsolete (after taking any final backups).
Good archive hygiene keeps your workspace lean while maintaining a strong history.
Archiving templates
You can also archive templates if you retire or replace them:
Archive older template versions once you move to a new standard.
Keep at least one version that represents the structure used for any existing important models, so you can cross reference if needed.
This prevents clutter in your template list and reduces the risk of someone starting a new model from an outdated pattern.
Related articles
Last updated