Preserve decades of valuable engineering data
Engineering organizations invest considerable time and resources collecting, interpreting, and reporting subsurface information.
Borehole logs, geological cross-sections, grain-size analyses, groundwater measurements, field testing results, and customized reporting templates may remain valuable for decades after the original investigation has been completed.
Many long-standing GAEA Technologies customers have accumulated extensive archives using earlier versions of WinLoG, WinFence, and WinSieve.
These records represent more than historical project files. They contain valuable geological observations, engineering measurements, and specialized reporting configurations developed through years of practical experience.
As software and operating systems evolve, organizations face an important challenge: how can they modernize their engineering software without losing access to the information created using earlier applications?
GAEA’s new Migration Center helps users transfer supported legacy WinLoG, WinFence, and WinSieve information into current GAEA software environments, reducing manual conversion and preserving the value of historical engineering records.
The objective is to help organizations move forward without having to recreate years of existing work.
Why migrating legacy engineering data matters
Engineering firms often continue using older software long after newer versions become available.
In many cases, the existing software still performs its original tasks adequately.
Engineers are familiar with the interface, existing templates satisfy client requirements, and historical project records remain accessible.
However, depending on outdated software indefinitely can create increasing difficulties.
Older applications may become incompatible with modern operating systems, computer hardware, or network configurations.
Legacy databases may depend on components that are no longer routinely installed or maintained.
Organizations may also find it difficult to introduce newer data management practices while maintaining information in several separate software systems.
For customers using older GAEA products, the concerns are often practical:
- Can existing borehole logs be imported without re-entering their data?
- Will geological cross-sections and fence diagrams remain accessible?
- Can historical grain-size measurements be preserved?
- What happens to customized templates and lithologic libraries?
- Can multiple projects be imported rather than converted individually?
- Will older information work with current reporting and validation tools?
The Migration Center is designed to simplify supported migration workflows and help users address these questions systematically.
Understanding the legacy GAEA applications
Before beginning a migration, it is useful to understand the different types of information maintained by the original applications.
WinLoG: Borehole and well logging
WinLoG has been used for many years to create and manage professional borehole and well logs.
Historical WinLoG projects may contain borehole identifiers, coordinates, geological intervals, soil and rock descriptions, sampling information, testing results, groundwater observations, and well construction details.
Many customers have also developed custom log templates, graphical symbols, and lithologic libraries to satisfy company or regulatory reporting requirements.
These resources are particularly important because they allow organizations to maintain established reporting standards.
WinFence: Geological cross-sections and fence diagrams
WinFence is used to create geological cross-sections and fence diagrams that help engineers and geoscientists visualize subsurface conditions between investigation locations.
Legacy WinFence data may contain cross-section layouts, geological interpretations, borehole references, stratigraphic boundaries, and display configurations.
Customized styles and templates may also represent a significant investment.
Preserving these resources can reduce the effort required to maintain or update historical geological interpretations.
WinSieve: Grain-size analysis
WinSieve was developed to analyze grain-size distribution data and prepare associated engineering reports.
Historical WinSieve records may include sieve sizes, retained weights, particle-size distribution results, soil classification information, and customized reporting settings.
These records are particularly valuable to geotechnical laboratories and engineering firms that need to reference historical soil testing information.
Moving this information into a current data management environment can improve accessibility while reducing dependence on older software.
Introducing legacy data importing in the GAEA Migration Center
The GAEA Migration Center brings supported legacy data conversion workflows into a broader approach to geological and geotechnical information management.
Rather than requiring organizations to manually recreate historical records, appropriate import procedures can transfer supported information from older databases or exchange files.
The migration method depends on the originating product, software version, database structure, and information being transferred.
Some legacy products support direct project database importing.
Others use exchange files created by the original application.
Templates, styles, and supporting libraries may require separate conversion operations.
These differences are important because migrating a borehole database is not necessarily the same process as converting a geological cross-section or a laboratory test record.
A structured migration approach allows organizations to identify the correct conversion method for each type of information.
Importing legacy WinLoG data
WinLoG migration is particularly important for organizations with large historical borehole and well log archives.
GAEA has long supported importing information from earlier WinLoG versions, including Version 4 project databases and exchange files.
The new Migration Center builds on these capabilities to help customers bring supported records into current WinLoG and GaeaSynergy workflows.
Importing individual borehole logs
When only selected historical logs are required, individual importing may be the most practical approach.
For example, a geotechnical engineer preparing an expansion project may need to review several boreholes from an investigation completed many years earlier.
If those records are stored in an older WinLoG format, the appropriate import procedure can transfer supported borehole information without requiring each geological description and test result to be recreated manually.
The engineer can then review the imported information and prepare an updated log using a suitable current template.
Older exchange-file workflows may require the records to be exported from the original WinLoG application before importing.
Importing multiple WinLoG projects
For larger archives, project-list importing provides a more efficient approach.
Legacy WinLoG 4 projects may be organized through a Microsoft Access project-list database named gaeaproject.mdb.
The supported project-list import workflow allows users to identify the available projects and select those requiring migration.
This can be particularly valuable for organizations with hundreds of historical project databases.
Instead of converting each project manually, users can organize the migration into manageable groups.
The original project identifiers should be reviewed, and any conflicts with existing destination projects should be resolved before completing the import.
Preserving WinLoG templates and libraries
For many customers, customized borehole log templates represent years of development.
These templates may incorporate company logos, specialized data columns, graphical symbols, soil classifications, testing graphs, and client-specific reporting requirements.
Earlier WinLoG versions maintained template information in separate databases, and supported import procedures are available for transferring older templates.
For example, legacy WinLoG 4 template lists may be stored in a Microsoft Access database named winlog.mdb.
During migration, users should identify the templates and supporting libraries that need to be preserved.
After importing, representative templates should be checked to confirm that their layouts, data assignments, and graphical elements behave correctly.
This review is especially important for heavily customized designs.
Importing legacy WinFence data
WinFence migration helps organizations preserve historical geological cross-sections and fence diagrams.
These graphical interpretations often represent substantial engineering effort.
A completed cross-section may combine numerous boreholes, geological contacts, lithologic patterns, groundwater information, and interpretive boundaries.
Recreating such drawings manually can be time-consuming.
Transferring cross-sections
Supported legacy WinFence exchange workflows allow cross-section information to be brought into the current GAEA environment.
For example, WinFence Version 2 cross-sections can be exported from the original application and subsequently imported through the appropriate conversion procedure.
After import, the cross-section can be reviewed and updated as required.
Users should verify that important elements such as borehole references, geological boundaries, graphical settings, and interpretations are represented correctly.
Preserving WinFence styles
Cross-section appearance is often controlled by styles or templates.
These may specify scales, lithologic patterns, labels, line styles, and other presentation settings.
GAEA’s documented legacy import procedures include the conversion of WinFence Version 2 template exchange files into cross-section styles.
This provides a way to preserve useful presentation configurations while transitioning to newer software.
As with borehole templates, converted styles should be reviewed before they are used for professional reporting.
Importing legacy WinSieve data
WinSieve migration addresses a different category of engineering information: grain-size distribution testing.
Grain-size analyses are commonly used for soil classification, foundation engineering, earthworks, pavement investigations, and other geotechnical applications.
A historical WinSieve record may contain the results of sieve testing and associated particle-size distribution information.
These results may remain valuable when reviewing previous investigations or comparing soil characteristics over time.
Preserving grain-size information
Where the legacy data structure is supported, importing WinSieve records can help preserve information such as sieve measurements, particle-size distributions, and associated test details.
However, the appropriate conversion process depends on the original WinSieve version and database configuration.
Some historical records may also use customized classifications or report formats that require additional review.
Moving toward GDMS
GAEA’s Geotechnical Data Management System (GDMS) provides a broader environment for managing geotechnical laboratory testing information.
For organizations previously using WinSieve, GDMS offers a path toward more integrated test management and reporting workflows.
Migrating historical grain-size results can therefore be part of a larger effort to organize laboratory information more consistently.
Users should confirm the applicable import procedure and compatibility requirements before beginning a large WinSieve migration.
Example: Migrating 20 years of historical engineering information
Consider a hypothetical engineering firm that has used GAEA software for more than 20 years.
During that period, the company accumulated:
- 1,200 historical WinLoG projects.
- Hundreds of borehole log templates.
- 150 WinFence geological cross-sections.
- A large collection of WinSieve grain-size analyses.
The organization now wants to standardize its work around the latest GAEA software.
However, its historical information remains distributed across multiple legacy databases and computers.
A systematic migration plan can make the transition more manageable.
Stage 1: Inventory existing data
The firm identifies the software versions used to create its historical information.
Project databases, log templates, lithologic libraries, cross-section files, and laboratory records are catalogued.
The company also identifies data stored on shared network drives or older workstations.
Stage 2: Back up the original records
Complete backups are created before any conversion begins.
These backups include the original databases, exchange files, templates, and supporting resources.
The historical files are retained even after successful migration.
Stage 3: Select representative projects
The firm chooses several examples from each legacy application.
For WinLoG, these include boreholes containing geological descriptions, samples, SPT results, and groundwater observations.
For WinFence, they include cross-sections with different geological interpretations and customized styles.
For WinSieve, they include grain-size analyses representing common testing and classification procedures.
Stage 4: Test the conversion workflows
The appropriate import procedures are used to transfer the representative records.
Engineering staff compare the resulting information with the original source files and reports.
Any differences are investigated before continuing.
Stage 5: Migrate additional information
Once the procedures have been verified, the organization begins transferring additional projects.
Large archives can be divided into smaller groups to simplify review and recordkeeping.
For some organizations, it may be appropriate to migrate only frequently referenced historical projects initially.
Stage 6: Standardize current workflows
After importing the historical information, the firm evaluates how its reporting templates, laboratory procedures, and project management practices can be improved.
This allows the organization to retain its existing investment in data while taking advantage of newer software capabilities.
Data validation after migration
A successful import does not automatically mean that every historical record is accurate or complete.
Older project databases may contain inconsistencies that were never identified when the information was originally collected.
Examples include:
- Missing borehole identifiers.
- Incorrect or inconsistent depth intervals.
- Incomplete geological descriptions.
- Missing sample information.
- Inconsistent measurement units.
- Invalid or questionable test results.
- Missing supporting templates or graphical symbols.
- Cross-section references that no longer match available boreholes.
GAEA’s newer Validation and QA/QC capabilities provide additional opportunities to review applicable imported borehole and testing data.
These tools can help identify inconsistencies that may affect how the information is interpreted or presented.
However, data validation must be distinguished from data conversion.
Importing transfers information between systems. Validation evaluates whether applicable information satisfies defined checks.
Both are important for responsible engineering data management.
Preserving templates, styles, and supporting resources
One of the most frequently overlooked aspects of migrating older engineering software is the importance of supporting resources.
A historical borehole database may contain all its original geological measurements, but the log may not display as expected if the corresponding template is missing.
Similarly, a cross-section may contain useful interpretation data but depend on a particular style configuration.
For this reason, migration planning should include more than project databases.
Organizations should identify important templates, lithologic libraries, cross-section styles, report configurations, and related resources.
The applicable import procedures may differ from those used for project records.
Users should also recognize that newer software may use updated reporting components.
Consequently, historical reports may not always reproduce pixel-for-pixel after conversion.
Where exact historical presentation is important, the original printed or PDF reports should be retained as reference documents.
Benefits for existing GAEA customers
For companies already using older GAEA products, the Migration Center offers several practical advantages.
Reduced re-entry: Supported historical information can be transferred without manually recreating every record.
Preserved investment: Borehole descriptions, geological interpretations, and testing information remain available for future reference.
Improved accessibility: Historical projects can be incorporated into more current software workflows.
More consistent reporting: Existing data can be presented using suitable modern templates and styles.
Better project continuity: Engineers can compare historical observations with information collected during new investigations.
Gradual modernization: Organizations can migrate selected projects first rather than converting their entire archive immediately.
These benefits are especially important for engineering firms that have maintained historical data for many years.
Supporting long-term engineering information management
Subsurface investigation information often remains useful long after the original project has been completed.
A borehole drilled 20 years ago may provide valuable background information for a new investigation at the same site.
A historical cross-section may assist an engineer evaluating changes to an existing infrastructure facility.
A previous grain-size analysis may provide useful context when comparing soil properties from different investigations.
However, the long-term value of these records depends on continued accessibility.
As software systems evolve, historical information can become difficult to retrieve if it remains dependent on outdated applications.
Migrating legacy data into maintained software environments helps reduce that risk.
It also provides opportunities to improve how older and newer information is organized and reviewed.
Part of GAEA’s broader Migration Center initiative
Legacy WinLoG, WinFence, and WinSieve migration is part of the broader GAEA Migration Center strategy.
The Migration Center also supports workflows involving legacy GaeaSynergy and StrataExplorer databases, gINT projects, government water well records, Excel spreadsheets, and industry data exchange formats such as AGS and DIGGS.
Together, these capabilities help address a common engineering problem: valuable subsurface information is often distributed across different applications, databases, and historical software versions.
By providing more structured paths for transferring supported records, GAEA helps organizations reduce data fragmentation and make better use of existing information.
For long-standing GAEA customers, legacy importing offers a practical way to preserve historical projects while adopting newer software.
For other engineering organizations, the broader Migration Center provides additional options for consolidating subsurface information from different sources.
Get started with legacy WinLoG, WinFence and WinSieve migration
Upgrading engineering software should not require abandoning valuable historical information.
GAEA’s new Migration Center helps customers preserve and import supported legacy WinLoG, WinFence, and WinSieve records while transitioning to modern GAEA project and reporting workflows.
Whether converting a few historical borehole logs, transferring custom cross-section styles, or reviewing legacy grain-size testing databases, the best approach is to begin with the original data, confirm the appropriate migration method, and verify the results.
Organizations with extensive historical archives should consider a staged migration plan based on representative projects and carefully reviewed conversion procedures.
To learn more, explore:
- GAEA Migration Center
- WinLoG Borehole Logging Software
- WinFence Geological Cross-Sections
- GaeaSynergy
- GDMS Geotechnical Data Management
- Upgrading WinLoG to Version 6
Preserve your historical logs. Retain your geological interpretations. Bring valuable engineering data forward with GAEA’s Migration Center.