Sorry, but with every new major release the migration topic comes up again, so here the situation:
I have now installed the officially released DTTG4 app and activated my license without any issues. All my data (more than a dozen GB) appeared very quickly in DTTG4, which makes me think that the databases were not copied over, but that the new app is still referencing the old data from DTTG3.
Now when deleting the old DTTG3 app, iOS asks whether I also want to delete the associated data.
My question is: What is the correct procedure here to ensure that DTTG4 keeps all my data, but I also avoid storing duplicate data on the device?
Should I keep or remove the data when deleting DTTG3?
so I definitely haven’t seen any migration instructions, the reply, to my knowledge, only came after the blog post.
So I deleted DTTG3 from my phone first, and then installed DTTG4. The app had no data, so I added iCloud sync from scratch…it took a while to sync, but now DTTG4 has my groups and documents.
It would have been helpful to know in advance, that the correct order is to keep the DTTG3, install DTTG4 so it “carries over” the databases and only then delete DTTG3.
but now everything is fine, and the new version of the app is very nice! thanks again to the developer team
When one removes an app, iOS always deletes the app’s data, and it also says so when it asks if it shall proceeds. Only when some other app has “a grip” on the data, like DEVONthink To Go 4 has on the data shared with version 3, the data is not deleted.
You kann safely choose Delete data as the shared data of DEVONthink To Go 3 and 4 is only removed if neither of the apps is present. As @eboehnisch mentioned, as long as one app has a grip on the data, it won’t be removed.
Just be sure to install the latest build of V3, then open V4 so the migration happens and only after that remove V3.
So I assume that if I have installed DTTG4 first, and only then have removed DTTG3 — all my data would have been migrated? But the iCloud sync would still need to be set up in the DTTG4, right? Because the encryption key is not transferred?
I can confirm that I safely deleted DTTG3, selected “Yes” when iOS asked whether to delete the associated data, and all my databases are still fully available in DTTG4.
Automatic migration from DTTG3 to DTTG4 does more harm than good.
I have DTTG3 with several WebDAV sync locations. The locations weren’t migrated to DTTG4 and I worked for some time only on a local data not being aware that there is NO synchronisation to the store on a NAS.
Without this half-backed convenience I would have to take care myself and probably went your way (remove DTTG3, install DTTG4, sync from scratch), and not to count on the app.
My setup is definitely much less involved than yours, last night I’ve successfully installed DTT4 on my iPad and the databases and iCloud sync have been successfully migrated from DTTG3.
so for iPhone I did all that manually, and iPad it was automatically migrated. All works now.
Definitely! I’m using DTTG3 every day for I do not remember how long and I am updating the version very soon any update show up.
I think I had similar problem in the past with some other migration and the result was the same. It looks like WebDAV synchronisation is not a priority in moving/upgrading to a new version.
What I could recommend for the future is what I am using in my software - no matter how good developers and QAs are, when I’m using their code (e.g. API) I’m using their PUT/POST and I’m then use GET and compare field by field if everything was done correctly. May look like overkill but can’t count how many times I’ve caught something wrong.
In this situation I would say “take old config, take new config, compare field by field thoroughly, report to the user any suspicious things”.
Saying all of that I’m unwavering eulogist of DT And I will of course manage to clean up the things myself. I just need some time, no problem.
I was always impressed how well synchronisation in DT is done (i.e. solid and reliable). The thing with migrating to DTTG4 is kinda very rare exception to the high standards.