Geotechnical data migration cost is difficult to estimate from a project count alone. Ten consistent databases may require less investigation than one heavily customized archive with unclear field meanings and missing dependencies. A useful budget therefore starts with the work needed to preserve meaning, verify results and support the intended destination workflow.
This guide explains the main cost drivers, how to prepare for a quotation and what to include in a delivery scope. It does not present a GAEA price list or promise a fixed completion time. The purpose is to help organizations compare proposals fairly and understand which decisions can reduce uncertainty before production begins.
Define the result being purchased
Begin with what users need to do after migration. Do they need to search historical boreholes, produce current logs, review laboratory results or continue active projects? Those outcomes determine the required records, relationships and configurations. “Move the database” is too vague to establish whether a quotation includes everything needed for practical use.
Separate conversion from related work such as source recovery, data correction, template recreation, software deployment and staff training. These activities may all be necessary, but they are not automatically included in the same price. A clear scope shows which party performs each task and which deliverables demonstrate completion.
Source accessibility is an early cost driver
A database that opens normally with a documented structure presents a different starting point from an inaccessible archive. Missing software, uncertain versions, damaged files or incomplete exports can require investigation before field mapping begins. Identify those conditions early rather than assuming every file in a project folder is ready for conversion.
External dependencies can also affect effort. Attachments, lookup lists, symbols and templates may be stored outside the main database. An export may contain values while omitting relationships or supporting content. Confirm what is actually available and which components are essential. The assessment should distinguish recoverable dependencies from material that cannot currently be located.
Volume matters, but structure matters too
Record counts help describe production and checking effort, but they do not capture every source of complexity. A large, consistent collection may support repeatable rules. A smaller archive containing several unrelated schemas may require separate analysis and testing for each structure. Count distinct source families as well as projects, boreholes and results.
Avoid estimating the scope from storage size alone. Images and attachments can make a modest database large, while a compact file may contain extensive relational information. Provide counts by relevant record type where available, and label estimates. Clear quantity assumptions make it easier to understand how the quote would change if the actual inventory differs.
Custom fields and terminology require decisions
Customized fields often contain valuable organizational knowledge, but their purpose may not be obvious from their names. A column called “Type” could describe several different concepts. Resolving that meaning may require examples, old reports and input from experienced staff. The conversion team cannot safely infer every convention from the database structure.
Controlled values and identifiers create similar questions. Decide whether legacy codes will be preserved, translated or combined, and document the rule. If projects reuse borehole names, the destination must maintain their separate identities. Mapping effort grows when many conventions need interpretation, especially when no single person can approve the decisions.
Data quality changes the amount of review
Missing units, questionable coordinates, duplicate records and inconsistent intervals can increase review effort. Some problems can be identified systematically; deciding how to treat them may still require professional judgment. Distinguish transferring the source faithfully from correcting it. Otherwise, a conversion quote can quietly become an open-ended data rehabilitation exercise.
Agree how known defects will be handled. Options may include correction before conversion, correction through an approved mapping, separate exception reporting or retention with a stated limitation. The right treatment depends on the intended use and available evidence. A proposal should explain which correction activities are included and how additional work will be authorized.
Templates and outputs need their own scope
A database migration does not necessarily reproduce the source application’s reporting system. Different products may represent layouts, symbols and calculated fields differently. Identify the essential templates and provide representative outputs. Clarify whether the objective is equivalent information, a new organizational standard or close visual reproduction of an existing deliverable.
Prioritization can materially simplify the project. If staff actively use three templates but the archive contains thirty historical variants, decide which require recreation now. Preserve the others appropriately and record the decision. Avoid treating every abandoned report variation as a production requirement unless it has a continuing purpose.
Include verification in the budget
A defensible scope should allocate effort to reconciliation and review, not only conversion. This may involve counts, identifier checks, selected value comparisons, relationship testing and output review. Agree which checks cover the full population and which use representative samples. Also identify who investigates differences and who accepts the result.
Customer review time is part of the total project effort even when it is not billed by the service provider. Staff may need to locate original records, interpret unusual fields and test normal workflows. Include that time in internal planning. A low external quote does not necessarily mean a low total cost if substantial customer work remains unstated.
Use a pilot to reduce estimating uncertainty
A representative pilot can reveal mapping difficulty, output requirements and exception patterns before the full archive is priced or released. Select examples that cover important differences rather than only clean records. Define the pilot’s deliverables and acceptance criteria so the exercise produces usable evidence about the remaining work.
Treat pilot findings as information for refinement. The production scope may become simpler because a repeatable route is demonstrated, or more involved because an unknown dependency appears. Neither outcome justifies assuming the initial estimate applies unchanged. Record revised quantities, assumptions and responsibilities before approving the next phase.
Compare quotations on the same basis
Ask each proposal to identify the source inventory, included record types, destination requirements, mapping work and verification scope. Confirm whether templates, attachments, exception reports and training are included. A headline total is meaningful only when the associated deliverables and exclusions are understood. Different prices may reflect different projects rather than different rates for identical work.
Clarify the commercial basis as well. A fixed scope, an effort-based assessment and a staged engagement allocate uncertainty differently. Confirm currency, taxes, any minimum charges, payment milestones and the process for approving changes. These should come from the actual quotation; do not infer them from another service or an unrelated software price.
Build a realistic schedule around dependencies
The elapsed schedule includes more than the time a conversion process runs. Source preparation, access arrangements, mapping decisions, pilot review and corrections can determine when production is possible. Identify dependencies and assign owners. If a key reviewer is unavailable, even a technically straightforward project may wait for an essential decision.
For a large archive, discuss delivery in defined batches. Early review can reveal issues before the same rule is applied broadly. Grouping similar source structures can also make checking more manageable. Confirm whether the proposed schedule assumes prompt acceptance of each batch and what happens when a newly discovered source type requires separate assessment.
Plan the transition for active projects. Decide when the source will be frozen, how changes after extraction will be captured and who will authorize use of the destination. Repeatedly converting a moving source without a clear change process can create duplicate effort and uncertainty about which dataset is current.
Reduce cost through preparation and prioritization
Useful preparation includes locating dependencies, identifying authoritative copies, documenting conventions and selecting representative examples. These steps reduce repeated clarification and make the initial assessment more productive. Avoid extensive undocumented cleanup, however. Changes that cannot be traced may create new questions about whether the assessment package still represents the original archive.
Consider phased migration based on business value. Active or frequently reused projects may deserve priority, while rarely accessed records can remain in a controlled archive until needed. Record the deferred scope and access plan. Phasing is most useful when it is an explicit decision rather than an accidental omission discovered after the old system is retired.
Specify the delivery package
The final package should include the agreed converted data and enough evidence to understand its limits. Depending on scope, that may include a field mapping register, identifier cross-reference, reconciliation summary, exception report and configured templates. Identify the file organization and any instructions needed to open or review the material.
Define acceptance and correction arrangements before delivery. State who reviews the result, how issues are reported and how revised files are distinguished. Keep the approved source baseline and project records according to organizational requirements. A delivery should leave the customer able to understand what was transferred, what changed and what remains outside the accepted scope.
Request an assessment with useful evidence
GAEA’s Migration Center page provides guidance on supported routes and scoped assistance. Share the source application and version, approximate volumes, representative records, essential outputs, destination workflow and timing requirements. Confirm file-handling arrangements before transferring the complete archive. Unreleased centralized Migration Center capabilities remain upcoming and should not be assumed in a current quotation.
Need a migration budget? Contact GAEA to discuss an assessment and, where useful, a representative pilot. A well-defined scope gives both parties a stronger basis for estimating cost and schedule while preserving the technical value of the information being moved.