Thanks, @matt
Those steps make sense, even if it is a bit painful. I’ll probably commit to the process at some point when I can set aside enough time for it. Initially I thought the gap would only be a handful of days that I could just ignore, but the repair ended up taking longer than expected, and unfortunately those weeks include some more interesting movement days, hence I’d quite like to recover them properly.
Before I go down the full Codex merge route, do you think it still makes sense to try the “conventional” import approach once, just to see what happens? Or is your expectation that importing those 3 weeks into the current database will very likely create a mess that is hard to recover from afterwards?
I was also wondering about one other route, though I suspect it probably runs into the same issue: using JSON export for individual days, then converting those files into importer format using the script discussed here:
https://support.bigpaua.com/t/json-import-format/219/17
No, that wouldn’t help, since it would still end up going through the same importer / timeline processing path, right?
But one more thought: what about GPX timeline export / import? I’ve used the GPX import before for flight paths, and that seemed able to import over existing data. But GPX might be too simplicstic and too much just route geometry instead of a valid timeline restore?
Thanks again and yes, if I go for the full process, I’ll probably come back with questions.