Do you SYNCHRONIZE keepass kdbx files between Windows & Android?

It seems there are two completely different tasks inside KEEPASS:
1. Synchronization (this does not work the way I thought it worked)
2. Import (this seems to replace the entire file, I think)

I'm still formalizing my strategy for keeping my personal data off the net,
where passwords are good since Keepass works on all platforms.

Mainly (but not always), I edit on the desktop (using a keyboard),
but _sometimes_ I find myself, on the road, adding a password on the phone.

Up until now, I've been using "IMPORT" where the general use model was:
a. Edit the "master" passwd file on the Windows desktop
b. Import that "master" desktop passwd file en masse into Android

But recently, I added a passwd on the mobile device, and then had to get
that back into the desktop master passwd kdbx database.

But when I tried to synchronize the mobile device kdbx into the Wineows,
desktop, the desktop Keepass didn't take anything from the phone.
o How do you successfully import & merge & overwrite multiple keepass.kdbx files between Windows & Android?
https://groups.google.com/forum/#!topic/comp.mobile.android/y7CWoAunIOY

So how do we best synchronize data that was added on the phone?

Notice there is a SYNCHRONIZE command on the Windows KeePass:
o KeePass Password Safe, Windows 10, version 2.39.1)
https://sourceforge.net/projects/keepass/files/KeePass%202.x/2.39.1/KeePass-2.39.1-Setup.exe/download

But there is not a synchronize command I can find on the Android Keepass.
o Keepass2Android
https://play.google.com/store/apps/details?id=keepass2android.keepass2android

Given that oddity, I think this will be my MAIN use model, moving forward:
a. Add/change password on the "master" desktop kdbx
b. On Android - IMPORT that "master" desktop kdbx

Once in a while, this will be my SECONDARY use model, moving forward:
a. Continue to add/change passwds on the "master" desktop kdbx
b. Once in a while, add/change passwds on the "mobile" kdbx
c. On the desktop, SYNCHRONIZE the "mobile" kdbx with the "master" kdbx

The main caveat to that synchronize step is that I have to ensure that the
DATE STAMP on the mobile kdbx is at a LATER date than the date stamp of the
"master" kdbx, which I can do with a simple "touch" command process on the
desktop.

Seems silly to have to change the date stamp - but the synchronize on the
desktop did not work until I changed the date stamp on the mobile kdbx.

Anyone else experience this problem with the Windows SYNCHRONIZE command
when they added a password on the mobile device but when they ALSO had
added passwds on the Windows device such that the Windows datestamp was
NEWER than the Android datestamp?