Are multiple runs of OTRS migrator possible - maybe with yearly migrate runs?

[xeno]

@MrGeneration & @anon29869905 my biggest issue is that I do not have any correlation possibility.
The logfile of the importer does not have even a timestamp, so I am getting an error and I have no idea where to look in OTRS since not even a timestamp is available.
So this feature

Feature-Request: Timestamp or some other correlationID required

I can’t see any remarks about the correlationID in the logs. Can you tell me where it comes from? on multi-systems debugging via log you need something to correlate the log messages. The simpliest one is a timestamp in the logs. This is missing in the migrator. The better one is to have UUIDs on both sides, so you clearly identify errors independently if you have tons of parallel threads on any system. What I see in the logs is that your OTRS takes to long to answer that HTTP POST request: …

would be very helpful to get responses from admins.
Afaik rails has a default logging mechanism, which can be configured with a: log formatter
Where can I activate it? And why are the timestamps missing?

The other thing is, that the import fails after about 2-4 h not after days.
To make this more transparent, how long my migration may take, this feature is crucial:

Feature-Request: Simple import progress report

A progress update would be great in the OTRS migrator. Afaik a very simple one would do already a great job: fetch total count of articles from OTRS on start update on every batch (otrs.rb variable “limit”) the processed articles in the form x / processed it would make the life much easier for admins to extrapolate how long the migration will take.

And this feature would help to be able to grep/sed easily the logfiles, if the logging would be consistent:

Feature-Request: Improve log output of migrator

The log output of the migrator uses a bunch of quote chars, which corrupt the output on pasting in this forum. Feature-Request to use double or single quotes to eliminate bad formatting here and of course to make the logfile parseable with other tools. E.g. this chars are used and also not consistently: ’ ` " here the original log output (only copy and pasted) thread#1: loading 20 Ticket starting at 56480... thread#1: POST: https://otrs.example.com/otrs/public.pl?Action=ZammadMigrator thre…

Since I have already exceeded massively my planned effort for the migration, I have deferred my migration plans already. I will post my faced issues combined soon here.

best wishes