Migration
Migrate from the combined otobo-znuny / otobo_znuny client to separate otobo and znuny packages.
Migration from the combined client — OTOBO
Version 2.0 splits the monolithic client into product-specific SDKs while keeping compatibility imports. For OTOBO integrations, use the dedicated otobo package.
Recommended imports
| Before (deprecated) | After (OTOBO) |
|---|---|
from otobo_znuny.clients.otobo_client import OTOBOZnunyClient | from otobo import OTOBOClient |
from otobo_znuny_python_client import OTOBOZnunyClient | from otobo import OTOBOClient |
OTOBOError | from otobo import OTOBOError |
Compatibility window
These continue to work in 2.x but are deprecated:
otobo_znuny.*otobo_znuny_python_client.*- Combined CLI command
setup-otobo-znuny-system
CLI changes
| Legacy | New |
|---|---|
| Combined auto-detect CLI | otobo-cli |
setup-otobo-znuny-system | otobo-cli setup-system |
Shared internals
REST models, mappers, and the async client implementation live in otrs_gi_core. Application code should import via otobo unless you maintain connector code.
Running Znuny instead of OTOBO? See the Znuny migration guide — use pip install znuny, not otobo.