I second what the other commenters have said.

There are several factors at play making conflicts almost impossible:

- A central device can be immediately synced to. For Nextcloud, it could be a server, for direct synchronization that I use (Syncthing), my phone (almost always online) is the intermediate device for all.

- You are usually online when creating accounts/password, so an sync can happen directly after a change

- And finally: How often do you actually _create_ accounts rather than just read the database? And how often do you do it on two devices in quick succession?

I've never seen this happen, because (as far as I can tell) all KeePassXC clients auto-save the file any time a change is made, and all the Nextcloud clients auto-sync as soon as the file changes. Keepass is also resilient to the underlying file changing while you have, say, the edit password dialog open.

If a conflict did happen though, newer versions of Nextcloud just keep both copies and alert you to resolve it. If I had to resolve this I'd probably try the built-in database merger first: https://keepassxc.org/docs/KeePassXC_UserGuide#_merging_data...

Merge conflicts on NextCloud are terrible, but for a KeePass file, I don't think this comes up very much. My laptop syncs from Nextcloud whenever it's online, and my phone syncs whenever it opens or modifies the file. Nobody else is using my laptop or phone, and certainly not my keepass vault. I would probably have to go out of my way to use both my laptop and my phone offline and add/change passwords during that time in order to get a merge conflict.