By Tyler E. · 9 July 2026
Migrating off Bluebeam Revu 20: the practical checklist
Revu 20 support ends July 31, 2026 and Studio access ends December 31. Here's the migration itself: what to do before each date, where every Revu habit lands in a browser-based tool, and what genuinely has no replacement.
If you're leaving Bluebeam Revu 20, the migration itself takes an afternoon — the expensive part is leaving it too late. Do two things before July 31, 2026: complete any planned hardware moves while self-service seat release still works, and start a two-week trial of your replacement now, so the decision happens on a real job instead of against a deadline. After July 31 there are no support tickets and no seat moves; after December 31, Revu 20 loses Studio Sessions, Studio Projects, and API access for good. (The full breakdown of the dates and the three-year cost of each option is in what Revu 20 end of support actually means — this post is about the move itself.)
Before July 31: the pre-migration checklist
- Move seats first. If any machine running Revu 20 might be replaced in the next few years, do the license move now. Seat release stops being self-service at end of support, and this is the item that quietly strands people six months later.
- Export what lives inside Revu. Custom tool chests, profiles, and stamp sets exist on your machine, not in your PDFs. If you're staying on Revu 20 offline, back them up; if you're leaving, screenshot or list them — they're the checklist for rebuilding your markup kit in whatever comes next.
- Flatten and file your record sets. Marked-up PDFs you've already issued are fine — they're just PDFs. But any live, unflattened markup rounds you might need to stand behind later are worth flattening to a record copy while you still have a supported tool.
- List your Studio dependencies. Sessions you host are replaceable. Sessions you join — a GC's coordination round, for example — are not: joining Studio always requires a supported Revu seat, whatever else you switch to.
Where each Revu habit lands
The workflow most contractors actually run in Revu — open the drawing, mark it up, measure, count, send a clean PDF back — maps directly to a browser-based tool. Here's the honest translation table for ContractorCounter:
| Revu habit | Where it lands |
|---|---|
| Everyday markup (callouts, arrows, text, highlights, clouds) | Same tools, in the browser — nothing to relearn |
| Tool chests of repeated markups | Stamps for repeated marks; the deep tool-chest system has no full equivalent |
| Calibrate and measure | Calibrate the scale once per sheet, then lengths, areas, and volumes read from it |
| Counts | Symbol counts that stay grouped as the drawing evolves |
| Markups list | Measurements and counts feed a live Bill of Quantities that flows into a quote — a step Revu hands to separate estimating software |
| Studio sessions you host | Workspace sharing: invite by email or link, live cursors, no session administration |
| Studio sessions you join | No substitute — a supported Revu seat (Basics, US$260/yr) is the only ticket into someone else's Studio |
| Advanced PDF editing, document standards | Keep Revu — this is genuinely its territory |
The pattern in that table is the honest test for whether to migrate at all: if your last month of Revu work happened in the first six rows, a lighter tool covers you. If it happened in the last two, subscribe to Revu 21 and stop reading migration guides.
The first week in the new tool
Run the trial like a real job, not a demo. Upload the current job's drawings, calibrate each sheet once, and rebuild your five most-used markups as stamps — that's the whole setup. Then put one live markup round through it end to end: mark up, measure, count, export the PDF, and send it to someone who was expecting a Revu file. If the round survives contact with a real recipient, the migration works; if you hit something Revu did that the browser doesn't, you've found it for the price of a trial instead of a license. ContractorCounter's 14-day trial needs no card, and the line-by-line comparison against Revu covers price, platforms, and the three-year math if you're building the business case.
The questions that come up mid-migration
Do my old marked-up PDFs still work? Yes — markups saved into a PDF are part of the file. Any PDF tool opens them; your archive is safe regardless of what you switch to.
Can I run Revu 20 and the new tool side by side? That's the recommended way to migrate: keep Revu 20 for in-flight jobs, start new jobs in the new tool, and let the overlap retire itself. Just remember the July 31 seat-move deadline applies even during the overlap.
What about the jobs where a GC requires Studio? Budget for one supported Revu seat (Basics) as the entry ticket, and do the rest of your work wherever it's cheapest. Several subs run exactly this split after end of life.
Is there anything to import? No migration wizard exists in either direction — but for markup work there's nothing to import: your drawings are PDFs, and your kit is a handful of stamps you rebuild in minutes. The only real rebuild is habits, which is what the two-week parallel run is for.
Dates and Bluebeam pricing per Bluebeam's official Revu 20 EOL notice, verified July 2026; see the end-of-support explainer for the full timeline. ContractorCounter pricing current as of July 2026.