> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/importing-data/cross-database-object-copying.md).

# Cross-Database Object Copying

GeoDin can move objects between databases without exporting flat files: you can copy boreholes directly from one connected database into another, package a selection as a portable GeoDin Access database, and convert older-standard objects to the current standard as part of the copy. This page covers connecting the source and target databases, the copy and publish/export commands, and the SEP 1 -> SEP 3 conversion option.

## Database Connections & File-Based Migration

Database connections are created via `Create Database Connection` - choose database type (e.g. Microsoft Access), then either link an existing file or create a new one from scratch.

Access database files can be created locally or on a shared network drive.

Existing Access databases can be added to GeoDin by drag-and-dropping the `.mdb` file into the left-hand tree - this auto-creates the connection.

Right-click on a database connection > `Edit Database Connection` to view or change the stored path.

Demo databases ship with GeoDin installations under a `demos` subfolder in the configuration folder; they appear yellow in the connection list (user-created databases appear blue).

gINT (`.mdb`) databases are referenced as the historical predecessor format - users migrating from gINT must use import routines rather than direct file linking.

## Cross-Database Object Copying & Publish/Export

Objects (boreholes) can be duplicated - creates a full copy.

The `Publish and Export` command at the project level exports selected objects as a zip file containing a GeoDin Access database - useful for extracting a group of boreholes from an existing database.

`Publish and Export` is also available at the individual borehole level; produces a single-borehole Access database that can be re-imported elsewhere.

Cross-database object copying: via `Add Objects` at the project level, users can select boreholes from another (already connected) database and import them into the current project - preserves measurement data and general data.

Options during cross-database copy include: include/exclude attached documents, include/exclude measurement values, location-only copy (just names and general data).

Borehole log properties (layer data) can be copied from one borehole to another, even across databases, via `Copy Borehole Log` - layers are transferred but some standard-specific codes may not translate automatically.

## Converting SEP 1 Objects to SEP 3 During Copy

When copying SEP 1 objects from one database into another using **Add Objects**, a conversion option appears at the bottom of the copy dialog: **Conversion SEP 1 -> SEP 3** (German: *Konvertierung von SEP 1 nach SEP 3*).

### How to use it

{% stepper %}
{% step %}

#### Step 1: Open the Add Objects dialog

Open the **Add Objects** dialog on the target project.
{% endstep %}

{% step %}

#### Step 2: Add the SEP 1 objects

Drag the SEP 1 objects from the source database into the **List of objects**.
{% endstep %}

{% step %}

#### Step 3: Enable the conversion

At the bottom of the dialog, check **Conversion SEP 1 -> SEP 3**.
{% endstep %}

{% step %}

#### Step 4: Copy and confirm

Choose **Copy** and confirm.
{% endstep %}
{% endstepper %}

### What to check after the copy

GeoDin displays a protocol log on completion. Review this log carefully:

* Successfully transferred layers are listed with their mapped codes.
* Abbreviations (Kürzel) that could not be matched to a SEP 3 code are not discarded - they are written into the **comment/remarks field** (Kommentarfeld) of the target SEP 3 record for manual review.

{% hint style="warning" %}
This conversion is one-directional only: **SEP 1 -> SEP 3**. There is no built-in conversion from SEP 3 back to SEP 1 in GeoDin. Always review the protocol log and the comment fields of imported objects to catch any unmatched abbreviations.
{% endhint %}

For importing SEP 3 data delivered by a state authority, see [Importing SEP 3 data via the exchange database](/importing-data/sep3-exchange-database.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.geodin.com/importing-data/cross-database-object-copying.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.