Move Project Data In and Deliver It Out with Control

Exchange projects, boreholes, wells and GIS information with structured formats, then prepare tables and presentation outputs for the people who need them.

Choose the exchange level first, map the content deliberately and validate the result before it becomes authoritative project data.

XML, AGS, DIGGS

gINT and legacy projects

Import and map

GaeaSynergy Project Database

Select and export

XML, AGS, DIGGS and gINT

GIS, Excel and reports

Match the Workflow to the Intended Result

Not every output is a round-trip data exchange. GaeaSynergy supports several distinct ways to move or deliver information:

Exchange structured data with another application or project team
Migration moves legacy GAEA projects into the current platform
GIS export delivers selected spatial layers
Reporting output presents tables, figures and project information for review

Important: A file that imports successfully is not automatically complete or semantically correct. Review mappings, units, coordinates, identifiers and interval relationships before accepting the imported data.

Choose the Right Exchange Level

Use the narrowest transfer that preserves the information required by the destination.

Whole Project

Transfer a GaeaSynergy project with the XML Exchange format when the destination needs the connected project package.

Boreholes and Wells

Exchange selected investigation records through supported XML, AGS, DIGGS or mapped gINT workflows.

GIS Layers

Export selected project layers for use in common GIS and CAD-oriented spatial formats.

Tables and Reports

Deliver selected summaries, tables and presentation outputs when editable project data is not required.

Supported Import and Export Workflows

Availability can depend on the installed modules, selected data, format version and destination requirements.

Workflow	Typical scope	Direction	Use it for
GaeaSynergy Project XML	Whole project	Import / Export	Moving a connected GaeaSynergy project between installations or controlled project stores.
Log and Template XML	Selected borehole, well, template or cross-section content	Import / Export as applicable	Exchanging defined GAEA logging and interpretation content without moving the entire project.
AGS 3 and AGS 4	Geotechnical and geoenvironmental investigation data	Import / Export	Standards-based delivery where the agreed AGS version, groups and field mappings are known.
DIGGS	Borehole and investigation data	Import / Export	Structured geotechnical and geoenvironmental data exchange using the applicable DIGGS schema.
gINT version 8 (.gpj)	Mapped project, point, sample, dataset and CPT information	Import / Export	Transferring selected boreholes and wells with reusable table and column mappings.
GIS Layers	Selected spatial project layers	Export	Creating ArcView Shape, MapInfo Interchange or AutoCAD DXF deliverables.
Excel Tables	Selected project and sampling summaries	Export	Review, tabulation and downstream reporting outside the project database.
Legacy GAEA Databases	WinLoG, WinFence and WinSieve projects	Import	Migrating selected legacy projects and records into GaeaSynergy.

Confirm before delivery: Exact fields, groups, code lists and supported schema versions must be agreed with the receiving organization. Attachments, images and proprietary presentation settings may require separate handling.

A Controlled Exchange Workflow

Use traceable mappings and a review step for both incoming and outgoing data.

Define the Destination

Confirm the purpose, format, schema version, required records, coordinate reference and units.

Preserve the Source

Keep an unchanged source copy and record the source system, export date and project scope.

Map the Data

Match source tables, fields and datasets to GaeaSynergy data types or the destination schema.

Test a Representative Set

Use a staging project or a small selection containing intervals, samples, results and edge cases.

Validate the Result

Review totals, identifiers, coordinates, depths, units, nulls, codes, qualifiers and unmapped content.

Archive the Exchange

Retain the delivered file, mapping or script, exceptions and acceptance record with the project.

Validate Meaning, Not Only File Structure

A technically valid file can still contain incorrect relationships or assumptions. Review the imported or exported dataset in the context of the project.

Unique project, location, sample and result identifiers
Coordinate system, datum and elevation reference
Depth direction, interval boundaries and measurement units
Null, blank, zero and below-detection-limit meanings
Result qualifiers, methods and laboratory references
Code lists and destination-controlled values
Template and data-type mapping
Rejected, truncated or unmapped content

Recommended Acceptance Check

Compare a representative record in the source, GaeaSynergy and the delivered file.

Count projects, locations, samples and results
Review shallow, deep and overlapping intervals
Confirm coordinates on a known basemap
Check units and converted values
Inspect notes, special characters and long text
Re-import critical exports when practical
Document accepted exceptions

Import and Export Resources

Use the product page for planning and the current guides for format-specific procedures.

Data Management Guide

Review how import and export support connected GaeaSynergy project data.

Read the overview

AGS Exchange

Review the supported workflow for importing and exporting AGS investigation data.

Open the AGS guide

gINT Exchange

Learn how tables, columns and records are mapped for gINT version 8 project databases.

Open the gINT guide

Project XML

Review the procedure for exporting the open GaeaSynergy project to an XML Exchange file.

Open the project XML manual

GIS Export

Review layer selection and the available Shape, MapInfo Interchange and DXF outputs.

Open the GIS export manual

Related Capabilities

See how exchanged information is organized and used within the platform.

Explore Data Management
Explore the GIS

GaeaSynergy Import and Export