> 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/geodin-desktop/es/integraciones-y-complementos/introduction.md).

# Convertidor de gINT

## Fácil migración de gINT a GeoDin

GeoDin ofrece una transición fluida de gINT con su potente convertidor integrado de gINT, para que pueda migrar fácilmente su gINT **Proyecto**, **Litología**, **Punto**, y **Muestra** datos de gINT a GeoDin.

El Proceso consta de dos pasos clave:

1. Convertir caracteres: su Base de datos gINT o Base de datos Access a GeoDinML, que puede importarse en GeoDin. Los Campos de datos se comprueban y emparejan (Todo); cualquier anomalía quedará Marcado para el Usuario (Cualquiera)
2. Importar el archivo GeoDinML en GeoDin.

Cuando en el Paso 1 falte algún Campo necesario, como tablas de Base de datos o Parámetros, GeoDin proporcionará comentarios y los elementos obligatorios faltantes quedarán Marcado.

**Formatos de soporte**: .mdb, .gpj, .accdb **Estándar**: ASTM D2487, soporte BS próximamente

Continuar Sobre, en la Hoja siguiente para seguir Paso a paso.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.geodin.com/geodin-desktop/es/integraciones-y-complementos/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.