Estimating and preconstruction data are among the most valuable information a contractor owns. Years of unit costs, vendor quotes, assemblies, and historical bids drive pricing decisions and competitive advantage. When a company decides to change estimating platforms, the data move is often treated as a technical detail. It should be treated as a project with its own plan, owner, and security considerations.
Here are the most common mistakes and how to avoid them.
Mistake 1: Starting without an inventory
Before any data moves, you need to know what you have. Estimating information tends to live in many places: the main platform, local spreadsheets, shared drives, estimators' laptops, and old email attachments.
Fix: Build an inventory of data sources, owners, and approximate volume. Include cost databases, assemblies, templates, vendor lists, bid histories, takeoff files, and attachments.
Mistake 2: Migrating everything
Bringing every legacy record into a new system can also bring outdated costs, duplicate vendors, and errors.
Fix: Decide what to migrate, what to archive, and what to leave behind. For example, current cost databases and active bids may be migrated, while old completed bids might go to a read-only archive.
Mistake 3: No clean-up before moving
Importing messy data into a clean system just makes a new mess.
Fix: Allocate time to merge duplicates, standardize naming, and remove obsolete items before the move. Ask estimators to review the highest-value databases.
Mistake 4: Ignoring who has access
Migrations often involve temporary access for consultants, implementation partners, and exporters. These accounts can linger with broad rights.
Fix: Create named accounts for every external party, grant only required permissions, set end dates, and remove them at go-live. Use MFA on all of them.
Mistake 5: Moving data through insecure channels
Exports are frequently emailed, copied to USB drives, or placed in consumer cloud storage because it is quick. Those copies may include pricing, margins, and client lists.
Fix: Use an approved, encrypted transfer method and a controlled location. Delete working copies once the migration is validated. Keep a record of where exports were stored.
Mistake 6: Skipping validation
A platform may appear to import everything while altering units, rounding, or formulas.
Fix: Pick a sample of past bids and rebuild them in the new system, then compare totals with the original results. Differences deserve an explanation before go-live.
Mistake 7: No fallback plan
If something goes wrong on a bid deadline day, the team needs a way to keep working.
Fix: Run the old and new systems in parallel for a defined period, and keep the old system available in read-only mode for a time after cutover. Schedule the switch away from major bid deadlines.
Mistake 8: Forgetting retention and legal needs
Contracts, insurers, or bonding companies may require you to keep bid and project records for certain periods.
Fix: Ask your attorney or accountant how long you need to retain estimating records, and store archives accordingly, with backups.
Mistake 9: Not decommissioning the old system
An old estimating server or subscription that nobody uses is still a target. Unpatched and forgotten systems can expose data.
Fix: After the archive is verified, shut down the old system on a defined date, remove its accounts, and confirm backups of the archive. If it was a cloud subscription, cancel it and confirm data deletion according to the vendor's process.
A simple migration plan
- Name an owner in preconstruction and a technical partner in IT.
- Inventory data and decide what moves, archives, or retires.
- Clean the data.
- Set up access with least privilege and MFA.
- Test with sample bids.
- Train estimators before go-live.
- Run in parallel for a defined period.
- Archive and decommission the old system.
Consider a hypothetical 70-person civil contractor whose estimating cost database lives partly in the platform and partly in an estimator's personal spreadsheets. The inventory step alone might reveal that the most trusted unit costs are in a file only one person controls. Discovering that before the move is far cheaper than after.
Where Ironfield Cyber fits
Ironfield Cyber supports contractors during software transitions, including access control, secure data transfer, backups, and decommissioning of old systems. If you are considering a change in estimating or project software, we can help plan the security side of the move so the data arrives intact and nothing is left exposed.