{"id":92651,"date":"2026-06-25T02:54:01","date_gmt":"2026-06-25T02:54:01","guid":{"rendered":"https:\/\/gaeatech.com\/knowledge-center\/?p=92651"},"modified":"2026-06-12T02:58:07","modified_gmt":"2026-06-12T02:58:07","slug":"preventing-data-loss-during-borehole-data-migration","status":"publish","type":"post","link":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/","title":{"rendered":"Preventing Data Loss During Borehole Data Migration"},"content":{"rendered":"\n<h2 id=\"h-best-practices-for-moving-geological-data-from-legacy-systems-to-modern-databases\" class=\"wp-block-heading\">Best Practices for Moving Geological Data from Legacy Systems to Modern Databases<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Data migration is one of the most critical\u2014and often riskiest\u2014activities in geological and geotechnical data management. Organizations routinely migrate borehole records from legacy databases, spreadsheets, paper archives, proprietary software systems, and aging data repositories into modern geological database platforms. While the goal is usually to improve accessibility, reporting, validation, and long-term data management, poorly planned migrations can result in lost information, corrupted records, broken relationships, and costly rework.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For organizations managing decades of geological, geotechnical, hydrogeological, environmental, or mining data, migration projects often involve thousands of boreholes, hundreds of thousands of intervals, laboratory results, groundwater records, and historical reports. Even small migration errors can affect engineering decisions, regulatory compliance, environmental investigations, and future project planning.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The good news is that most migration-related data loss can be prevented through structured planning, data standardization, spreadsheet cleanup, and comprehensive validation procedures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This article explores best practices for preventing data loss during borehole data migration, focusing on legacy systems, spreadsheet cleanup, standardization, and validation workflows.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-why-borehole-data-migrations-fail\" class=\"wp-block-heading\">Why Borehole Data Migrations Fail<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Many organizations underestimate the complexity of geological data migration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Migration projects often involve:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Multiple data sources<\/li>\n\n\n\n<li>Different software platforms<\/li>\n\n\n\n<li>Inconsistent coding systems<\/li>\n\n\n\n<li>Missing metadata<\/li>\n\n\n\n<li>Historical records<\/li>\n\n\n\n<li>Varying data quality standards<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">When these issues are not addressed before migration, data loss becomes much more likely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Common migration failures include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Missing boreholes<\/li>\n\n\n\n<li>Lost laboratory results<\/li>\n\n\n\n<li>Incorrect coordinates<\/li>\n\n\n\n<li>Broken interval relationships<\/li>\n\n\n\n<li>Truncated text fields<\/li>\n\n\n\n<li>Duplicate records<\/li>\n\n\n\n<li>Missing attachments<\/li>\n\n\n\n<li>Corrupted groundwater records<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In many cases, these problems are not discovered until long after the migration is complete.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-understanding-legacy-systems\" class=\"wp-block-heading\">Understanding Legacy Systems<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Most geological organizations possess valuable information stored in legacy systems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Older geological databases<\/li>\n\n\n\n<li>DOS-based applications<\/li>\n\n\n\n<li>Custom-built software<\/li>\n\n\n\n<li>Microsoft Access databases<\/li>\n\n\n\n<li>Spreadsheets<\/li>\n\n\n\n<li>Paper borehole logs<\/li>\n\n\n\n<li>Archived laboratory systems<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">While these systems may still contain valuable information, they often present challenges for modern migration projects.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-common-legacy-data-issues\" class=\"wp-block-heading\">Common Legacy Data Issues<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Legacy databases frequently contain:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Obsolete coding standards<\/li>\n\n\n\n<li>Inconsistent field definitions<\/li>\n\n\n\n<li>Unsupported formats<\/li>\n\n\n\n<li>Missing documentation<\/li>\n\n\n\n<li>Duplicate records<\/li>\n\n\n\n<li>Incomplete metadata<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One system may store lithology as:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Code<\/th><\/tr><tr><td>CL<\/td><\/tr><tr><td>SA<\/td><\/tr><tr><td>GR<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Another may use:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td>Description<\/td><\/tr><tr><td>Clay<\/td><\/tr><tr><td>Sand<\/td><\/tr><tr><td>Gravel<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Without proper mapping, important information can be lost during migration.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-document-the-source-system\" class=\"wp-block-heading\">Document the Source System<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before any migration begins, organizations should fully document:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Database structure<\/li>\n\n\n\n<li>Field definitions<\/li>\n\n\n\n<li>Relationships<\/li>\n\n\n\n<li>Coding systems<\/li>\n\n\n\n<li>Data volumes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This documentation becomes essential when verifying migrated data later.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-inventory-all-data-sources\" class=\"wp-block-heading\">Inventory All Data Sources<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most common causes of migration-related data loss is incomplete source identification.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations often focus on the primary database while overlooking secondary data sources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Spreadsheets<\/li>\n\n\n\n<li>Laboratory exports<\/li>\n\n\n\n<li>GIS systems<\/li>\n\n\n\n<li>Monitoring databases<\/li>\n\n\n\n<li>Core photography archives<\/li>\n\n\n\n<li>PDF reports<\/li>\n\n\n\n<li>Survey files<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A comprehensive inventory should identify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data source location<\/li>\n\n\n\n<li>Data owner<\/li>\n\n\n\n<li>Data format<\/li>\n\n\n\n<li>Record count<\/li>\n\n\n\n<li>Relationship to other datasets<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Without a complete inventory, important information may never be migrated.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-spreadsheet-cleanup\" class=\"wp-block-heading\">Spreadsheet Cleanup<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Spreadsheets are among the most common sources of migration problems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Many organizations have accumulated years of borehole information stored in Excel files created by multiple users.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">While spreadsheets are flexible, they often contain inconsistencies that must be addressed before migration.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-common-spreadsheet-problems\" class=\"wp-block-heading\">Common Spreadsheet Problems<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Duplicate records<\/li>\n\n\n\n<li>Missing fields<\/li>\n\n\n\n<li>Inconsistent codes<\/li>\n\n\n\n<li>Mixed units<\/li>\n\n\n\n<li>Formatting issues<\/li>\n\n\n\n<li>Hidden rows<\/li>\n\n\n\n<li>Embedded formulas<\/li>\n\n\n\n<li>Merged cells<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These issues can interfere with automated imports.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-standardize-units\" class=\"wp-block-heading\">Standardize Units<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Migration projects should verify that units are consistent.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td>Parameter<\/td><td>Unit<\/td><\/tr><tr><td>Depth<\/td><td>metres<\/td><\/tr><tr><td>Elevation<\/td><td>metres<\/td><\/tr><tr><td>Recovery<\/td><td>percent<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Mixing units can create significant errors after migration.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-remove-duplicate-records\" class=\"wp-block-heading\">Remove Duplicate Records<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Duplicate records frequently occur when multiple spreadsheet versions exist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before migration:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Identify duplicates<\/li>\n\n\n\n<li>Verify correct records<\/li>\n\n\n\n<li>Remove obsolete versions<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This prevents unnecessary confusion and database inflation.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-data-standardization\" class=\"wp-block-heading\">Data Standardization<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Standardization is one of the most effective ways to reduce migration risk.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Without standardization, identical information may appear in many different forms.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-example-lithology-descriptions\" class=\"wp-block-heading\">Example: Lithology Descriptions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Consider the following entries:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Clay<\/li>\n\n\n\n<li>CLAY<\/li>\n\n\n\n<li>clay<\/li>\n\n\n\n<li>Silty Clay<\/li>\n\n\n\n<li>Clay, Silty<\/li>\n\n\n\n<li>Firm Clay<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">All may represent similar materials.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standardization ensures that equivalent values are stored consistently.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-controlled-vocabularies\" class=\"wp-block-heading\">Controlled Vocabularies<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations should establish:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Standard lithology codes<\/li>\n\n\n\n<li>Laboratory test codes<\/li>\n\n\n\n<li>Sampling method codes<\/li>\n\n\n\n<li>Groundwater observation codes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Controlled vocabularies improve consistency and simplify validation.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-standardize-coordinate-systems\" class=\"wp-block-heading\">Standardize Coordinate Systems<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Coordinate-related errors are among the most serious migration problems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations should verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Coordinate system<\/li>\n\n\n\n<li>Projection<\/li>\n\n\n\n<li>Datum<\/li>\n\n\n\n<li>Elevation reference<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Failure to standardize spatial information can result in boreholes appearing in incorrect locations.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-data-mapping\" class=\"wp-block-heading\">Data Mapping<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Data mapping defines how information from the source system will be stored in the target database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every source field should have a documented destination.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-mapping-example\" class=\"wp-block-heading\">Mapping Example<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td>Source Field<\/td><td>Target Field<\/td><\/tr><tr><td>BH_NO<\/td><td>BoreholeID<\/td><\/tr><tr><td>DEPTH_M<\/td><td>FinalDepth<\/td><\/tr><tr><td>NORTHING<\/td><td>YCoordinate<\/td><\/tr><tr><td>EASTING<\/td><td>XCoordinate<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Clear mapping documentation helps ensure that information is transferred accurately.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-relationship-mapping\" class=\"wp-block-heading\">Relationship Mapping<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Migration projects must also preserve relationships.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Boreholes to lithology intervals<\/li>\n\n\n\n<li>Boreholes to samples<\/li>\n\n\n\n<li>Samples to laboratory tests<\/li>\n\n\n\n<li>Wells to groundwater readings<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Broken relationships can significantly reduce data value.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-validation-procedures\" class=\"wp-block-heading\">Validation Procedures<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Validation is the most important step in preventing data loss.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Migration should never be considered complete until validation has been performed.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-pre-migration-validation\" class=\"wp-block-heading\">Pre-Migration Validation<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Before migration begins:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Record counts<\/li>\n\n\n\n<li>Field completeness<\/li>\n\n\n\n<li>Coordinate quality<\/li>\n\n\n\n<li>Duplicate records<\/li>\n\n\n\n<li>Mandatory fields<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This establishes a baseline for comparison.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-post-migration-validation\" class=\"wp-block-heading\">Post-Migration Validation<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">After migration:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compare migrated data against source records.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td>Dataset<\/td><td>Source<\/td><td>Target<\/td><\/tr><tr><td>Boreholes<\/td><td>5,000<\/td><td>5,000<\/td><\/tr><tr><td>Samples<\/td><td>120,000<\/td><td>120,000<\/td><\/tr><tr><td>Lab Tests<\/td><td>450,000<\/td><td>450,000<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Differences should be investigated immediately.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-automated-validation-rules\" class=\"wp-block-heading\">Automated Validation Rules<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Modern geological databases often support automated validation checks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<h3 id=\"h-borehole-validation\" class=\"wp-block-heading\">Borehole Validation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Duplicate IDs<\/li>\n\n\n\n<li>Missing coordinates<\/li>\n\n\n\n<li>Invalid elevations<\/li>\n<\/ul>\n\n\n\n<h3 id=\"h-lithology-validation\" class=\"wp-block-heading\">Lithology Validation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Overlapping intervals<\/li>\n\n\n\n<li>Missing descriptions<\/li>\n\n\n\n<li>Invalid codes<\/li>\n<\/ul>\n\n\n\n<h3 id=\"h-sampling-validation\" class=\"wp-block-heading\">Sampling Validation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Depth conflicts<\/li>\n\n\n\n<li>Duplicate sample numbers<\/li>\n<\/ul>\n\n\n\n<h3 id=\"h-groundwater-validation\" class=\"wp-block-heading\">Groundwater Validation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Invalid dates<\/li>\n\n\n\n<li>Water level anomalies<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Automated validation significantly improves migration reliability.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-use-a-staging-environment\" class=\"wp-block-heading\">Use a Staging Environment<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">One of the best practices for migration projects is using a staging environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A staging database allows organizations to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Import data safely<\/li>\n\n\n\n<li>Perform validation<\/li>\n\n\n\n<li>Resolve issues<\/li>\n\n\n\n<li>Test reports<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">before data enters production.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This approach reduces risk and improves quality.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-qa-qc-review-workflows\" class=\"wp-block-heading\">QA\/QC Review Workflows<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Validation alone is not enough.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Technical review remains essential.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A recommended workflow includes:<\/p>\n\n\n\n<h3 id=\"h-step-1\" class=\"wp-block-heading\">Step 1<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Extract data from source systems.<\/p>\n\n\n\n<h3 id=\"h-step-2\" class=\"wp-block-heading\">Step 2<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Perform spreadsheet cleanup.<\/p>\n\n\n\n<h3 id=\"h-step-3\" class=\"wp-block-heading\">Step 3<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Standardize data.<\/p>\n\n\n\n<h3 id=\"h-step-4\" class=\"wp-block-heading\">Step 4<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Import into staging database.<\/p>\n\n\n\n<h3 id=\"h-step-5\" class=\"wp-block-heading\">Step 5<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Run automated validation.<\/p>\n\n\n\n<h3 id=\"h-step-6\" class=\"wp-block-heading\">Step 6<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Conduct technical review.<\/p>\n\n\n\n<h3 id=\"h-step-7\" class=\"wp-block-heading\">Step 7<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Approve migration results.<\/p>\n\n\n\n<h3 id=\"h-step-8\" class=\"wp-block-heading\">Step 8<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Move data into production.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This process combines automation with expert oversight.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-audit-trails-and-migration-documentation\" class=\"wp-block-heading\">Audit Trails and Migration Documentation<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Migration projects should be fully documented.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations should record:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Source systems<\/li>\n\n\n\n<li>Mapping rules<\/li>\n\n\n\n<li>Validation results<\/li>\n\n\n\n<li>Error corrections<\/li>\n\n\n\n<li>Review approvals<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This documentation provides accountability and supports future audits.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"h-why-audit-trails-matter\" class=\"wp-block-heading\">Why Audit Trails Matter<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Years after migration, users may ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Where did this data originate?<\/li>\n\n\n\n<li>Was it modified?<\/li>\n\n\n\n<li>Were errors corrected?<\/li>\n\n\n\n<li>Was validation completed?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Audit trails provide the answers.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-common-data-loss-risks\" class=\"wp-block-heading\">Common Data Loss Risks<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Several recurring issues contribute to migration failures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<h3 id=\"h-truncated-text\" class=\"wp-block-heading\">Truncated Text<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Long descriptions may exceed target field lengths.<\/p>\n\n\n\n<h3 id=\"h-missing-attachments\" class=\"wp-block-heading\">Missing Attachments<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Core photos, reports, and PDFs may not be migrated.<\/p>\n\n\n\n<h3 id=\"h-orphaned-records\" class=\"wp-block-heading\">Orphaned Records<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Laboratory results lose links to samples.<\/p>\n\n\n\n<h3 id=\"h-coordinate-conversion-errors\" class=\"wp-block-heading\">Coordinate Conversion Errors<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Incorrect projections move boreholes to invalid locations.<\/p>\n\n\n\n<h3 id=\"h-unmapped-fields\" class=\"wp-block-heading\">Unmapped Fields<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Information exists in the source system but has no destination.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Each of these risks should be addressed during planning.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-future-proofing-your-geological-database\" class=\"wp-block-heading\">Future-Proofing Your Geological Database<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">A migration project is an opportunity to improve data quality.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations should use migrations to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Standardize coding systems<\/li>\n\n\n\n<li>Implement validation rules<\/li>\n\n\n\n<li>Improve metadata management<\/li>\n\n\n\n<li>Establish QA workflows<\/li>\n\n\n\n<li>Support AGS and DIGGS standards<\/li>\n\n\n\n<li>Prepare for AI and analytics initiatives<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A successful migration does more than move data\u2014it creates a stronger foundation for future projects.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 id=\"h-conclusion\" class=\"wp-block-heading\">Conclusion<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Preventing data loss during borehole data migration requires much more than transferring records from one system to another. Successful migrations begin with understanding legacy systems, inventorying all data sources, cleaning spreadsheets, standardizing information, documenting mapping rules, and performing rigorous validation. By combining automated QA\/QC procedures with technical review and audit-ready documentation, organizations can significantly reduce migration risk while improving data quality and long-term usability. As geological databases continue to evolve, well-planned migration strategies will play a critical role in preserving valuable subsurface information and ensuring that decades of knowledge remain accessible, accurate, and ready for future use.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Best Practices for Moving Geological Data from Legacy Systems to Modern Databases Data migration is one of the most critical\u2014and often riskiest\u2014activities in geological and geotechnical data management. Organizations routinely migrate borehole records from legacy databases, spreadsheets, paper archives, proprietary software systems, and aging data repositories into modern geological database platforms. While the goal is [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":92652,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[792,1880],"tags":[1827,1962,795,1884,1106,1611,1946,1276,1961,1885,1963,558,757,1965,1964],"class_list":["post-92651","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-borehole-data-management","category-borehole-qa-qc","tag-ags-data","tag-borehole-data-migration","tag-borehole-database","tag-data-quality","tag-data-standardization","tag-data-validation","tag-diggs-standard","tag-digital-transformation","tag-geological-database-migration","tag-geological-qa-qc","tag-geological-records","tag-geotechnical-data-management","tag-legacy-systems","tag-migration-workflow","tag-spreadsheet-cleanup"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.7 (Yoast SEO v27.7) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Preventing Data Loss During Borehole Data Migration - Knowledge Center<\/title>\n<meta name=\"description\" content=\"Ensure success in data migration by preventing data loss during borehole data migration. Learn best practices for safe transfers.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Preventing Data Loss During Borehole Data Migration\" \/>\n<meta property=\"og:description\" content=\"Ensure success in data migration by preventing data loss during borehole data migration. Learn best practices for safe transfers.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/\" \/>\n<meta property=\"og:site_name\" content=\"Knowledge Center\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.linkedin.com\/company\/2663277\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-25T02:54:01+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/06\/preventing-data-loss-during-borehole-data-migration-hero.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1536\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"GAEA Technologies\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"GAEA Technologies\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/\"},\"author\":{\"name\":\"GAEA Technologies\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/940fb5fed6e95dd9d0ec1370207f5dba\"},\"headline\":\"Preventing Data Loss During Borehole Data Migration\",\"datePublished\":\"2026-06-25T02:54:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/\"},\"wordCount\":1303,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/preventing-data-loss-during-borehole-data-migration-hero.jpg\",\"keywords\":[\"AGS data\",\"borehole data migration\",\"borehole database\",\"data quality\",\"data standardization\",\"Data Validation\",\"DIGGS standard\",\"digital transformation\",\"geological database migration\",\"geological qa qc\",\"geological records\",\"Geotechnical Data Management\",\"Legacy Systems\",\"migration workflow\",\"spreadsheet cleanup\"],\"articleSection\":[\"Borehole Data Management\",\"QA\\\/QC\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/\",\"url\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/\",\"name\":\"Preventing Data Loss During Borehole Data Migration - Knowledge Center\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/preventing-data-loss-during-borehole-data-migration-hero.jpg\",\"datePublished\":\"2026-06-25T02:54:01+00:00\",\"description\":\"Ensure success in data migration by preventing data loss during borehole data migration. Learn best practices for safe transfers.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/#primaryimage\",\"url\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/preventing-data-loss-during-borehole-data-migration-hero.jpg\",\"contentUrl\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/preventing-data-loss-during-borehole-data-migration-hero.jpg\",\"width\":1536,\"height\":1024,\"caption\":\"Successful borehole data migrations require legacy system assessment, spreadsheet cleanup, standardization, validation, and structured QA\\\/QC workflows to preserve data integrity.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/preventing-data-loss-during-borehole-data-migration\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Preventing Data Loss During Borehole Data Migration\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#website\",\"url\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/\",\"name\":\"GAEA Technologies Blog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#organization\",\"name\":\"GAEA Technologies\",\"url\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/Gaea_3dlogo_white-scaled.jpg\",\"contentUrl\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/Gaea_3dlogo_white-scaled.jpg\",\"width\":2560,\"height\":1440,\"caption\":\"GAEA Technologies\"},\"image\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/company\\\/2663277\\\/\"],\"description\":\"GAEA Technologies develops and distributes geoscience and engineering solutions worldwide. Our solutions have been used for over 30 years by companies and organizations around the world.\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/940fb5fed6e95dd9d0ec1370207f5dba\",\"name\":\"GAEA Technologies\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cdc2b26dbe02c637b6e6ae5e99ff7928c8d2c7fb325dffb8da7e8b0af95dcbd7?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cdc2b26dbe02c637b6e6ae5e99ff7928c8d2c7fb325dffb8da7e8b0af95dcbd7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cdc2b26dbe02c637b6e6ae5e99ff7928c8d2c7fb325dffb8da7e8b0af95dcbd7?s=96&d=mm&r=g\",\"caption\":\"GAEA Technologies\"},\"sameAs\":[\"https:\\\/\\\/gaeatech.com\\\/wordpress\"],\"url\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/author\\\/mfraser\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Preventing Data Loss During Borehole Data Migration - Knowledge Center","description":"Ensure success in data migration by preventing data loss during borehole data migration. Learn best practices for safe transfers.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/","og_locale":"en_US","og_type":"article","og_title":"Preventing Data Loss During Borehole Data Migration","og_description":"Ensure success in data migration by preventing data loss during borehole data migration. Learn best practices for safe transfers.","og_url":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/","og_site_name":"Knowledge Center","article_publisher":"https:\/\/www.linkedin.com\/company\/2663277\/","article_published_time":"2026-06-25T02:54:01+00:00","og_image":[{"width":1536,"height":1024,"url":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/06\/preventing-data-loss-during-borehole-data-migration-hero.jpg","type":"image\/jpeg"}],"author":"GAEA Technologies","twitter_card":"summary_large_image","twitter_misc":{"Written by":"GAEA Technologies","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/#article","isPartOf":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/"},"author":{"name":"GAEA Technologies","@id":"https:\/\/gaeatech.com\/knowledge-center\/#\/schema\/person\/940fb5fed6e95dd9d0ec1370207f5dba"},"headline":"Preventing Data Loss During Borehole Data Migration","datePublished":"2026-06-25T02:54:01+00:00","mainEntityOfPage":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/"},"wordCount":1303,"commentCount":0,"publisher":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/#organization"},"image":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/#primaryimage"},"thumbnailUrl":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/06\/preventing-data-loss-during-borehole-data-migration-hero.jpg","keywords":["AGS data","borehole data migration","borehole database","data quality","data standardization","Data Validation","DIGGS standard","digital transformation","geological database migration","geological qa qc","geological records","Geotechnical Data Management","Legacy Systems","migration workflow","spreadsheet cleanup"],"articleSection":["Borehole Data Management","QA\/QC"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/","url":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/","name":"Preventing Data Loss During Borehole Data Migration - Knowledge Center","isPartOf":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/#website"},"primaryImageOfPage":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/#primaryimage"},"image":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/#primaryimage"},"thumbnailUrl":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/06\/preventing-data-loss-during-borehole-data-migration-hero.jpg","datePublished":"2026-06-25T02:54:01+00:00","description":"Ensure success in data migration by preventing data loss during borehole data migration. Learn best practices for safe transfers.","breadcrumb":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/#primaryimage","url":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/06\/preventing-data-loss-during-borehole-data-migration-hero.jpg","contentUrl":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/06\/preventing-data-loss-during-borehole-data-migration-hero.jpg","width":1536,"height":1024,"caption":"Successful borehole data migrations require legacy system assessment, spreadsheet cleanup, standardization, validation, and structured QA\/QC workflows to preserve data integrity."},{"@type":"BreadcrumbList","@id":"https:\/\/gaeatech.com\/knowledge-center\/preventing-data-loss-during-borehole-data-migration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/gaeatech.com\/knowledge-center\/"},{"@type":"ListItem","position":2,"name":"Preventing Data Loss During Borehole Data Migration"}]},{"@type":"WebSite","@id":"https:\/\/gaeatech.com\/knowledge-center\/#website","url":"https:\/\/gaeatech.com\/knowledge-center\/","name":"GAEA Technologies Blog","description":"","publisher":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/gaeatech.com\/knowledge-center\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/gaeatech.com\/knowledge-center\/#organization","name":"GAEA Technologies","url":"https:\/\/gaeatech.com\/knowledge-center\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/gaeatech.com\/knowledge-center\/#\/schema\/logo\/image\/","url":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2025\/12\/Gaea_3dlogo_white-scaled.jpg","contentUrl":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2025\/12\/Gaea_3dlogo_white-scaled.jpg","width":2560,"height":1440,"caption":"GAEA Technologies"},"image":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/2663277\/"],"description":"GAEA Technologies develops and distributes geoscience and engineering solutions worldwide. Our solutions have been used for over 30 years by companies and organizations around the world."},{"@type":"Person","@id":"https:\/\/gaeatech.com\/knowledge-center\/#\/schema\/person\/940fb5fed6e95dd9d0ec1370207f5dba","name":"GAEA Technologies","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/cdc2b26dbe02c637b6e6ae5e99ff7928c8d2c7fb325dffb8da7e8b0af95dcbd7?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/cdc2b26dbe02c637b6e6ae5e99ff7928c8d2c7fb325dffb8da7e8b0af95dcbd7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/cdc2b26dbe02c637b6e6ae5e99ff7928c8d2c7fb325dffb8da7e8b0af95dcbd7?s=96&d=mm&r=g","caption":"GAEA Technologies"},"sameAs":["https:\/\/gaeatech.com\/wordpress"],"url":"https:\/\/gaeatech.com\/knowledge-center\/author\/mfraser\/"}]}},"jetpack_featured_media_url":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/06\/preventing-data-loss-during-borehole-data-migration-hero.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/posts\/92651","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/comments?post=92651"}],"version-history":[{"count":1,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/posts\/92651\/revisions"}],"predecessor-version":[{"id":92653,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/posts\/92651\/revisions\/92653"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/media\/92652"}],"wp:attachment":[{"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/media?parent=92651"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/categories?post=92651"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/tags?post=92651"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}