Preserve years of geological, geotechnical, and environmental project information while upgrading legacy GAEA software to GaeaSynergy 6.
Protecting your investment in historical subsurface data
Engineering and environmental consulting firms often accumulate years or even decades of valuable project information.
Historical borehole logs, geological descriptions, laboratory testing results, groundwater measurements, environmental records, and customized reporting templates represent a substantial investment in data collection and engineering expertise.
For organizations using older versions of GAEA software, this information may be stored in legacy StrataExplorer 3 or GaeaSynergy 4 and 5 databases.
While these earlier systems have served customers for many years, modernizing software should not require organizations to abandon their existing project records.
GAEA Technologies’ new Migration Center makes it easier to transfer supported legacy GaeaSynergy 4, GaeaSynergy 5, and StrataExplorer 3 information into the current GaeaSynergy 6 environment.
The Migration Center provides a more centralized approach to importing historical projects, reducing manual data transfer and helping organizations preserve access to existing information as they adopt newer software capabilities.
Why legacy data migration matters
Many engineering organizations continue using older software long after newer versions become available.
There are understandable reasons for this.
Existing software may still perform the required work, users may be familiar with established procedures, and customized templates may have taken considerable time to develop.
A company may also have hundreds of historical projects stored in database structures designed for earlier software versions.
For these organizations, the greatest concern is often not the cost of upgrading the software. It is the risk of losing access to valuable historical information.
Questions commonly include:
- Will existing project databases remain accessible?
- Can historical borehole logs and geological information be transferred?
- Will customized log templates and lithologic libraries be preserved?
- Can multiple projects be migrated without manually recreating each one?
- What happens when project numbers already exist in the destination database?
- Can the migration be performed without disrupting other users?
- Will historical information remain available for future investigations?
The Migration Center is intended to make these transitions easier to manage through supported conversion workflows.
Rather than requiring users to start over, the objective is to preserve existing information and make it useful in the current GAEA software environment.
From StrataExplorer to GaeaSynergy
GAEA’s software platform has evolved considerably over time.
StrataExplorer was originally developed as a platform for organizing, managing, displaying, and analyzing geological and environmental information.
In 2019, StrataExplorer was renamed GaeaSynergy with the introduction of Version 4, reflecting the increasingly integrated nature of the software.
The platform combines project data management with applications for borehole logging, geotechnical testing, environmental data management, cross-sections, mapping, and visualization.
Subsequent releases introduced additional capabilities and improvements.
GaeaSynergy 6 represents the current generation of this integrated environment, with updated database structures, expanded data management capabilities, and improvements to project workflows.
For organizations continuing to use StrataExplorer 3 or GaeaSynergy 4 and 5, upgrading offers an opportunity to take advantage of newer capabilities while preserving historical information.
However, because the database structures have changed, upgrading requires an appropriate data migration process.
Introducing legacy database importing in the Migration Center
The new GAEA Migration Center builds on the import and upgrade tools developed for earlier versions of GaeaSynergy.
It provides a more centralized starting point for moving supported legacy project information into GaeaSynergy 6.
The migration process accommodates differences between older and newer database structures while allowing users to select the information to transfer.
Depending on the source version and selected import workflow, supported information may include:
- Project identification and administrative information.
- Borehole and well records.
- Geological and lithological descriptions.
- Field measurements and testing information.
- Laboratory and environmental data.
- Associated project records.
- Borehole log templates.
- Lithologic libraries and related supporting information.
Not every legacy database component is necessarily transferred through the same operation.
Projects, templates, and supporting libraries may require separate import procedures.
This distinction is particularly important for organizations that have developed extensive custom reporting resources.
Importing GaeaSynergy 5 projects
Organizations using GaeaSynergy 5 can migrate supported project information into GaeaSynergy 6.
Two approaches are available: importing individual projects or importing multiple projects through a project list.
Importing individual projects
Individual project importing is useful when only selected historical investigations are required.
For example, an engineering consultant may need to reopen a geotechnical investigation completed several years ago.
Instead of converting an entire historical archive, the consultant can import the relevant Version 5 project into the current environment.
The import workflow identifies the selected project database and converts the supported information to the destination project structure.
After import, the project should be opened and reviewed to confirm that its important records are available.
This approach is particularly suitable for companies that prefer to migrate historical projects as they are needed.
Importing multiple projects
For organizations with larger archives, importing a list of projects is generally more efficient.
GaeaSynergy 5 uses a project list database, typically named gaeasynergy.mdb, to identify available projects.
The supported project-list import workflow allows users to select multiple projects for conversion.
A typical procedure includes:
- Selecting the source GaeaSynergy 5 project list database.
- Reviewing the projects available for importing.
- Selecting individual projects or the complete list.
- Identifying and resolving project number conflicts.
- Importing the selected project records.
- Reviewing the resulting projects in GaeaSynergy 6.
This can reduce the effort required to transfer a large number of historical projects.
It also provides an opportunity to identify existing project numbers that might conflict with those already used in the destination system.
Importing GaeaSynergy 4 projects
Organizations still using GaeaSynergy 4 can follow a similar migration approach.
GaeaSynergy 4 project databases can be imported individually or through a project list using the applicable version-specific import workflow.
The source project list is typically maintained in a Microsoft Access database.
During migration, the selected records are converted into the database structures used by GaeaSynergy 6.
As with Version 5, users should review project identifiers, associated data, and any customized resources after importing.
For firms with older project archives, it may be practical to begin with a small representative group of projects.
This allows differences between historical database structures and the current application to be identified before converting a larger collection.
Importing StrataExplorer 3 projects
StrataExplorer 3 is an earlier generation of the GAEA software platform.
Many long-standing customers may still have valuable investigation records, templates, and lithologic libraries created using this version.
GaeaSynergy provides migration procedures for supported StrataExplorer 3 data, allowing users to transfer existing information into the newer software environment.
The appropriate method depends on the installation and database configuration.
For a single-user installation on the same computer, an available upgrade workflow may provide a direct conversion route.
For installations on different computers or network environments, the supported import wizards can be used to transfer selected projects and related resources.
A particularly important consideration is that GaeaSynergy 6 should not be configured to use the original StrataExplorer 3 database as its active database.
The older data must be converted into the appropriate current structure.
Pointing the newer application directly at the legacy database can cause compatibility problems and should be avoided.
Preserving custom templates and lithologic libraries
For many GAEA customers, historical project data is only part of the investment they want to preserve.
Customized boring and well log templates may have been developed to satisfy company reporting standards, government specifications, or specialized industry requirements.
Lithologic libraries may also contain custom symbols, material descriptions, and conventions developed over many years.
These resources can be as valuable as the underlying project records.
The legacy import capabilities therefore include supported procedures for transferring templates and lithologic libraries.
Depending on the source version, templates and libraries may be imported separately from the project databases.
After importing, users should review representative templates to ensure that columns, symbols, graphical elements, and data assignments behave as expected.
Special attention should be given to older custom designs that may depend on features or settings that have changed between software versions.
An import should preserve supported information, but it does not eliminate the need to verify presentation and reporting results.
Example: Upgrading an engineering company’s historical archive
Consider a hypothetical geotechnical consulting firm that has used GaeaSynergy for more than 15 years.
The company has accumulated approximately 800 historical projects created using StrataExplorer 3, GaeaSynergy 4, and GaeaSynergy 5.
These projects include borehole logs, soil and rock descriptions, laboratory results, groundwater observations, and customized templates.
The company wants to introduce GaeaSynergy 6 but remains concerned about maintaining access to historical investigations.
Rather than attempting to migrate every project simultaneously, the firm establishes a staged migration plan.
Stage 1: Inventory the existing information
The company identifies its historical databases, project lists, templates, libraries, and database locations.
Projects are grouped according to the originating software version.
Stage 2: Back up the original databases
Complete backups are created before any conversion begins.
The original source databases are retained as historical archives.
Stage 3: Select representative projects
The company selects several projects containing different types of information.
These include projects with complex borehole logs, environmental records, laboratory testing results, and customized templates.
Stage 4: Perform pilot imports
The selected projects are imported using the appropriate version-specific migration workflows.
The engineering team verifies that important information has transferred correctly.
Stage 5: Import additional projects
After establishing a reliable procedure, the organization migrates additional projects in manageable groups.
The firm may also choose to import older projects only when they become relevant to new investigations.
Stage 6: Review and standardize workflows
Following migration, the organization evaluates whether existing templates and project procedures should be retained or updated to take advantage of newer GaeaSynergy capabilities.
This staged approach reduces disruption while allowing the company to modernize its software environment.
Handling project number conflicts
One important consideration when importing legacy projects is the possibility of duplicate project identifiers.
For example, a Version 5 project may use the same project number as a project already maintained in GaeaSynergy 6.
The project-list import workflow provides a mechanism for identifying and resolving these conflicts.
Depending on the selected import option, users can assign a different project number or omit the conflicting project from the import.
This helps prevent accidental duplication or confusion between historical and current projects.
For larger organizations, establishing a consistent project numbering convention before migration can simplify the process.
It is also advisable to retain a record of any project identifiers changed during conversion.
This provides an important reference when comparing migrated records with archived reports or original project documentation.
Considerations for network installations
Migrating legacy data in a networked GaeaSynergy environment requires additional planning.
In these installations, the project databases and supporting data may be stored on a central server or shared network location.
Multiple users may also depend on common templates, project lists, and database connections.
Before beginning migration, the organization should identify the current database locations and determine where the GaeaSynergy 6 data will be maintained.
The new licensing and database environment should be configured appropriately before historical information is imported.
Users should also confirm that the necessary network permissions and application settings are correct.
Where practical, a test installation can be used to verify the process before updating the production environment.
The legacy databases should remain backed up and unchanged until the new system has been tested successfully.
Taking advantage of GaeaSynergy 6
Migrating historical projects is not simply about retaining access to old information.
It also allows organizations to take advantage of the current software environment.
GaeaSynergy 6 includes improvements to data management, project organization, licensing, and related application workflows.
The platform also provides access to newer capabilities such as Validation and QA/QC, expanded project management functionality, mapping improvements, and updated registration and maintenance processes.
Historical project information can therefore become part of a broader modernization strategy.
For example, a company may import selected older borehole logs and review the available data using current WinLoG validation capabilities.
Or it may transfer historical environmental and geotechnical records into the current project environment for use alongside new investigations.
Not every modern feature will necessarily apply to every legacy record, particularly where historical information is incomplete.
Nevertheless, the ability to bring older data forward can extend its useful life.
Reviewing imported information
Successful migration requires more than confirmation that a project appears in the destination project list.
Users should verify that important information remains accessible and that the converted records behave correctly.
A practical review may include:
- Confirming project names, numbers, and identification details.
- Opening representative boreholes and wells.
- Checking geological descriptions and interval depths.
- Reviewing groundwater and testing information.
- Confirming laboratory and environmental records where applicable.
- Checking customized log templates.
- Reviewing lithologic symbols and libraries.
- Verifying that network users can access the migrated data.
- Comparing representative outputs with historical reports.
This verification is especially important when migrating records from older or highly customized installations.
The original databases should remain available until the migrated information has been adequately reviewed.
Common migration mistakes to avoid
Several common mistakes can complicate legacy software upgrades.
Using the original database directly: Earlier database structures should not simply be assigned as active GaeaSynergy 6 databases.
Failing to create backups: Original project databases and supporting resources should be preserved before conversion.
Importing an entire archive without testing: A representative pilot can identify problems before they affect hundreds of projects.
Forgetting templates and libraries: Historical project records may depend on customized reporting resources stored separately.
Ignoring project number conflicts: Duplicate identifiers can create confusion and complicate historical record management.
Overlooking network settings: Shared database paths, access permissions, and licensing arrangements may differ between versions.
Assuming every feature converts identically: Custom content and legacy functionality should be reviewed after import.
A controlled migration process helps minimize these risks.
Preserve historical information without delaying modernization
One reason engineering organizations postpone software upgrades is concern about disrupting established workflows.
Legacy applications may continue functioning adequately, even when they no longer benefit from the latest development and support improvements.
However, maintaining older software indefinitely can create increasing risks as operating systems, hardware, network environments, and security requirements change.
The longer an organization waits, the more complicated future migration may become.
By providing supported import procedures for older GAEA software, the Migration Center helps reduce this barrier.
Organizations can move historical information into the current platform without having to recreate every project manually.
They can also adopt a gradual approach, migrating the most relevant historical records first and converting additional archives as needed.
This allows the benefits of modernization to be introduced without requiring an immediate replacement of every established procedure.
Part of GAEA’s broader Migration Center strategy
Legacy GaeaSynergy and StrataExplorer importing is one part of GAEA’s broader Migration Center initiative.
The Migration Center also addresses the transfer of data from other sources, including gINT project databases, government water well databases, Excel spreadsheets, AGS, and DIGGS exchange files.
These capabilities reflect an important principle: geological, geotechnical, and environmental information should remain useful beyond the original software in which it was created.
For customers upgrading from older GAEA products, the Migration Center provides a path for preserving existing project information.
For organizations moving from other applications, it offers additional ways to bring relevant subsurface data into the GAEA software environment.
Together, these capabilities support more accessible and reusable engineering information.
Get started with legacy GAEA data migration
If your organization is still using StrataExplorer 3, GaeaSynergy 4, or GaeaSynergy 5, upgrading does not need to mean abandoning your historical project information.
The new GAEA Migration Center provides a more organized approach to importing supported legacy data into GaeaSynergy 6.
Whether migrating a single historical project or preparing to convert a large project archive, the recommended approach is to begin with backups, select the appropriate migration workflow, and verify the imported information before relying on it.
For more information, explore:
- GAEA Migration Center
- GaeaSynergy Software
- GaeaSynergy Import and Export
- How to Migrate from StrataExplorer 3 to GaeaSynergy 6
Preserve your historical projects. Protect your investment in subsurface information. Move forward with GaeaSynergy 6 and the new GAEA Migration Center.