Migration Guides
From PlanSwift, Bluebeam, STACK, OST.
Step-by-step migration playbooks for the four most-common incumbents. What carries over, what needs rebuilding, parallel-run protocol, and how long it really takes.
Per-vendor guides
4 migration paths
Migrating from PlanSwift to OmniTakeoff
low difficulty2–3 weeks
Data portability
PlanSwift exports CSV from its takeoff workspace. We provide an importer that maps PlanSwift's standard schema to OmniTakeoff line items.
What carries over- Historical takeoff line items (CSV import)
- Assembly database (with mapping spreadsheet — we provide the template)
- Project-level metadata (project name, address, sheet metadata)
- Symbol library mappings via our PlanSwift symbol export tool
What needs rebuilding- Symbol-library training is org-specific; the recognizer ramps over the first weeks of active learning on your sheets (specific accuracy curves shared under NDA)
- Custom report templates need rebuilding in our proposal editor (CSM time is bundled to assist)
- Plugin-based AI auto-counts (e.g., third-party Symbio integration) do not transfer — but native AI is included
Request the PlanSwift migration kitParallel-run protocol
Run PlanSwift + OmniTakeoff in parallel for the first 2 bids to validate quantity outputs against your team's manual counts. By bid 3, customers typically retire PlanSwift for new bids while keeping it available for read-only access to historical projects.
Migrating from Bluebeam Revu to OmniTakeoff
medium difficulty3–4 weeks
Data portability
Bluebeam stores measurement data in PDF annotations + Studio session metadata. We extract takeoff data via our Bluebeam markup importer (PDF-by-PDF).
What carries over- PDF measurement annotations imported as takeoff lines
- Studio session participants (mapped to OmniTakeoff users)
- Markup tool customizations rebuilt as OmniTakeoff symbol-library entries
- Project drawings imported directly
What needs rebuilding- Bluebeam users tend to have heavy custom toolchests — we provide a worksheet to map each tool to a symbol-library entry
- Legends + custom title-block stamps require manual rebuild (typical: 2–4 hours per stamp set)
- Bluebeam Studio collaboration model differs from our review-queue model; teams typically prefer the queue after 1 week
Request the Bluebeam migration kitParallel-run protocol
Bluebeam migration is the most workflow-impactful because users have years of muscle memory in the Markup panel. We recommend running Bluebeam read-only for the first 30 days while OmniTakeoff handles new takeoffs. Most customers fully migrate within 6 weeks.
Migrating from STACK to OmniTakeoff
low difficulty2 weeks
Data portability
STACK exports a structured project archive (XML + binary asset bundle). We import the full archive including assembly definitions.
What carries over- STACK projects (full takeoff history + assemblies)
- Assembly database mapped to our pricing system
- Drawings + sheets
- User accounts and project permissions
What needs rebuilding- STACK's auto-count rules don't transfer; recognizer training is org-specific
- Custom report templates rebuild in our proposal editor
- Workflow status definitions differ — we provide a mapping table during onboarding
Request the STACK migration kitParallel-run protocol
STACK migrations are typically clean because both platforms are cloud-native with similar data models. Most customers parallel-run for 1 week, then cut over fully.
Migrating from On-Screen Takeoff (OST) to OmniTakeoff
medium difficulty3 weeks
Data portability
OST stores projects in a proprietary format. We extract via OST's Excel export endpoint and a tab-delimited audit-trail dump.
What carries over- Project history via Excel export
- Sheet metadata + drawing files
- Audit-trail records (read-only archive)
- Quantity counts mapped to our line-item schema
What needs rebuilding- OST Style libraries (the OST equivalent of symbol libraries) require manual mapping
- OST Pages → OmniTakeoff sheets is a 1:1 mapping but assembly logic differs
- OST report templates do not transfer; rebuild in our proposal editor
Request the OST migration kitParallel-run protocol
OST customers tend to have very long historical archives. We import the historical archive read-only and run OmniTakeoff on net-new projects starting day 1. After 30 days, customers typically retire OST entirely.
What every migration includes
Bundled with onboarding, no extra fee
Migration specialist
A named migration specialist for the duration of the cutover. Slack channel + weekly check-in until you sign off on parallel-run results.
Data import + validation
We'll do the data import. You'll review a parallel-run report comparing OmniTakeoff output to your incumbent's output, line-by-line, on 2 historical bids you choose.
Team training
Live sessions for your estimators (90 min × 2). Recorded for replay. Custom training available on Enterprise.
Migrating from something else?
Custom migrations on request.
If your team is on Excel, ProEst, eTakeoff, Sage Estimating, or a homegrown system — we've migrated from all of them. Email us with your current tooling and we'll send a custom plan.