We discovered two issues when moving from Evidentia 3 to Evidentia 3+ that are limitations of the old Evidentia 3 — not problems with the new code. I want to be upfront about what’s happening and share a workaround that’s available right now.
The Two Issues
- When v3 creates a backup, it does not export the
directlogtable — the home of your Lineage Tracker data. That means Lineage Tracker history from v3 cannot be carried over to v3+. - There is no way to export custom claim type records from v3, so none of your custom claim types get copied to v3+ either.
I can’t change the old v3 code to fix these limitations — but I do have a workaround, and it involves Dropbox and a brand-new feature now available in Evidentia 3+ v3.9.1.
The Evidentia Merge Database Feature
Version 3.9.1 adds a “Merge Database” button to the Database tab. Unlike “Restore Database” — which clears all your existing data before importing from a backup — Merge lets you import data into an existing table without deleting it first.
You’ll be asked what to do about any duplicate records: overwrite them with data from the file, or skip them and keep what you already have. It’s a surgical import, not a full replacement.
The Evidentia merge database workflow is especially useful when you’ve already begun working in v3+ — adding new sources, citations, and notes — because it won’t touch your existing records. Only the data from the imported file is processed; everything else stays exactly as it is. Think of it as a precision tool, not a blunt instrument.

I had planned this feature for Evidentia 4 — but it turns out we need it now.
So How Does This Help If v3 Doesn’t Export That Data?
That’s where Dropbox comes in.
If you use Dropbox with Evidentia v3, the Database directory contains a separate file for each table. The naming convention is databasename.tablename — so in that directory you’ll find files like evidentia.directlog and evidentia.claimType. You can Merge those individual files just as you would a backup file, and only those specific tables will be affected.

“But I Don’t Use Dropbox”
If recovering your Lineage Tracker data or custom claim types matters to you, here’s a path forward — even without an existing Dropbox subscription:
Dropbox Workaround — Step by Step
- Create a free or trial Dropbox account
- Enable Dropbox in Evidentia v3 (v3 and v3+ can coexist — they just don’t share the same database)
- Wait for the database to sync to Dropbox
- Locate
evidentia.directlogand/orevidentia.claimTypein your Dropbox Database folder - Use the new Merge Database feature in v3.9.1 to import those files into v3+
- Cancel your Dropbox account if you don’t want to keep it
A few things worth knowing about the Dropbox approach: Dropbox offers a free plan and a 30-day trial of paid tiers — more than enough time to complete this one-time migration. You don’t need to install the desktop app; you can access and download your files through the Dropbox web interface. Once the migration is done, you can downgrade to the free tier or cancel your subscription entirely without affecting anything inside Evidentia.
If you’ve been using Evidentia 3 for years, your Lineage Tracker may hold significant research history — ancestor lines you’ve traced, progress markers you’ve set. The same goes for custom claim types: if you’ve built a tailored vocabulary for your genealogy workflow, those definitions represent real setup work. It’s worth the extra steps to bring them across.
Not ideal, I know — but it’s a reliable path around the limitations of the old system.
I hope this helps someone. As always — thank you for your patience!















![tumblr_m6n6hg87241qe1bqp[1]](https://evidentiasoftware.com/wp-content/uploads/2012/12/tumblr_m6n6hg87241qe1bqp1.jpg)