OTRS to GOTRS Migration Guide
This guide covers options for migrating from OTRS to GOTRS.
Migration Options
Option 1: Connect to Existing OTRS Database (Simplest)
Point GOTRS at your existing OTRS database server. This avoids any data migration:
- Configure GOTRS database connection to use your existing OTRS MySQL/PostgreSQL instance
- GOTRS is schema-compatible with OTRS Community Edition
- Point GOTRS attachment storage at your OTRS file store
- Users can authenticate against OTRS directly or be migrated
Advantages:
- Zero data migration
- Instant cutover
- No risk of data loss
Option 2: Dump and Load
- Dump OTRS database:
mysqldump otrs_db > otrs_backup.sql - Restore to new MariaDB/MySQL or PostgreSQL database
- Copy attachment files to GOTRS storage location
- Run database migrations if needed
Option 3: Use GOTRS Migration Tool
GOTRS includes migration tooling via Makefile targets (run from the gotrs-ce directory):
# First, analyze your OTRS dump to see what will be migrated
make migrate-analyze SQL=/path/to/otrs_backup.sql
# Dry run - preview the import without making changes
make migrate-import SQL=/path/to/otrs_backup.sql DRY_RUN=true
# Import the data
make migrate-import SQL=/path/to/otrs_backup.sql
# Force import (skip confirmations)
make migrate-import-force SQL=/path/to/otrs_backup.sql
# Validate the migration
make migrate-validate
Note: These tools run inside the toolbox container with access to your database. Always test with a backup first!
Prerequisites
- OTRS 6.x or later
- Database access (MySQL or PostgreSQL)
- File system access to OTRS attachments
- Docker/Podman for GOTRS
Getting Help
- Community Chat: Join our Discord
- Professional Migration: Contact Gibbsoft Ltd