---
id: KB-IN-015
url: https://app.codecontract.io/help/integrations/mirroring-documents-to-your-own-folder
idioma: en
categoria: integraciones
audiencia: administrador
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-IN-002, KB-IN-012]
citadoPor: [KB-IN-001]
---

# Mirroring documents to your own folder

_Also having in SharePoint or Drive what comes in here, without ending up with two archives that disagree._

**Responde a:** sync documents with sharepoint · copy files to google drive · also keep documents in our own folder · mirror documents to onedrive

Many companies want what comes in here to appear in their corporate folder too: because some people work there, because their backups run through it, or simply because they have used that structure for years. It can be done, and it pays to understand exactly what it does and does not do.

## What the mirror does

| Aspect | How it works |
| --- | --- |
| Direction | One way only: from here to your folder |
| Structure | It reproduces the hierarchy: folder, process and document |
| Versions | If the document is already mirrored, it updates that same file rather than creating another |
| When | Immediately, daily or weekly, as you choose |
| Scope | Everything, or only the modules you specify |

> [!IMPORTANT]
> The first row must be crystal clear before setting it up: **it goes one way**. A document someone drops into the SharePoint folder **does not come in here**. If your team starts saving things there assuming they sync, you will have two archives that look alike and disagree, which is worse than having one.

## When it is worth it and when not

**En corto**

- Worth it if some people only work in the corporate folder and will not come in here.
- Worth it if your backup policy requires everything to pass through your own storage.
- Not worth it "just in case": it duplicates without solving anything and costs consumption.
- And it does not replace exporting: taking everything away has its own route.

## What to decide before switching it on

1. **What gets copied** — Everything or one module. Copying what nobody will look at only fills the folder.
2. **How often** — Immediately if someone needs it now; daily or weekly if it is for archiving.
3. **Who wins if something changes in both places** — This platform does, because the copy does not come back. Say it out loud to the team.
4. **And what happens to older material** — The mirror starts when you switch it on; anything earlier is moved separately if needed.

> [!WARNING]
> A detail you only discover once it is running: SharePoint does not accept certain characters in names (`\ / : * ? " < > | # %`), so they are replaced with spaces when copying. The file is the same, but **the name in your folder may not be identical to the one here** — worth knowing if you search there by exact name.

> [!NOTE]
> Each replication is an action and consumes: one per sync request. With "immediate" frequency and high volume, that shows in the breakdown — which is the argument for daily or weekly when the copy is for archiving rather than working.

**Can I work in the copy?**

You can open it, but what you do there does not come back. The original lives here.

**What if I delete something in the corporate folder?**

It is not deleted here. They are two separate places with the same content.

**Does it count as a backup?**

As an additional copy yes; as a recovery plan, review it with whoever owns your policy.

## Ejemplos

**A company switches on the SharePoint mirror and its team starts leaving documents there.**

- Explains to the team that the mirror is one way
- Makes clear new material comes in here and the folder is read-only in practice

→ Documents that exist in the corporate folder but not in the file stop appearing.

**A copy of everything is wanted in the corporate folder and it is done by hand.**

- Configures the automatic copy on approval

→ The folder maintains itself.

**Everything is copied and the folder grows without criteria.**

- Copies only what is approved or final

→ The folder stays usable.

**The copy loses the context of which file it belongs to.**

- Reproduces the file structure when copying

→ It is found equally well in both places.

**The copy is edited and stops matching the original.**

- Treats the copy as an archive, not a workplace

→ The original remains the reference.

**The copy fails for a week and nobody notices.**

- Sets an alert if copying stops

→ The gap is caught before it is needed.