Running on Miro?

Miro boards sluggish or API throttling? We sort it out.

Miro is fine when a team is sketching. It starts to creak when a strategic board has eight thousand sticky notes, an app build hits the REST API ceiling halfway through a migration, or an SSO reconfiguration logs everyone out of their templates. We split the boards, back off the rate limits, and fix the integration that was quietly dropping objects on the way across.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

miro-import.log

still failing

What it is

Miro at a glance

Miro is a collaborative online whiteboard launched in 2011 by Andrey Khusid and Oleg Shardin, originally as RealtimeBoard. It renamed to Miro in 2019 and grew into the de facto digital whiteboard for product teams, running workshops, retrospectives, roadmaps, journey maps and architecture sketches across remote and hybrid teams.

The platform offers boards, templates, frames, sticky notes, connectors, voting, timers, embeds and a REST API with OAuth 2.0 and SDKs for custom apps. It supports SAML SSO, SCIM provisioning, Enterprise Guard for data loss prevention, and integrations with Jira, Confluence, Azure DevOps, Asana, Monday.com and many others. The friction we see is usually around three things: boards that have grown beyond what a browser session can hold, API rate limits hitting imports or bulk migrations, and SSO or SCIM configuration that stops provisioning accounts cleanly after a tenant or identity provider change.

Type
Online collaborative whiteboard platform
First released
2011, as RealtimeBoard
License
Proprietary SaaS, per-editor pricing with Free, Starter, Business and Enterprise tiers
Maintained by
Miro (RealtimeBoard, Inc.)
Typically used for
Workshops, retrospectives, journey maps, roadmaps, architecture diagrams, UX research synthesis

The honest version

Miro pros and cons

No technology is all upside. This is where Miro earns its place and where it tends to cause trouble.

Where Miro is strong

  • Real-time collaboration at scaleDozens of people can edit the same board simultaneously, with cursors, avatars and voice built in, and the experience holds up on video calls without screen-share lag.
  • A huge template libraryRetrospectives, journey maps, SWOT, lean canvas, story maps and dozens more templates ship with the product and from the community, so a workshop can start in minutes rather than hours.
  • Decent integrations with the rest of the stackJira cards, Confluence pages, Azure DevOps work items and Asana tasks can be synced to board items, so a workshop output can land in the tracker without re-keying.
  • A proper developer platformREST API, OAuth 2.0, Web SDK and server-side SDKs mean custom apps can read, write and extend boards for enterprise workflows that need automation.
  • Enterprise controls when you need themSAML SSO, SCIM provisioning, audit logs, data residency and Enterprise Guard let security and IT accept the platform in regulated environments.
  • Works well with async teamsMentions, comments, video threads and timed activities turn a board into something that keeps running after the workshop closes.

Where Miro bites

  • Board size limits bite real teamsA board over ten thousand widgets refuses to duplicate, slows to a crawl, and eventually loses WebSocket connections. The limit is a soft fact of life once an organisation uses Miro seriously.
  • Pricing climbs with editor countPer-editor seats add up fast, especially when half the organisation only touches a board once a quarter but is billed as an editor because they moved a sticky.
  • API rate limits throttle bulk workThe REST API caps requests per minute, which turns a full-content migration into a weekend job rather than an evening one, and surfaces as 429s partway through.
  • Offline is not a featureA dropped connection in the middle of a workshop loses pending edits, and Miro has no meaningful offline mode. Running a workshop on poor connectivity is a bad bet.
  • Exports are not a design systemA PNG or a PDF of a board is a snapshot, not a document, and organisations that treat Miro exports as source of truth find them out of date by the time they are shared.
  • SSO and SCIM edge cases catch Enterprise teamsTenant migrations, identity provider switches and group renames routinely break provisioning, and the recovery path is support-ticket speed rather than self-service.

Sound familiar?

Common Miro problems we fix

The Miro problems that bring people to us, and what you have once each one is fixed.

429 rate limit exceeded

A bulk migration into Miro throttles out

An import script hitting /v2/boards item endpoints at the full-speed default, with no exponential backoff and no per-minute budget. The job fails halfway through, leaving a half-populated board and no clear resume point.

Import respects limits, resumable

board exceeds the maximum of 10000 widgets

A strategic board is too large to duplicate

Years of workshops accumulating in one board, with ghost frames, duplicate stickies and connectors that nobody has pruned. Miro refuses to duplicate it for archival, and performance has already degraded.

Boards split, archive clean

SAML response signature invalid

SSO stops working after an identity provider change

A certificate rotation on Okta or Azure AD that was not reflected in Miro's SSO settings, or a tenant alias that changed and now mismatches the SAML audience value.

SSO signed, users log in cleanly

SCIM: user provisioning deferred

Users in the IdP are not appearing in Miro

Group mappings that do not match on the Miro side, SCIM filter attributes that were renamed, or a SCIM token that expired after a rotation. New hires wait days for access.

SCIM provisioning on schedule

OAuth token expired or revoked

A Miro app stops working in production

An OAuth token that was never refreshed because the app skipped the refresh flow, or a token that was revoked when a user disconnected the app for a moment. Automations fail silently.

OAuth refresh handled

export failed: image larger than 25 MB

Board export hits the file size cap

An attempt to export a very large board as a single PNG or PDF, exceeding the 25 MB limit. The common workaround, exporting per frame, needs scripting rather than a right-click.

Exports split, automated

parent frame does not exist on this board

Template or board migration drops items

A migration that moves items to a new board but creates child items before their parent frames exist, so the API rejects the write. Items end up detached or missing.

Migration ordered correctly

WebSocket disconnected unexpectedly

Workshop participants keep dropping out

Corporate VPNs that interfere with long-lived WebSocket sessions, or browser tabs that suspend after being hidden during a video call. Edits made just before the drop are lost.

Session stable, autosave verified

What we do

Miro help, board to integration

Call us for one failing workshop, or let us own the whole Miro integration layer.

Rescue
A board that will not duplicate, an SSO path that locked everyone out, or an import job that is 429ing. We get people back into the board first and explain the cause second.
Board architecture
Breaking oversized boards into linked, right-sized ones, pruning ghost items, and setting a convention for frames and tags that keeps new boards sustainable.
API and app development
REST and Web SDK integrations that respect rate limits, handle OAuth refresh properly, and survive retries. Custom panels, embeds and workflow triggers delivered end to end.
SSO and SCIM
SAML configuration against Okta, Azure AD or Google Workspace, with group mapping, SCIM provisioning and the tenant edge cases Miro's docs do not spell out.
Migrations
Moving content from Mural, Lucidspark, FigJam or legacy whiteboards into Miro, with templates recreated and workshops tested before team rollout.
Managed Tech
Monitoring on app installations, quarterly board hygiene reviews, SSO certificate rotation reminders, and an engineer on call when the Developer Platform changes an endpoint.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Miro alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Miro questions

Something else? Call+1 737 727 7327

Why is our Miro board getting slow and refusing to duplicate?

You are probably past the practical limit on widget count. Boards with many thousands of items become slow in the browser and eventually hit the duplicate cap. The fix is architectural rather than a setting change: we split the board into linked ones along meaningful boundaries (per quarter, per workstream), archive stale content, and set a convention for when to spin up a new board instead of growing the current one.

How do we avoid hitting Miro API rate limits on imports?

By building the importer with backoff rather than retry-on-429, batching writes under the per-minute budget, and making every request idempotent so a retry does not duplicate items. For large migrations we also split the import into phases (frames first, items next, connectors last) so a failure does not leave orphaned items.

Why did Miro SSO stop working after we changed identity providers?

SAML needs the signing certificate, the entity ID, the ACS URL and the audience value to all match. A move from one IdP to another, or a renewed certificate, breaks at least one of those. We re-upload the current metadata, verify the SAML response signature against the new certificate, and test with a sample account before switching the team.

Can we build a custom Miro app for our internal workflow?

Yes. The Developer Platform supports server-side apps that read and write boards through the REST API, as well as Web SDK apps that run inside the board itself as panels and modals. Common patterns include syncing board items to Jira or Linear, injecting templates from an internal library, and automating workshop output into a document system. We design, build, publish through the Marketplace or install privately, and maintain them.

How do we migrate from Mural, Lucidspark or FigJam to Miro?

There is no one-click importer, so migrations are a mix of template recreation, selective content export (to CSV or image) and manual recreation of critical boards. For big moves, we build a small import pipeline that reads the source format where one exists and writes to Miro through the REST API, and we run a workshop with the team on the new platform before switching defaults.

How much does Miro help cost?

The quote is free. Send a short note describing the board, the plan tier and what is going wrong, and we return a scope and a price before any engineer logs into your workspace.

Free estimate

Miro giving you trouble?

Oversized boards, failing imports, SSO reconfigurations and custom Developer Platform apps. We work on the whole workspace, not just a single board.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.