Migrating from PlanSwift to CivilTakeoff
A PlanSwift migration to CivilTakeoff starts with reusing the original plan PDFs, preparing an item-library CSV, and retaining exported quantity records. Recreate measurements and condition setup in CivilTakeoff.
What you can reuse
- Plan PDFs upload directly. Use the original issued files with their revision information.
- Item and pay-item lists can be prepared from a report export and mapped to the CSV code, description, and unit columns.
- Completed takeoff records exported to Excel serve as reference records.
- Your conventions: names, codes, and colors can be recreated in your condition setup.
What needs rebuilding
- Takeoff geometry. PlanSwift polygons and measurements do not import as editable CivilTakeoff geometry. Recreate the measurements you need.
- Assemblies and cost logic. Recreate the relevant item attachments and formulas manually.
- Plugins and PlanSwift templates. Rebuild the needed workflow using CivilTakeoff’s available tools.
Migration steps
- 1
Choose a comparison project
Use a small representative project with an area, a length, counts, and an alternate. Keep an active bid in its established workflow while you test the new setup.
- 2
Prepare the item library
Export a PlanSwift report containing the item data you need. Clean up codes, descriptions, and units in a spreadsheet, then prepare a CSV that matches CivilTakeoff’s code, description, and unit columns. Correct any mismatched columns in the imported rows.
- 3
Upload the original plan PDFs
Use the issued PDF set with its revision information. CivilTakeoff detects sheet names and scale. Calibrate each sheet against a known dimension.
- 4
Recreate conditions
Rebuild the conditions, attached items, and conversions needed for the sample scope. Measure the plans, adjust automatic area boundaries to match the scope, and compare quantities with the reference takeoff.
- 5
Compare exports and retain the archive
Export XLSX and match its item codes, units, totals, and bid groups to your estimating spreadsheet. Retain the PlanSwift jobs and reports needed for historical review.
Plan the setup work
The amount of work depends on the item library, conditions, and spreadsheet connections you use. Start with one representative scope and record the time needed to recreate it and compare quantities. Use that result to plan the remaining setup and decide when to move new bids. Retain archive access for the jobs you still need to review.
Migration questions
- Can I still use my old takeoffs?
- Keep the original PlanSwift jobs and the environment needed to open them, plus exported Excel or PDF reports. Test archive access before changing your license or installation. Recreate measurements in CivilTakeoff from the original PDFs.
- Can CivilTakeoff import PSF or SwiftJob packages?
- No. Upload the original plan PDFs and recreate the measurements you need.
- What happens to my assemblies and templates?
- Recreate the conditions, item attachments, and conversions you need in CivilTakeoff. Test their output against a known example.
- Can I use both tools during the transition?
- Yes. You can finish an active bid in PlanSwift and test a new or completed sample project in CivilTakeoff. Keep the source revision and quantity records clear when using both.
- How much setup time should I allow?
- It depends on your item library, templates, and export requirements. Rebuild a representative scope first, measure the setup and review time, then use that result to plan the rest.
- How do I check that the transition worked?
- Compare the same sheet, scale, boundaries, units, and bid groups in both tools. Reconcile the exported item totals and record any intentional differences.