# Move a document to the right folder when its type is changed

When someone re-classifies a document into this type, it lands in this type's folder automatically — a Content DocType Change trigger and a Move to Folder action — so a fixed classification never leaves a misfiled document behind.

Product: content-central · Versions: 7.8+ · Audience: catalog-administrator · Time: 10 minutes · Last verified: 2026-09-05

Canonical: https://help.ademero.com/content-central/workflow/move-a-document-when-its-type-changes

**When you're done, a document that someone changes into this document type moves itself into this type's folder, so a corrected classification also corrects the filing.**

```plan
scope: document-type
trigger: Content DocType Change › Changed to this Document Type | Any user
action: Content - Move to Folder | Folder Path: this type's folder
rule: "Changed to this type → move to its folder", enabled
```

Changing a document's type updates its fields and rules, but the file stays wherever it was filed under the *old* type. This rule finishes the job.

## Build the trigger

1. Go to **Administration** > **Catalogs & Document Types**, pick the **Catalog** and the *destination* **Document Type** (the one documents are being changed *into*), click the **Workflow** tile, then **Triggers** > **New Trigger**.

2. **Type:** `Content DocType Change` and `Changed to this Document Type`. **Trigger Name:** `Re-classified into this type`.

3. Click **Save**.

**What you should see:** a Live trigger. It fires for every document whose type is changed to this one, from any other type.

## Build the action

1. Click **Actions** > **New Action**.

2. **Type:** `Content - Move to Folder`. **Action Name:** `Move to this type's folder`.

3. Under **Folder Path**, use **Select a subfolder…** (and **Move Up**) until the displayed path is the folder this type belongs in. Click **Save**.

## Wire the rule

1. Click **Rules** > **New Rule**. **Rule Name:** `Changed to this type → move to its folder`.

2. **Add Trigger:** `Re-classified into this type`. **Add Action:** `Move to this type's folder`. **Apply**.

## Test it

1. Pick a test document of a *different* type in the same catalog and change its document type to this one.

2. Browse to the destination folder.

**What you should see:** the document now in the destination folder, with **View History** showing the type change followed by the workflow move. If the change was blocked before it happened, that's permissions, not workflow — see the linked guide on changing types.

## Variations

| Want this instead | Change this |
| --- | --- |
| Catch changes *out of* a type (to clean up the old folder) | There's no "changed from" sub-type; put this rule on every destination type instead |
| Move to a folder based on a field value | Add a trigger per value under **Use Multiple Triggers** with `AND`, or split into one rule per value |
| Start this type's approval after re-classification | Add **Approval Process - Start Process** — type changes don't start a process on their own |
| Copy instead of move | Action **Content - Copy to Folder** |
| React to catalog-wide changes | Build it at the catalog scope: sub-type `Document-Type Change in a Catalog` |

## What's next

- [Change a document's type, catalog, or fields after filing](https://help.ademero.com/content-central/documents/change-a-document-after-filing)
- [When an invoice is marked Paid, clear it from queues and file it](https://help.ademero.com/content-central/workflow/clear-paid-invoices-from-queues-and-file-them)