CYBBACK|for Miro
Quick User Guide

Your first Miro backup
in under 10 minutes.

From sign-up to an encrypted, restorable snapshot of your Miro boards - frames, items, connectors, images and documents, with a coverage report that tells you which boards the backup account cannot read.

AudienceMiro admins & IT
Reading time~ 8 minutes
Setup time~ 10 minutes
VersionEN - 2026
What you'll learn

6 steps to a production-ready backup

1
Get started

Sign up - trial or paid plan

Every plan covers every application, Miro included; only the storage changes.

  1. Open cybback.com/essai-gratuit for a 14-day trial (no credit card), or pick a plan on cybback.com/tarifs.
  2. Confirm your e-mail, then open Dashboard → Miro.
2
Connect Miro

Connect a dedicated Miro account

CYBBACK reads Miro with one token per team that backs up and restores, pasted in the Configuration tab like every other application. Use a dedicated account, for example backup-svc, never a person's own account: the connection sees exactly the boards its account can access.

Prepare the account

  1. Create a dedicated Miro account (for example backup-svc@acme.com). It uses a Miro licence.
  2. Enterprise: make it a Company Admin and turn Content Admin on. In Admin Console → Apps and integrations → Apps → Data access, set the backup app to Entire organization (all teams): without it, whole teams can be missing.
  3. Other plans: make it an admin of the team to protect and add it to the spaces and boards to protect. Connect one team at a time.

Connect it to CYBBACK

  1. Signed in to Miro as backup-svc, open Profile settings → Your apps → Create new app. The first time, Miro asks you to create a developer team (Create a dev team) and accept its developer terms. Name the app (for example backup-svc) and leave Expire user authorization token unticked.
  2. In the app, tick the permissions boards:read and boards:write (the same token backs up and restores).
  3. Click Install app and get OAuth token, choose the team to protect, authorize and copy the token. One token per team (the whole organization on Enterprise).
  4. In app.cybback.com/dashboard/miro-backup → Configuration, paste the token, click Validate (team, plan and account shown) then Save. Tokens are encrypted (AES-256-GCM).
app.cybback.com/dashboard/miro-backup
Dashboard
Configuration
Miro configurationEncrypted at rest
Miro token: ••••••••••••
  ✓ acme · Enterprise · 12 teams readable · 1,384 boards
Private boards

Even a Company Admin cannot read the content of a private board that is not shared: it is visible in the list but unreadable. CYBBACK counts and lists these boards in the coverage report; share them with backup-svc to protect them.

3
Scope

Pick what to back up

Incremental forever

A board whose last modification date did not move keeps its previous snapshot; a changed board is read again in full. Each board is a sub-task: one failing board never blocks the others and is retried alone.

Not backed up

Comments, freehand drawings, tables, diagrams and the board version history are not exposed by the Miro REST API.

4
Bring Your Own Bucket

Use your own S3-compatible storage

Want full data sovereignty? Point CYBBACK at your S3-compatible bucket - AWS S3, GCS, Scaleway, OVH, Wasabi, MinIO. Your data, your provider, your region.

  1. In your S3 provider, create a private bucket (no public access, versioning recommended).
  2. Create an access key / secret key with permissions limited to that bucket.
  3. Open Dashboard → Storage, select My own S3 storage, click Test connection, then Save.
5
First backup

Run your first backup and read the coverage report

  1. Back on the Dashboard tab, click Start a backup. A daily schedule is created automatically after the first backup.
  2. Follow the progress live in the history (per-board detail) or on the Events page.
  3. Open the coverage report: boards backed up, boards visible but unreadable, teams that could not be listed, item types the API does not support. Share the missing boards with backup-svc or fix the data access setting, then run the backup again.
Lost access is not a deletion

A board that becomes unreadable keeps its previous snapshot and is flagged; only a board that has really disappeared from Miro goes to the CYBBACK recycle bin.

6
Restore

Restore - board, frame or items

  1. Selection. Browse the boards by team, open a board to see its frames and items, tick the whole board, a frame or some items. Show the recycle bin to see deleted boards and removed items.
  2. Options. Dry run (on by default), destination (a new board, or an existing board for a frame or items), files, tags, connectors, groups, markers for items that cannot be restored, members (option).
  3. Execution. The worker recreates frames first, then items in their positions, files, connectors, tags and groups, and logs every step. You can cancel; a re-run never duplicates and nothing is ever deleted on the target board.
Dashboard → Miro → Restore
1. Selection
2. Options
3. Execution
Restore options1 board · 14 frames · 1,240 items
Dry runNothing is written to Miro
 
What cannot be restored identically

Restored items get new identifiers and the board a new URL; author and dates are those of the restore account. Some styles are not exposed by the API (sticky note font, shape text colour). Mind maps and unknown item types become a neutral marker at their position. Images and documents above about 6 MB may be refused by Miro. Comments, drawings, tables and diagrams are not available through the API.

You're all set.

Need help? Our team replies within one business day on every plan.

Contact support →