Data export and switching
This register describes the structures and formats currently available for exporting customer-related data from Hafenmeister and the regular process for switching providers.
Standard package
Protected ZIP archive
Structured data
CSV or JSON
Files
Existing original format
Regular transition period
Up to 30 calendar days
A specific export only contains data that exists for and is enabled for the respective customer. Individual contractual terms and mandatory legal requirements take precedence over this general technical overview.
Exportable data structures
The following list represents the logical data domains of the standard export. Relationships between objects are represented by documented identifiers. Where available, creation and modification timestamps and customer-specific assignments are included.
Customer and configuration
JSONCustomer settings, enabled configuration values, notification and export settings
Logical structure: Configuration objects and key-value assignments
Users, roles and organisation
CSVJSONUser master data, roles, permission scopes and organisational assignments
Logical structure: User, role and assignment objects
Vessels, ports and berths
CSVJSONCustomer-specific master data, dimensions, ports, berths and reference assignments
Logical structure: Master-data objects with documented relationships
Voyages and itineraries
CSVJSONVoyages, periods, port sequences, passages, berth plans, comments and import metadata
Logical structure: Voyage objects with ordered itinerary entries and assignments
Organisational route planning
JSONStored origin and destination information, planning parameters and customer-related results
Logical structure: Route-planning objects and related result data
Excursions
CSVJSONExcursion master data, port and voyage assignments, descriptions, status and planning information
Logical structure: Excursion objects and assignment tables
Crew planning
CSVJSONCrew master data, contact and employment data, document information and voyage, vessel and assignment links
Logical structure: Crew, assignment, document and relationship objectsfiles separately
Files and documents
Original formatCustomer-uploaded files, document metadata, descriptions and object assignments
Logical structure: File directory plus machine-readable metadatametadata as CSV or JSON
AI chat and assistance tools
JSONStored chat sessions, user inputs, outputs, ratings and visible metadata
Logical structure: Session and message objects
Communications and activity data
CSVJSONNotifications, customer-related reports, business change states and visible usage metadata
Logical structure: Message, status and activity objects
Other customer-generated module data
CSVJSONOther existing inputs, outputs and metadata from modules enabled for the customer
Logical structure: Module-dependent objects with a data dictionary
Export package structure
The standard export package is provided through a protected retrieval channel. Its exact structure may vary with the enabled modules and is documented within the package.
hafenmeister-export.zip
Manifest
Version, creation timestamp, included data domains and verification information
Structured data
Separate CSV or JSON files for each data domain
Files
Uploaded documents in their existing original file format
Data dictionary
Description of supplied files, fields, data types, identifiers and relationships
Notes
Known limitations and any required mapping information
Formats, standards and interoperability
Character encoding and time values
Text data is provided as UTF-8. Where technically available, date and time values are supplied in a documented ISO 8601-compatible format.
CSV
Tabular data contains a header row. Delimiters, escaping, date representation and empty values are described in the export data dictionary.
JSON
Hierarchical data is provided as UTF-8 encoded JSON. Object relationships are represented by documented identifiers or embedded assignments.
Interfaces
The standard export is the regular switching method. Contractually enabled APIs may support integrations but do not automatically replace the complete export package. Scope and documentation are provided for the respective enablement.
Open interoperability specifications
Beyond the generally used formats and standards listed here, no product-specific open interoperability specification is currently used for the standard export. Relevant new harmonised standards or common specifications will be added in a future version when applicable.
Regular switching process
The exact process is governed by the contract and applicable mandatory law. The regular process is intended as follows:
- 01
Switching request
The customer identifies the intended destination provider or on-premises ICT infrastructure, authorised recipients and a secure transfer channel in text form.
- 02
Coordination
TNG acknowledges receipt, verifies authorisation and scope and coordinates the required technical information. The maximum notice period for initiating the process is two months.
- 03
Export and handover
The standard export package is generally provided within the regular transition period of no more than 30 calendar days. If this is technically impossible, the contractual and statutory notification and extension rules apply.
- 04
Retrieval and completion
After the transition period, the package remains retrievable for at least 30 calendar days. It is then deleted according to contractual periods and regular backup cycles unless a retention obligation applies.
Excluded data and known restrictions
In particular, the following internal or legally restricted content is not included in the standard export:
- Source and object code, internal documentation, algorithms, system instructions and calculation logic
- Passwords, hashes, API keys, access tokens, private keys and other authentication secrets
- Internal architecture, infrastructure, security, diagnostic and monitoring data
- Data of other customers or persons where no lawful disclosure right exists
- Third-party, reference, map or geodata where licence terms or intellectual property rights prevent transfer
- Temporary caches, technical intermediate results and fully anonymised statistics without a customer reference
Modules under development
Data structures and export formats of modules that have not yet been released for production may change until release.
Target system
Import, transformation, business mapping and identical presentation in the target system are not part of the standard export unless an additional migration service has been agreed.
Volume and complexity
Large file collections, technically complex relationships or required security checks may affect the transfer channel. Applicable maximum periods remain unaffected.
Request an export or provider switch
Please send export and switching requests to the contractual and privacy contact below. Include the customer, desired scope, authorised recipients and, where available, the destination provider.
This page is a technical information register and does not independently amend existing contracts. The respective contract, applicable data protection requirements and mandatory law remain authoritative. Regulation (EU) 2023/2854 (Data Act)