Private equity and portfolios
Surveying roll-ups: merging decades of field records across acquired firms
By SourceX Editorial · Updated
Short answer
Surveying firm acquisition integration succeeds when every acquired archive is indexed to one shared schema before files are moved or systems retired. Index each job by location, survey type, dates, surveyor of record and source firm, then migrate in batches. Never discard a legacy firm's field books, raw data or research files until the index points to them.
Key takeaways
- Index first and migrate second: a shared job index makes acquired archives searchable long before files are consolidated.
- Location is the primary key for survey records, so every index row needs parcel, legal description and coordinates.
- Field books, raw data and research files often matter more than final plats, because they show how the answer was reached.
- Keep the source firm and surveyor of record on every record, since responsibility and some rights stay with them.
- Retire legacy servers and software only after the index and archive have been verified.
Why survey archives are an integration priority#
Survey archives are an integration priority because a surveying firm's past jobs are reused constantly: repeat clients, adjoining parcels, re-staking and boundary questions all start with the previous file. A platform that cannot find an acquired firm's old jobs loses one of the main reasons it bought the firm.
Each acquired firm usually arrives with its own job numbering, folder conventions, CAD standards and a mix of paper field books, flat files and digital raw data. Without a common index, the platform owns several archives that only their original staff know how to search, and that knowledge leaves when a senior party chief retires.
What sits in a typical acquired survey archive?#
A typical acquired survey archive holds far more than finished plats: it holds the evidence and reasoning behind each boundary, topographic or construction answer. Inventory each firm's holdings before planning any migration, and record the software version needed to open each digital record type.
- Field books and digital field notes, including sketches, ties and monument descriptions.
- Raw data collector and GNSS files from equipment such as Trimble, Leica or Carlson.
- Processed point files, control networks and adjustment reports.
- CAD drawings in Civil 3D, Carlson or MicroStation, plus signed and recorded plats.
- Research files: deeds, prior surveys, recorded plats and title commitments.
- Job folders with proposals, invoices, client correspondence and change requests.
- Historical records inherited from firms the acquired company itself bought years earlier.
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
A common index schema across acquired archives#
A common index schema gives every job from every acquired firm one row with the same fields, so staff can search by location, client or survey type regardless of where the files physically sit. Build it before moving files: the index is useful immediately and then guides the migration.
Coordinate systems deserve their own field. Legacy files may use different datums, projections or local coordinates, so record the system with each job rather than assuming a platform standard applies to older work.
| Field | What it holds | Notes |
|---|---|---|
| Platform job ID | New identifier assigned at indexing | Keep the legacy job number in its own field |
| Source firm | Acquired firm that performed the work | Needed for rights and responsibility questions |
| Surveyor of record | Licensed surveyor who signed or supervised | Never overwrite on later updates |
| Location | Parcel ID, legal description, county, coordinates | Primary search key for most staff |
| Coordinate system | Datum, projection or local system used | Prevents misplaced data when files are combined |
| Survey type | Boundary, ALTA/NSPS, topographic, construction staking and others | One controlled list across all firms |
| Dates | Field dates and signature date | Supports searches for recent or historic work |
| Client | Client name and client type | Flag confidentiality terms where they exist |
| File locations | Paths, box numbers or flat-file drawers | Points to both paper and digital copies |
| Rights and restrictions | Client terms, subcontracted work, holds | Blank means not yet reviewed |
The integration sequence, step by step#
The integration sequence works best in a fixed order that protects records before anything is reorganized. Most losses in roll-ups happen in the gap between closing and integration, when a legacy server is switched off, a laptop is reimaged or a storage unit lease ends.
Scanning paper field books is often the largest single effort. Prioritize books covering areas where the platform expects repeat work, and index the rest by location and date so they can be found and scanned on demand.
- Step 1: freeze deletion at every acquired firm and protect legacy servers and paper storage.
- Step 2: inventory record types, systems and software versions at each firm.
- Step 3: agree the shared schema and controlled lists for survey type and client type.
- Step 4: index digital jobs first, then paper, starting with areas of active work.
- Step 5: check a sample of index rows against the files they point to.
- Step 6: migrate files to shared storage in batches, keeping original folder structures.
- Step 7: retire legacy servers and software only after verification.
Rights and responsibility do not merge automatically#
Rights and professional responsibility in survey records do not merge automatically when firms combine. The surveyor of record remains responsible for the work they signed, client contracts may limit reuse of deliverables, and work performed by subcontracted crews raises its own ownership questions.
Copyright in work an employee creates as part of regular duties generally belongs to the employer as a work made for hire. The Copyright Office explains that commissioned work from outside parties qualifies only in certain statutory categories and with an express written agreement, so field work bought from independent subcontractors may need an assignment before the platform treats it as its own. State board rules on survey records also vary, so review them state by state with counsel.
Record these findings in the index's rights field rather than in a separate memo, so anyone searching the archive sees the restriction next to the record.
What a merged archive is good for#
A merged archive is good for faster quoting, better field preparation, training and, in some cases, new uses of the records themselves. Each use needs slightly different fields indexed and different rights cleared, so decide the priority uses before indexing begins.
| Use | Records needed | Rights question |
|---|---|---|
| Quoting repeat or adjoining work | Index by parcel and client, prior proposals | Usually internal use only |
| Field preparation | Control, monuments found, prior field notes | Internal use |
| Training new party chiefs | Field books paired with final plats | Internal use, with client confidentiality in mind |
| Exit diligence | Complete index, rights flags, retention policy | Shows a buyer what the platform controls |
| Licensing to AI developers | Field notes, raw data and decisions with outcomes | Client terms, personal data and surveyor responsibility reviewed per package |
Illustrative: a three-firm survey platform builds one index#
Illustrative: a fictional PE-backed survey platform has acquired three firms in neighboring counties. One runs Civil 3D with digital field data, one uses Carlson with scanned field books, and the oldest keeps paper books and flat files in a rented storage unit.
The integration lead freezes deletion, moves the paper archive to climate-controlled storage and builds the shared index. Party chiefs at each firm assign survey types and flag jobs done by subcontracted crews. Indexing the oldest firm's records by parcel lets the platform quote boundary work on adjoining properties using prior field evidence.
Legacy servers are retired only after the index is verified. The rights field marks subcontracted jobs and client-restricted work, which keeps later decisions about reuse straightforward.
How SourceX works with merged survey records#
SourceX helps survey platforms assess whether field notes, raw data and decision histories can be licensed to AI developers studying real geospatial and boundary work. The SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, begins with a metadata fit check, so a shared index often answers most early questions.
Bulky raw GNSS and scan archives remain on the platform's own storage or travel on encrypted drives; SourceX does not host multi-terabyte datasets. Each package carries a SourceX Evidence Packet recording provenance, licensing rights, permitted use, the privacy record and release authorization.
Frequently asked questions
Should we scan every paper field book?
Not at first. Index every book by location, date and job so it can be found, then scan by priority: areas with active work, jobs likely to be revisited and books in poor physical condition. On-demand scanning for the rest spreads the effort without losing access.
Do legacy job numbers need to be kept?
Yes. Staff, clients and recorded documents refer to legacy job numbers long after an acquisition. Keep the original number in its own index field alongside the platform job ID, so a search on either one finds the record.
Who should own the merged archive?
Usually the platform's operating entity, with a named records owner responsible for the index, storage and retention policy. Where acquired firms remain separate legal entities, record which entity holds each archive, because that affects who can approve any later use.
What if an acquired firm's software is no longer supported?
Export files to current or open formats while a working copy of the old software is still available, and keep the original files alongside the exports. Note in the index which jobs were converted, because conversions can shift layers, coordinates or annotations.
Can survey records contain personal data?
Yes. Client correspondence, title documents and field notes can name owners, occupants and neighbors. Personal details are reviewed and removed before any use outside the firm, and some records may be excluded entirely.
Sources
- Copyright Office Circular 30 explains a work made for hire arises either when an employee creates the work as part of regular duties, or when a work in certain statutory categories is created under an express written agreement with a party specially ordering or commissioning it. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.