Tickets backup for another OTRS instance

[altronrain]

Hello!
I'm interested in finding a way to backup tickets only from one OTRS instance (that is prod solution) to Test-OTRS instance (where were implemented a bunch of changes to many aspects including queues, services, sla, acl, ga, dynamic_fields..e.t.c) and how risky is to do such thing?
I don't want to make all the changes from test-OTRS to prod by hands (again). But available options only [fullbackup & notfullbackup (what's the difference between them?) + dbonly]. Dbnly also contains queue, service, sla, ga e.t.c info so I can't use it.
Are there any solutions? Or, perhabs, list of tables that should be dumped to backup/restore tickets only? (Also it would be great option to use 'from the box' community-edition distribution)

[zzz]

Hey,

Exporting and importing tables from two different systems can really mess up the data integrity.

You're almost always better of copying your settings from one system to the other, sorry.
Be aware that you can export/import the system configuration and ACLs, which should help you a little bit.

Best regards
Emin

[altronrain]

Ough. Okay. I understand.
Yesterday I tried Import/Export addition but it couldn't install properly, so I gave up this idea.

[root]

Yesterday I tried Import/Export addition but it couldn't install properly, so I gave up this idea.

Hi,

If the ImportExport add-on could help, I'm pretty sure zzz would have mentioned it. This is only about importing or exporting ConfigurationItems.

- Roy