Contacts, projects, budgets, schedules, change orders, bills, payments, daily logs and documents move into CPro360 through a guided import we run for you. Here's exactly what moves, the process we follow, how long it takes — and what to expect.
4–6 wks
typical calendar time, start to hypercare
~2 wks
of your team's time — mostly exports and review
to the cent
budget, committed, invoiced and paid totals reconciled before go-live
On CoConstruct? Start your exports this week.
CoConstruct is being folded into Buildertrend, and access may be time-limited.
Buildertrend acquired CoConstruct and is moving its customers over. Before anything else, export every module for every job — open and closed — and keep local copies. We'll walk you through it on a screen-share; the export checklist is below.
Scope
What moves
Moves imported as-isWith notes imported, with a known translationArchived kept as documents, not live records
Certificate of Insurance (COI) and W-9 documents re-attached to each sub, so they're payment-ready from day one
Jobs
Moves
Every project — name, address, client, status, start / target end
The client-portal link, and team assignments — matched by email once each person has accepted their CPro360 invite (logins are never copied over)
Open jobs in full detail; closed jobs as summarised records (see Money)
Budgets & estimates
With notes
Your cost-code list — mapped to NAHB / CSI where it lines up, kept as custom codes where it doesn't. Nothing dropped.
Live budget lines with budgeted vs. actual
Estimates and proposals with markups; allowances and optional items preserved
Selections come over as allowance lines plus your selection sheets as documents — CPro360 doesn't yet have a dedicated selections workflow
Schedule
With notes
Tasks, phases, dates, progress, assignees and the sub on each task
Finish-to-start dependencies move directly
Start-to-start / finish-to-finish links and lags are linked as finish-to-start with your original dates kept, and flagged on the task — the reconciliation sheet lists every one so you can review them
Financials
Moves
Change orders (approved and implemented, with their budget impact)
Subcontracts and purchase orders with their committed amounts
Vendor bills and payments, coded to the right budget line so actuals roll up — payments that settle a bill mark it paid
Material and equipment spend comes across the same way: as bills and payments coded to the budget
Rows already in your QuickBooks are marked as synced, so nothing is double-booked when the sync reconnects
Field records
With notes
Daily logs → CPro360's Journal, our daily log (date, notes, weather, crew count) with their photos attached
Owner draw schedules → payment installments on the job (planned, due, paid)
To-dos, punch lists, RFIs, permits and inspections are filed as documents on the job (see below), not re-created as live records
Documents & photos
Moves
Plans, contracts, photos, selection sheets — one folder per job, with your sub-folders kept as the document folders
Bulk-loaded from your export folders in batches; large volumes are fine, we schedule them, and a re-run replaces instead of duplicating
Home assets (appliances, finishes, warranties) for the client portal
Not migrated as live records
Archived
Message & comment history — exported to PDF and filed under the job's documents; you start fresh in Communications
Owner invoices — the draw schedule becomes payment installments (above); the invoice PDFs are filed
Warranty claims, punch lists, RFIs, permits, inspections — your exports are filed under the job's documents
Time clock / crew hours — stays in your payroll tool
Sequence
The import runs in build order
Each layer depends on the one before it — a budget line needs its job and cost code; a payment needs its job, sub and bill. We load in this order so every link lands.
01Cost codesyour list, mapped or kept custom
02Contactsclients, subs, suppliers + docs
03Jobsprojects, status, team
04Budgetslines, estimates, allowances
05Scheduletasks, phases, links
06FinancialsCOs, commitments, bills, payments
07Field & docslogs, draws, files, photos
Process
Five phases, one sign-off gate
01
Discovery
Kick-off. We count your jobs (open vs. closed), users, subs and document volume; confirm what each module can export; agree what's full-detail vs. summarised; set the cutover date and freeze window.
Done whenScope signed · export checklist issued · cutover date set
1 week
02
Export & mapping
You run the exports (we screen-share). We normalise them into our import templates, build the cost-code and status maps, resolve duplicate vendors and clients, and dry-run every file until it validates clean.
Done whenZero blocking errors · mapping approved by you
1–2 weeks
03
Staging & validation
A full trial load into a staging workspace. You click through three to five representative jobs end to end. We produce the reconciliation sheet — counts and money totals per job, source vs. CPro360.
Done whenEvery delta explained · your sign-off on the sheet
1 week
04
Cutover
Old system goes read-only. We re-export what changed since staging, load production in build order, reconnect QuickBooks if you use it, and invite your users.
Done whenProduction reconciles · users signed in
1–2 days
05
Hypercare
Daily check-ins the first week. Anything we missed is fixed with a targeted re-import — imports are repeatable and safe to re-run.
Done whenNo open data issues
2 weeks
Money
How we handle the financials
Open jobs — full detail
Budget lines, commitments, bills, payments and change orders, all linked. This is what makes your budget tab correct on day one.
Closed jobs — summarised
One project record with budget vs. actual totals, implemented change orders as totals, and every document. Cheaper to migrate, and it's what people actually look back at.
QuickBooks stays your ledger
We don't rebuild accounting history. We import the operational payments open jobs need, then reconnect your QuickBooks sync — with migrated rows marked so nothing is double-booked.
Reconciled to the cent
Per job: total budget, change-order total, committed, invoiced, paid and actual — source vs. CPro360. Every skipped row is listed with its reason. Nothing is silently dropped.
Your part
What we'll ask you to do
Export checklist
Every module, for every job (open and closed): budget & financials, schedule, change orders, selections & allowances, bills & payments, daily logs, to-dos & punch lists
Your account-wide lists: clients, subcontractors & suppliers, cost codes, and leads
All files and photos per job, as a folder per job with the sub-folders intact (a zip is fine — we unpack it)
Name each file with the job and the module it came from — for example Smith Residence – Budget.xlsx — so we can match everything up
Your QuickBooks setup: Online / Desktop / none, and whether the platform syncs to it today
Discovery questions
How many jobs — open vs. closed? Which closed jobs do you still look at?
Users (office + field), subs, clients — rough counts. Do clients use the portal?
Is your accounting in QuickBooks? Synced today?
How heavily do you use Selections / Allowances? Owner draws? Warranty?
Which modules can you export? CoConstruct: when does your access end?
Document / photo volume (GB); keep the folder structure?
Preferred cutover window and how long you can freeze the old system.
Timeline
What it takes
Track
Calendar
Your effort
Notes
From CoConstruct
4–6 wks
~2 wks
Exports first — access may be time-limited. Selections-heavy accounts need a little more mapping time.
From Buildertrend
4–6 wks
~2 wks
Document and photo volumes tend to be larger; purchase orders map cleanly.
Migrations are run for you by the CPro360 team as a professional-services engagement, quoted per migration — you're never left to import on your own.
Next
Two things to do this week
1. Send us your exports
Run the checklist above — or book a screen-share and we'll do it together. On CoConstruct, this is the first thing to do.
2. Answer the discovery questions
Seven short answers let us size the work, set the cutover date and tell you up front exactly what will and won't move.