Couchbase Lite upgrade from community edition to enterprise edition

We use Couchbase.Lite (2.0.3) community edition at present in our .NET Core project. Now we would like to upgrade to Couchbase.Lite.Enterprise 2.5.0. Would it affect the already existing local couchbaselite database at client systems? Also, please guide what are the things we need to take care of before/after upgrading to the enterprise edition. Does it require any .NET code changes?
We use Couchbase Server 6.0 Enterprise in our cloud environment.

The only thing to note with Couchbase Lite 2.5 is that a database opened or created by 2.5 can’t be opened by 2.1; so you can’t go back to an earlier version. (This is due to some internal data format changes.)

There’s nothing you need to change when upgrading to EE.

Thanks a lot Jens. We have one more query that do we need to get any license key to use Couchbase.Lite. Enterprise 2.5.0 NuGet package in our application? If needed, can the license key be used for multiple users? Please advise

Yes, you need to purchase a license to use Couchbase.Lite.Enterprise in production (you can have a lawyer review the license agreement that is included in the NuGet package). For specific details I’d advise contacting the sales team at Couchbase.

Thanks Jim.
As part of testing, we deleted the CouchbaseLite folder which contains DBName.cblite2 folder and Logs folder. But, no documents were getting synced down to the local system after that. This was the case even with the community edition. We tried replicator.ResetCheckpoint() and that also didn’t help. How can we resolve this issue? Please advise.
When we copy and paste the CouchbaseLite folder from our backup (which was working before), then it is working.
Also, do we need to configure anything at sync gateway?
Code snippet given below.

var config = new ReplicatorConfiguration(DcfrDatabase.Instance, new URLEndpoint(dbUrl))
ReplicatorType = ReplicatorType.PushAndPull,
Continuous = true,
Authenticator = new SessionAuthenticator(sessionId)
repl = new Replicator(config);