{"id":93122,"date":"2026-10-23T01:33:59","date_gmt":"2026-10-23T01:33:59","guid":{"rendered":"https:\/\/gaeatech.com\/knowledge-center\/?p=93122"},"modified":"2026-10-23T01:34:03","modified_gmt":"2026-10-23T01:34:03","slug":"gint-database-import-export-migration-center","status":"publish","type":"post","link":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/","title":{"rendered":"Importing and Exporting gINT Databases with GAEA&#8217;s New Migration Center"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><em>Preserve valuable geotechnical data, simplify migration from legacy gINT databases, and improve data exchange between gINT, WinLoG, and GaeaSynergy.<\/em><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Modernizing geotechnical data without losing decades of work<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For decades, Bentley&#8217;s gINT has been widely used by geotechnical engineers, geological consultants, transportation agencies, and environmental professionals to store subsurface investigation data and produce borehole logs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Many engineering organizations have accumulated hundreds or thousands of gINT project databases containing valuable historical information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These databases may include geological descriptions, soil and rock classifications, Standard Penetration Test (SPT) results, groundwater measurements, laboratory testing, well construction information, and other engineering data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As organizations modernize their software systems, preserving and reusing this information has become increasingly important.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>GAEA Technologies&#8217; new Migration Center simplifies the process of importing and exporting gINT project databases, helping organizations transfer existing subsurface information into WinLoG and GaeaSynergy while maintaining compatibility with supported gINT data structures.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The objective is not simply to copy records between databases. It is to make historical information accessible, reusable, and easier to manage within modern engineering workflows.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why gINT data migration matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">gINT has been an important part of the geotechnical software industry for many years.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Engineering firms have invested substantial time developing project databases, custom data fields, lookup tables, reporting conventions, and borehole log designs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In some organizations, historical gINT records represent decades of engineering experience.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Replacing these databases or manually recreating their information would be expensive and time-consuming.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The retirement of the gINT product line has also increased interest in alternative solutions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, migrating away from an established system presents several challenges:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Preserving existing borehole and geological information.<\/li>\n\n\n\n<li>Transferring project identification and location details.<\/li>\n\n\n\n<li>Maintaining relationships between data tables.<\/li>\n\n\n\n<li>Handling custom fields and user-defined data structures.<\/li>\n\n\n\n<li>Converting units and geological classifications.<\/li>\n\n\n\n<li>Reproducing essential borehole log information.<\/li>\n\n\n\n<li>Exchanging data with organizations that continue to use gINT.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These challenges are particularly significant for engineering companies with extensive historical project archives.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The new GAEA Migration Center provides a more structured approach to addressing them.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding gINT project databases<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">gINT version 8 project databases typically use the <code>.gpj<\/code> file extension and are based on Microsoft Access database technology.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A gINT project database contains related tables that organize project information, borehole locations, geological intervals, field measurements, and laboratory test results.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Common categories of information include:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Project information:<\/strong> Project names, numbers, locations, clients, and other identifying details.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Point information:<\/strong> Borehole or well identifiers, coordinates, ground elevations, drilling dates, and total depths.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Lithology information:<\/strong> Soil and rock descriptions, geological intervals, sample depths, and formation information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Field testing:<\/strong> SPT results, groundwater observations, drilling information, and other measurements collected during investigations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Laboratory testing:<\/strong> Water content, grain-size distribution, Atterberg limits, and other geotechnical test results.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, not every gINT database uses identical table structures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations frequently modify their databases to accommodate project requirements, company standards, or government reporting specifications.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This flexibility makes gINT powerful, but it also means that successful migration requires more than simply copying database files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A reliable migration process must recognize the structure of the source database and determine how the information should be represented in the destination system.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Introducing gINT import and export in the Migration Center<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GAEA has supported gINT data exchange in earlier versions of WinLoG and GaeaSynergy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The new Migration Center builds on this experience by bringing migration workflows into a more centralized environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rather than relying on unrelated import tools, the Migration Center provides a dedicated starting point for working with supported external and legacy project data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For gINT databases, the workflow focuses on selecting source information, reviewing available data structures, configuring the required mappings, and transferring supported information into GAEA projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Migration Center also supports the broader goal of exchanging project information with other software environments through appropriate export workflows.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is important because software migration is not always a one-way process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some organizations may migrate entirely from gINT to WinLoG and GaeaSynergy, while others may need to exchange data with clients, subcontractors, or government agencies that continue to use gINT.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Importing gINT project databases<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Importing existing gINT project information is one of the most important applications of the Migration Center.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The process allows organizations to reuse historical geotechnical and geological data without manually recreating each record.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Select the gINT database<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Begin by opening the Migration Center and selecting the appropriate gINT import option.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Choose the <code>.gpj<\/code> project database containing the information to be transferred.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The selected database provides the source information for the import process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before importing, it is good practice to retain an unchanged backup of the original database.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Review project information<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The source database may contain project details such as project number, name, client, and location.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These details help identify the records being imported and associate them with the appropriate destination project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Where applicable, users can review the information before proceeding with the conversion.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Review tables and fields<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most important stages of importing a gINT database is understanding its data structure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The database may contain standard tables together with additional fields created specifically for a company or agency.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A structured import workflow allows relevant tables and fields to be identified and associated with corresponding data types in the destination system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a gINT field containing SPT blow counts should be associated with the appropriate testing data rather than imported as an unrelated text field.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Similarly, geological interval depths must be interpreted correctly to preserve their relationships with soil and rock descriptions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fields without a direct equivalent may require additional configuration or may not be transferable through the selected workflow.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Select or configure the log template<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Borehole logs depend on both the underlying data and the template used to display it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When importing a gINT project, users can associate the transferred information with an appropriate WinLoG template.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the available import options, this may involve selecting an existing template or creating a template based on the source database fields.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The objective is to make imported information available for reporting without requiring engineers to manually reconstruct every borehole.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An important distinction is that a gINT project database and a gINT report library are not the same thing. Importing project data does not automatically guarantee reproduction of custom gINT report layouts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Complete the import and review the results<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once the configuration has been established, the supported records can be imported into the GAEA project environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Following import, users should review representative boreholes and verify that critical information has been transferred correctly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Particular attention should be given to geological intervals, sample depths, test results, coordinates, units, and borehole identifiers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This review is essential when migrating customized databases or large historical datasets.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Exporting project data to gINT databases<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Although many organizations are moving away from gINT, exporting data to a supported gINT database remains valuable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Engineering firms often work with clients, consultants, and government agencies that have established data-delivery requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A project completed using WinLoG or GaeaSynergy may still need to provide its borehole information in a format compatible with an existing gINT workflow.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">GAEA&#8217;s gINT export capabilities support this type of data exchange.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A typical export process includes selecting the destination database, identifying the boreholes or wells to export, and specifying the project information and data fields to include.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The exported information must be mapped to the appropriate gINT tables and field structures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly important when transferring information to a customized database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a client may require borehole identification, geological intervals, SPT results, and groundwater observations to be organized according to a specific database structure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Using a configured export workflow can reduce the need for manual data transfer and help maintain consistency between projects.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why exporting remains important<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Retaining the ability to export supported gINT-compatible information provides several practical advantages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Client compatibility:<\/strong> Engineering firms can deliver data to clients who continue to use gINT.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Collaboration:<\/strong> Consultants using different software systems can exchange structured project information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Gradual software migration:<\/strong> Organizations can introduce WinLoG and GaeaSynergy without requiring every department or external partner to change software simultaneously.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Contractual requirements:<\/strong> Some government and infrastructure contracts may specify legacy database formats.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Data portability:<\/strong> Maintaining appropriate exchange options reduces dependence on any single application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Export support should not be confused with perfect round-trip conversion. Custom fields, report designs, attachments, and other specialized information must be checked for compatibility with the selected destination database.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Example: Migrating a historical gINT project archive<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Consider a geotechnical engineering company with 20 years of historical investigations stored in gINT.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The company has accumulated approximately 1,500 project databases containing thousands of boreholes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Its engineers regularly refer to these records when preparing proposals, planning new drilling investigations, and reviewing previous projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, the company wants to adopt WinLoG and GaeaSynergy for future work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Re-entering all the historical information manually would require substantial time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, the company can develop a structured migration plan using the Migration Center.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The first step is to identify representative databases containing the different table structures and customizations used over the years.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These databases can be evaluated and imported into test projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The engineering team can then review the transferred information and confirm that important geological descriptions, test results, and project identifiers have been preserved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once the required mappings and procedures have been established, the organization can progressively migrate additional supported projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This approach reduces implementation risk by identifying conversion issues before they affect a large number of records.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It also allows the company to retain its historical gINT databases as original archives while developing a more modern environment for future engineering work.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Using imported gINT data in WinLoG<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After importing supported gINT data, engineers can use WinLoG to manage borehole information and prepare professional boring and well logs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly valuable for organizations that want to continue using historical data while standardizing their reporting procedures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical applications include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reviewing historical borehole descriptions.<\/li>\n\n\n\n<li>Preparing updated borehole log presentations.<\/li>\n\n\n\n<li>Applying company-standard log templates.<\/li>\n\n\n\n<li>Organizing field and laboratory information.<\/li>\n\n\n\n<li>Reviewing geological intervals and measurements.<\/li>\n\n\n\n<li>Applying applicable Validation and QA\/QC rules.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">One important benefit is the ability to distinguish between transferring existing information and improving how it is managed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An organization does not necessarily need to change the geological interpretation of a historical borehole simply because it adopts new software.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, it can preserve the original observations while making them easier to access, review, and present.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Integrating gINT information with GaeaSynergy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GaeaSynergy provides an integrated environment for managing geological, geotechnical, environmental, and related project information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Importing gINT data into this environment can help organizations consolidate historical records with newer investigation data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a transportation engineering consultant may maintain historical gINT boreholes from highway investigations completed over many years.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">New projects can generate additional boreholes using WinLoG and other GAEA applications.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By bringing relevant historical information into GaeaSynergy, the consultant can work toward maintaining a more consistent project data environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly useful when investigations are repeated along the same highway corridors, at existing facilities, or within long-term infrastructure projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Historical records may contain valuable information about subsurface variability that would otherwise remain scattered across separate database files.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Improving data quality during migration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Moving data from one software system to another presents an opportunity to review historical information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Older geotechnical databases may contain inconsistencies that were never identified when the records were originally created.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Missing borehole identifiers.<\/li>\n\n\n\n<li>Geological intervals with overlapping depths.<\/li>\n\n\n\n<li>Incomplete sample information.<\/li>\n\n\n\n<li>Invalid or inconsistent units.<\/li>\n\n\n\n<li>Missing coordinates or elevations.<\/li>\n\n\n\n<li>SPT results that do not match expected data conventions.<\/li>\n\n\n\n<li>Laboratory measurements recorded in unexpected fields.<\/li>\n\n\n\n<li>Inconsistent geological descriptions.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The new Validation and QA\/QC capabilities in WinLoG and GaeaSynergy complement the Migration Center by providing tools for reviewing applicable imported information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, imported lithological intervals may be checked for inconsistencies, and supported testing records may be evaluated against validation rules.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not every historical record will meet current reporting standards, and some data may require professional interpretation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nevertheless, identifying these issues during migration can improve the reliability and usefulness of the resulting project database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A successful database import confirms that information has been transferred. It does not independently confirm that the original measurements or geological observations were correct.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Migration is more than file conversion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A common mistake when changing engineering software is to focus exclusively on whether a file can be opened in another application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For organizations with extensive historical records, successful migration requires a broader approach.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The original data must be preserved, important relationships must remain intact, unsupported information must be identified, and the new workflow must produce useful engineering results.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For this reason, organizations should begin large migrations with a representative pilot rather than immediately converting their entire archive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The pilot should include simple databases, highly customized databases, records containing a variety of field and laboratory test types, and examples with known data-quality issues.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Comparing source and destination results can help establish reliable acceptance criteria.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is also advisable to retain original databases and document the conversion process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This creates an audit trail and allows historical records to be revisited if questions arise.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Supporting a gradual transition from gINT<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Engineering organizations often adopt new technology gradually.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An established company may have long-standing project archives, experienced users, customized reporting procedures, and clients who continue to request gINT files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Attempting to replace every part of this workflow at once can create unnecessary disruption.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Migration Center supports a more practical transition strategy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations can begin by importing selected historical projects, configuring appropriate WinLoG templates, and verifying that critical data remains accessible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">New investigations can then be completed using GAEA software, while appropriate gINT export workflows help maintain compatibility with legacy requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Over time, more historical information can be migrated as project needs and available resources justify the effort.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This approach allows companies to modernize without abandoning the investments they have already made in data collection and management.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Beyond gINT: A broader data migration solution<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The GAEA Migration Center is not limited to gINT.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It forms part of GAEA Technologies&#8217; broader strategy for improving geological, geotechnical, and environmental data interoperability.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Other migration capabilities include supported legacy GAEA project conversions, government water well information, and industry data exchange formats such as AGS and DIGGS.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Together, these capabilities are intended to reduce the fragmentation of subsurface information across different applications and data structures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For engineering organizations, the long-term objective is to make historical data easier to preserve, transfer, validate, and reuse.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Get started with the new GAEA Migration Center<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Existing geotechnical information represents a substantial investment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations should not have to abandon decades of borehole logs, geological descriptions, laboratory measurements, and project records simply because the software used to create them is being replaced.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>GAEA&#8217;s new Migration Center helps organizations import and export supported gINT project data while establishing a more consistent approach to managing historical subsurface information.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Whether the objective is moving from gINT to WinLoG, integrating historical data into GaeaSynergy, or exchanging information with clients who still use gINT, structured migration and export workflows can reduce repetitive work and improve data accessibility.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The result is a more practical path toward modern geotechnical data management while preserving the value of existing engineering records.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Learn more<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Explore the following resources:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/gaeatech.com\/migration_center.php\">GAEA Migration Center<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/gaeatech.com\/winlog.php\">WinLoG Borehole Logging Software<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/gaeatech.com\/gaeasynergy.php\">GaeaSynergy Data Management<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/gaeatech.com\/gaeasynergy_import_export.php\">GaeaSynergy Import and Export<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/gaeatech.com\/knowledge-center\/gint-winlog-gaeasynergy-migration-plan-expanded\/\">From gINT to WinLoG and GaeaSynergy: A Practical Migration Plan<\/a><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Preserve your historical data. Simplify the transition. Move forward with GAEA&#8217;s Migration Center.<\/strong><\/p>\n\n\n\n<h1 id=\"h-preserve-valuable-geotechnical-data-simplify-migration-from-legacy-gint-databases-and-improve-data-exchange-between-gint-winlog-and-gaeasynergy\" class=\"wp-block-heading\"><em>Preserve valuable geotechnical data, simplify migration from legacy gINT databases, and improve data exchange between gINT, WinLoG, and GaeaSynergy.<\/em><\/h1>\n\n\n\n<h2 id=\"h-modernizing-geotechnical-data-without-losing-decades-of-work\" class=\"wp-block-heading\">Modernizing geotechnical data without losing decades of work<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For decades, Bentley&#8217;s gINT has been widely used by geotechnical engineers, geological consultants, transportation agencies, and environmental professionals to store subsurface investigation data and produce borehole logs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Many engineering organizations have accumulated hundreds or thousands of gINT project databases containing valuable historical information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These databases may include geological descriptions, soil and rock classifications, Standard Penetration Test (SPT) results, groundwater measurements, laboratory testing, well construction information, and other engineering data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As organizations modernize their software systems, preserving and reusing this information has become increasingly important.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>GAEA Technologies&#8217; new Migration Center simplifies the process of importing and exporting gINT project databases, helping organizations transfer existing subsurface information into WinLoG and GaeaSynergy while maintaining compatibility with supported gINT data structures.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The objective is not simply to copy records between databases. It is to make historical information accessible, reusable, and easier to manage within modern engineering workflows.<\/p>\n\n\n\n<h2 id=\"h-why-gint-data-migration-matters\" class=\"wp-block-heading\">Why gINT data migration matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">gINT has been an important part of the geotechnical software industry for many years.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Engineering firms have invested substantial time developing project databases, custom data fields, lookup tables, reporting conventions, and borehole log designs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In some organizations, historical gINT records represent decades of engineering experience.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Replacing these databases or manually recreating their information would be expensive and time-consuming.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The retirement of the gINT product line has also increased interest in alternative solutions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, migrating away from an established system presents several challenges:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Preserving existing borehole and geological information.<\/li>\n\n\n\n<li>Transferring project identification and location details.<\/li>\n\n\n\n<li>Maintaining relationships between data tables.<\/li>\n\n\n\n<li>Handling custom fields and user-defined data structures.<\/li>\n\n\n\n<li>Converting units and geological classifications.<\/li>\n\n\n\n<li>Reproducing essential borehole log information.<\/li>\n\n\n\n<li>Exchanging data with organizations that continue to use gINT.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These challenges are particularly significant for engineering companies with extensive historical project archives.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The new GAEA Migration Center provides a more structured approach to addressing them.<\/p>\n\n\n\n<h2 id=\"h-understanding-gint-project-databases\" class=\"wp-block-heading\">Understanding gINT project databases<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">gINT version 8 project databases typically use the <code>.gpj<\/code> file extension and are based on Microsoft Access database technology.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A gINT project database contains related tables that organize project information, borehole locations, geological intervals, field measurements, and laboratory test results.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Common categories of information include:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Project information:<\/strong> Project names, numbers, locations, clients, and other identifying details.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Point information:<\/strong> Borehole or well identifiers, coordinates, ground elevations, drilling dates, and total depths.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Lithology information:<\/strong> Soil and rock descriptions, geological intervals, sample depths, and formation information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Field testing:<\/strong> SPT results, groundwater observations, drilling information, and other measurements collected during investigations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Laboratory testing:<\/strong> Water content, grain-size distribution, Atterberg limits, and other geotechnical test results.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, not every gINT database uses identical table structures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations frequently modify their databases to accommodate project requirements, company standards, or government reporting specifications.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This flexibility makes gINT powerful, but it also means that successful migration requires more than simply copying database files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A reliable migration process must recognize the structure of the source database and determine how the information should be represented in the destination system.<\/p>\n\n\n\n<h2 id=\"h-introducing-gint-import-and-export-in-the-migration-center\" class=\"wp-block-heading\">Introducing gINT import and export in the Migration Center<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GAEA has supported gINT data exchange in earlier versions of WinLoG and GaeaSynergy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The new Migration Center builds on this experience by bringing migration workflows into a more centralized environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rather than relying on unrelated import tools, the Migration Center provides a dedicated starting point for working with supported external and legacy project data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For gINT databases, the workflow focuses on selecting source information, reviewing available data structures, configuring the required mappings, and transferring supported information into GAEA projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Migration Center also supports the broader goal of exchanging project information with other software environments through appropriate export workflows.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is important because software migration is not always a one-way process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some organizations may migrate entirely from gINT to WinLoG and GaeaSynergy, while others may need to exchange data with clients, subcontractors, or government agencies that continue to use gINT.<\/p>\n\n\n\n<h2 id=\"h-importing-gint-project-databases\" class=\"wp-block-heading\">Importing gINT project databases<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Importing existing gINT project information is one of the most important applications of the Migration Center.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The process allows organizations to reuse historical geotechnical and geological data without manually recreating each record.<\/p>\n\n\n\n<h3 id=\"h-step-1-select-the-gint-database\" class=\"wp-block-heading\">Step 1: Select the gINT database<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Begin by opening the Migration Center and selecting the appropriate gINT import option.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Choose the <code>.gpj<\/code> project database containing the information to be transferred.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The selected database provides the source information for the import process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before importing, it is good practice to retain an unchanged backup of the original database.<\/p>\n\n\n\n<h3 id=\"h-step-2-review-project-information\" class=\"wp-block-heading\">Step 2: Review project information<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The source database may contain project details such as project number, name, client, and location.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These details help identify the records being imported and associate them with the appropriate destination project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Where applicable, users can review the information before proceeding with the conversion.<\/p>\n\n\n\n<h3 id=\"h-step-3-review-tables-and-fields\" class=\"wp-block-heading\">Step 3: Review tables and fields<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most important stages of importing a gINT database is understanding its data structure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The database may contain standard tables together with additional fields created specifically for a company or agency.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A structured import workflow allows relevant tables and fields to be identified and associated with corresponding data types in the destination system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a gINT field containing SPT blow counts should be associated with the appropriate testing data rather than imported as an unrelated text field.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Similarly, geological interval depths must be interpreted correctly to preserve their relationships with soil and rock descriptions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fields without a direct equivalent may require additional configuration or may not be transferable through the selected workflow.<\/p>\n\n\n\n<h3 id=\"h-step-4-select-or-configure-the-log-template\" class=\"wp-block-heading\">Step 4: Select or configure the log template<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Borehole logs depend on both the underlying data and the template used to display it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When importing a gINT project, users can associate the transferred information with an appropriate WinLoG template.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the available import options, this may involve selecting an existing template or creating a template based on the source database fields.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The objective is to make imported information available for reporting without requiring engineers to manually reconstruct every borehole.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An important distinction is that a gINT project database and a gINT report library are not the same thing. Importing project data does not automatically guarantee reproduction of custom gINT report layouts.<\/p>\n\n\n\n<h3 id=\"h-step-5-complete-the-import-and-review-the-results\" class=\"wp-block-heading\">Step 5: Complete the import and review the results<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once the configuration has been established, the supported records can be imported into the GAEA project environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Following import, users should review representative boreholes and verify that critical information has been transferred correctly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Particular attention should be given to geological intervals, sample depths, test results, coordinates, units, and borehole identifiers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This review is essential when migrating customized databases or large historical datasets.<\/p>\n\n\n\n<h2 id=\"h-exporting-project-data-to-gint-databases\" class=\"wp-block-heading\">Exporting project data to gINT databases<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Although many organizations are moving away from gINT, exporting data to a supported gINT database remains valuable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Engineering firms often work with clients, consultants, and government agencies that have established data-delivery requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A project completed using WinLoG or GaeaSynergy may still need to provide its borehole information in a format compatible with an existing gINT workflow.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">GAEA&#8217;s gINT export capabilities support this type of data exchange.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A typical export process includes selecting the destination database, identifying the boreholes or wells to export, and specifying the project information and data fields to include.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The exported information must be mapped to the appropriate gINT tables and field structures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly important when transferring information to a customized database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a client may require borehole identification, geological intervals, SPT results, and groundwater observations to be organized according to a specific database structure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Using a configured export workflow can reduce the need for manual data transfer and help maintain consistency between projects.<\/p>\n\n\n\n<h3 id=\"h-why-exporting-remains-important\" class=\"wp-block-heading\">Why exporting remains important<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Retaining the ability to export supported gINT-compatible information provides several practical advantages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Client compatibility:<\/strong> Engineering firms can deliver data to clients who continue to use gINT.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Collaboration:<\/strong> Consultants using different software systems can exchange structured project information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Gradual software migration:<\/strong> Organizations can introduce WinLoG and GaeaSynergy without requiring every department or external partner to change software simultaneously.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Contractual requirements:<\/strong> Some government and infrastructure contracts may specify legacy database formats.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Data portability:<\/strong> Maintaining appropriate exchange options reduces dependence on any single application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Export support should not be confused with perfect round-trip conversion. Custom fields, report designs, attachments, and other specialized information must be checked for compatibility with the selected destination database.<\/p>\n\n\n\n<h2 id=\"h-example-migrating-a-historical-gint-project-archive\" class=\"wp-block-heading\">Example: Migrating a historical gINT project archive<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Consider a geotechnical engineering company with 20 years of historical investigations stored in gINT.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The company has accumulated approximately 1,500 project databases containing thousands of boreholes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Its engineers regularly refer to these records when preparing proposals, planning new drilling investigations, and reviewing previous projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, the company wants to adopt WinLoG and GaeaSynergy for future work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Re-entering all the historical information manually would require substantial time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, the company can develop a structured migration plan using the Migration Center.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The first step is to identify representative databases containing the different table structures and customizations used over the years.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These databases can be evaluated and imported into test projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The engineering team can then review the transferred information and confirm that important geological descriptions, test results, and project identifiers have been preserved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once the required mappings and procedures have been established, the organization can progressively migrate additional supported projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This approach reduces implementation risk by identifying conversion issues before they affect a large number of records.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It also allows the company to retain its historical gINT databases as original archives while developing a more modern environment for future engineering work.<\/p>\n\n\n\n<h2 id=\"h-using-imported-gint-data-in-winlog\" class=\"wp-block-heading\">Using imported gINT data in WinLoG<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After importing supported gINT data, engineers can use WinLoG to manage borehole information and prepare professional boring and well logs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly valuable for organizations that want to continue using historical data while standardizing their reporting procedures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical applications include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reviewing historical borehole descriptions.<\/li>\n\n\n\n<li>Preparing updated borehole log presentations.<\/li>\n\n\n\n<li>Applying company-standard log templates.<\/li>\n\n\n\n<li>Organizing field and laboratory information.<\/li>\n\n\n\n<li>Reviewing geological intervals and measurements.<\/li>\n\n\n\n<li>Applying applicable Validation and QA\/QC rules.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">One important benefit is the ability to distinguish between transferring existing information and improving how it is managed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An organization does not necessarily need to change the geological interpretation of a historical borehole simply because it adopts new software.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, it can preserve the original observations while making them easier to access, review, and present.<\/p>\n\n\n\n<h2 id=\"h-integrating-gint-information-with-gaeasynergy\" class=\"wp-block-heading\">Integrating gINT information with GaeaSynergy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GaeaSynergy provides an integrated environment for managing geological, geotechnical, environmental, and related project information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Importing gINT data into this environment can help organizations consolidate historical records with newer investigation data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a transportation engineering consultant may maintain historical gINT boreholes from highway investigations completed over many years.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">New projects can generate additional boreholes using WinLoG and other GAEA applications.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By bringing relevant historical information into GaeaSynergy, the consultant can work toward maintaining a more consistent project data environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly useful when investigations are repeated along the same highway corridors, at existing facilities, or within long-term infrastructure projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Historical records may contain valuable information about subsurface variability that would otherwise remain scattered across separate database files.<\/p>\n\n\n\n<h2 id=\"h-improving-data-quality-during-migration\" class=\"wp-block-heading\">Improving data quality during migration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Moving data from one software system to another presents an opportunity to review historical information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Older geotechnical databases may contain inconsistencies that were never identified when the records were originally created.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Missing borehole identifiers.<\/li>\n\n\n\n<li>Geological intervals with overlapping depths.<\/li>\n\n\n\n<li>Incomplete sample information.<\/li>\n\n\n\n<li>Invalid or inconsistent units.<\/li>\n\n\n\n<li>Missing coordinates or elevations.<\/li>\n\n\n\n<li>SPT results that do not match expected data conventions.<\/li>\n\n\n\n<li>Laboratory measurements recorded in unexpected fields.<\/li>\n\n\n\n<li>Inconsistent geological descriptions.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The new Validation and QA\/QC capabilities in WinLoG and GaeaSynergy complement the Migration Center by providing tools for reviewing applicable imported information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, imported lithological intervals may be checked for inconsistencies, and supported testing records may be evaluated against validation rules.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not every historical record will meet current reporting standards, and some data may require professional interpretation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nevertheless, identifying these issues during migration can improve the reliability and usefulness of the resulting project database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A successful database import confirms that information has been transferred. It does not independently confirm that the original measurements or geological observations were correct.<\/p>\n\n\n\n<h2 id=\"h-migration-is-more-than-file-conversion\" class=\"wp-block-heading\">Migration is more than file conversion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A common mistake when changing engineering software is to focus exclusively on whether a file can be opened in another application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For organizations with extensive historical records, successful migration requires a broader approach.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The original data must be preserved, important relationships must remain intact, unsupported information must be identified, and the new workflow must produce useful engineering results.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For this reason, organizations should begin large migrations with a representative pilot rather than immediately converting their entire archive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The pilot should include simple databases, highly customized databases, records containing a variety of field and laboratory test types, and examples with known data-quality issues.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Comparing source and destination results can help establish reliable acceptance criteria.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is also advisable to retain original databases and document the conversion process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This creates an audit trail and allows historical records to be revisited if questions arise.<\/p>\n\n\n\n<h2 id=\"h-supporting-a-gradual-transition-from-gint\" class=\"wp-block-heading\">Supporting a gradual transition from gINT<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Engineering organizations often adopt new technology gradually.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An established company may have long-standing project archives, experienced users, customized reporting procedures, and clients who continue to request gINT files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Attempting to replace every part of this workflow at once can create unnecessary disruption.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Migration Center supports a more practical transition strategy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations can begin by importing selected historical projects, configuring appropriate WinLoG templates, and verifying that critical data remains accessible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">New investigations can then be completed using GAEA software, while appropriate gINT export workflows help maintain compatibility with legacy requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Over time, more historical information can be migrated as project needs and available resources justify the effort.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This approach allows companies to modernize without abandoning the investments they have already made in data collection and management.<\/p>\n\n\n\n<h2 id=\"h-beyond-gint-a-broader-data-migration-solution\" class=\"wp-block-heading\">Beyond gINT: A broader data migration solution<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The GAEA Migration Center is not limited to gINT.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It forms part of GAEA Technologies&#8217; broader strategy for improving geological, geotechnical, and environmental data interoperability.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Other migration capabilities include supported legacy GAEA project conversions, government water well information, and industry data exchange formats such as AGS and DIGGS.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Together, these capabilities are intended to reduce the fragmentation of subsurface information across different applications and data structures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For engineering organizations, the long-term objective is to make historical data easier to preserve, transfer, validate, and reuse.<\/p>\n\n\n\n<h2 id=\"h-get-started-with-the-new-gaea-migration-center\" class=\"wp-block-heading\">Get started with the new GAEA Migration Center<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Existing geotechnical information represents a substantial investment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations should not have to abandon decades of borehole logs, geological descriptions, laboratory measurements, and project records simply because the software used to create them is being replaced.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>GAEA&#8217;s new Migration Center helps organizations import and export supported gINT project data while establishing a more consistent approach to managing historical subsurface information.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Whether the objective is moving from gINT to WinLoG, integrating historical data into GaeaSynergy, or exchanging information with clients who still use gINT, structured migration and export workflows can reduce repetitive work and improve data accessibility.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The result is a more practical path toward modern geotechnical data management while preserving the value of existing engineering records.<\/p>\n\n\n\n<h3 id=\"h-learn-more\" class=\"wp-block-heading\">Learn more<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Explore the following resources:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/gaeatech.com\/migration_center.php\">GAEA Migration Center<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/gaeatech.com\/winlog.php\">WinLoG Borehole Logging Software<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/gaeatech.com\/gaeasynergy.php\">GaeaSynergy Data Management<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/gaeatech.com\/gaeasynergy_import_export.php\">GaeaSynergy Import and Export<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/gaeatech.com\/knowledge-center\/gint-winlog-gaeasynergy-migration-plan-expanded\/\">From gINT to WinLoG and GaeaSynergy: A Practical Migration Plan<\/a><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Preserve your historical data. Simplify the transition. Move forward with GAEA&#8217;s Migration Center.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Preserve valuable geotechnical data, simplify migration from legacy gINT databases, and improve data exchange between gINT, WinLoG, and GaeaSynergy. Modernizing geotechnical data without losing decades of work For decades, Bentley&#8217;s gINT has been widely used by geotechnical engineers, geological consultants, transportation agencies, and environmental professionals to store subsurface investigation data and produce borehole logs. Many [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":93123,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[2038],"tags":[482,2073,2072,360,706,310,2071,2036,102],"class_list":["post-93122","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-data-migration","tag-borehole-data","tag-database-export","tag-database-import","tag-gaeasynergy","tag-geotechnical-data","tag-gint","tag-gint-migration","tag-migration-center","tag-winlog"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.5 (Yoast SEO v28.5) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>gINT Database Import and Export Simplified - Knowledge Center<\/title>\n<meta name=\"description\" content=\"Learn how to manage gINT database import and export for seamless data migration and preservation of geotechnical information.\" \/>\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\/gint-database-import-export-migration-center\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Importing and Exporting gINT Databases with GAEA&#039;s New Migration Center\" \/>\n<meta property=\"og:description\" content=\"Learn how to manage gINT database import and export for seamless data migration and preservation of geotechnical information.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/\" \/>\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-10-23T01:33:59+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-23T01:34:03+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/10\/gint-database-import-export-gaea-migration-center.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1672\" \/>\n\t<meta property=\"og:image:height\" content=\"941\" \/>\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=\"23 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/\"},\"author\":{\"name\":\"GAEA Technologies\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/940fb5fed6e95dd9d0ec1370207f5dba\"},\"headline\":\"Importing and Exporting gINT Databases with GAEA&#8217;s New Migration Center\",\"datePublished\":\"2026-10-23T01:33:59+00:00\",\"dateModified\":\"2026-10-23T01:34:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/\"},\"wordCount\":5083,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/gint-database-import-export-gaea-migration-center.jpg\",\"keywords\":[\"Borehole Data\",\"Database Export\",\"Database Import\",\"gaeasynergy\",\"geotechnical data\",\"gINT\",\"gINT Migration\",\"Migration Center\",\"WinLoG\"],\"articleSection\":[\"Data Migration\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/\",\"url\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/\",\"name\":\"gINT Database Import and Export Simplified - Knowledge Center\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/gint-database-import-export-gaea-migration-center.jpg\",\"datePublished\":\"2026-10-23T01:33:59+00:00\",\"dateModified\":\"2026-10-23T01:34:03+00:00\",\"description\":\"Learn how to manage gINT database import and export for seamless data migration and preservation of geotechnical information.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/#primaryimage\",\"url\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/gint-database-import-export-gaea-migration-center.jpg\",\"contentUrl\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/gint-database-import-export-gaea-migration-center.jpg\",\"width\":1672,\"height\":941,\"caption\":\"Import and export gINT project databases using GAEA's Migration Center to transfer geotechnical data between gINT, WinLoG, and GaeaSynergy.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/gint-database-import-export-migration-center\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/gaeatech.com\\\/knowledge-center\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Importing and Exporting gINT Databases with GAEA&#8217;s New Migration Center\"}]},{\"@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\":1920,\"height\":1080,\"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\"]}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"gINT Database Import and Export Simplified - Knowledge Center","description":"Learn how to manage gINT database import and export for seamless data migration and preservation of geotechnical information.","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\/gint-database-import-export-migration-center\/","og_locale":"en_US","og_type":"article","og_title":"Importing and Exporting gINT Databases with GAEA's New Migration Center","og_description":"Learn how to manage gINT database import and export for seamless data migration and preservation of geotechnical information.","og_url":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/","og_site_name":"Knowledge Center","article_publisher":"https:\/\/www.linkedin.com\/company\/2663277\/","article_published_time":"2026-10-23T01:33:59+00:00","article_modified_time":"2026-10-23T01:34:03+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/10\/gint-database-import-export-gaea-migration-center.jpg","type":"image\/jpeg"}],"author":"GAEA Technologies","twitter_card":"summary_large_image","twitter_misc":{"Written by":"GAEA Technologies","Est. reading time":"23 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/#article","isPartOf":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/"},"author":{"name":"GAEA Technologies","@id":"https:\/\/gaeatech.com\/knowledge-center\/#\/schema\/person\/940fb5fed6e95dd9d0ec1370207f5dba"},"headline":"Importing and Exporting gINT Databases with GAEA&#8217;s New Migration Center","datePublished":"2026-10-23T01:33:59+00:00","dateModified":"2026-10-23T01:34:03+00:00","mainEntityOfPage":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/"},"wordCount":5083,"commentCount":0,"publisher":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/#organization"},"image":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/#primaryimage"},"thumbnailUrl":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/10\/gint-database-import-export-gaea-migration-center.jpg","keywords":["Borehole Data","Database Export","Database Import","gaeasynergy","geotechnical data","gINT","gINT Migration","Migration Center","WinLoG"],"articleSection":["Data Migration"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/","url":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/","name":"gINT Database Import and Export Simplified - Knowledge Center","isPartOf":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/#website"},"primaryImageOfPage":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/#primaryimage"},"image":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/#primaryimage"},"thumbnailUrl":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/10\/gint-database-import-export-gaea-migration-center.jpg","datePublished":"2026-10-23T01:33:59+00:00","dateModified":"2026-10-23T01:34:03+00:00","description":"Learn how to manage gINT database import and export for seamless data migration and preservation of geotechnical information.","breadcrumb":{"@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/#primaryimage","url":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/10\/gint-database-import-export-gaea-migration-center.jpg","contentUrl":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/10\/gint-database-import-export-gaea-migration-center.jpg","width":1672,"height":941,"caption":"Import and export gINT project databases using GAEA's Migration Center to transfer geotechnical data between gINT, WinLoG, and GaeaSynergy."},{"@type":"BreadcrumbList","@id":"https:\/\/gaeatech.com\/knowledge-center\/gint-database-import-export-migration-center\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/gaeatech.com\/knowledge-center\/"},{"@type":"ListItem","position":2,"name":"Importing and Exporting gINT Databases with GAEA&#8217;s New Migration Center"}]},{"@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":1920,"height":1080,"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"]}]}},"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/gaeatech.com\/knowledge-center\/wp-content\/uploads\/2026\/10\/gint-database-import-export-gaea-migration-center.jpg","_links":{"self":[{"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/posts\/93122","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=93122"}],"version-history":[{"count":1,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/posts\/93122\/revisions"}],"predecessor-version":[{"id":93124,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/posts\/93122\/revisions\/93124"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/media\/93123"}],"wp:attachment":[{"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/media?parent=93122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/categories?post=93122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gaeatech.com\/knowledge-center\/wp-json\/wp\/v2\/tags?post=93122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}