Transferring a database fully WinOS<->macOS

Some questions still seem to be present about how to provide a full transfer of an RM database and its media as generated on WinOS to someone who wants to work on macOS (and perhaps vice-versa). The sharable drive option that is provided in RM does not work to transfer between the two OS’s (as discussed elsewhere).

Based on some initial insights, and as a macOS user, I suggest one approach below that I think should work. The approach below excludes any database content that is shared with/linked to/obtained from Ancestry.

***

The first step to make a fully sharable transfer of an entire RM database from WinOS to macOS (and vice-versa) is to have all files that are associated with the RM database in one central repository folder on your local drive. The easiest approach to meet this objective is when you have used the Settings→Folder tab to point your Data folder, Backup folder, Media folder, GEDCOM folder, and Report folder all within one main directory folder. In the next steps, the presumed Settings are as follows (where … indicates a higher level folder such as My Documents):

  • Data folder: …/Genealogy/Roots Magic/data
  • Backup folder: …/Genealogy/Roots Magic/backups
  • Media folder: …/Genealogy/Roots Magic/media
  • GEDCOM folder: …/Genealogy/Roots Magic/GEDCOM
  • Report folder: …/Genealogy/Roots Magic/reports

You can collapse the sub-folder structure by one level and/or name the sub-folders as you want. For example, the main locations can instead be at …/My Roots Magic Files/(data, backups, …).

In order for the macOS version to work fully when you share it, your RM database has to work fully based on a structure such as above. I make no claims as to whether the transfer process will work if you have pointed all your folder locations (data, backup, media …) into one main level folder without associated sub-folders. Also, to emphasize especially with regards to media, if you have any RM files that are stored outside of the above five folders and your WindowsOS version of RM still works seamlessly to access those files, you will have to research how to set up links to those outside files to work within the macOS version of RM.

Finally, the Data folder that you set up as above should contain only the RM database .rmtree file that you want to share. One change might be to put the main .rmtree file at the root of the sub-folders, (e.g. put it in …/Genealogy/Roots Magic directly). Keep this in mind for what follows as instructions to the macOS user.

To be readable by both WinOS and macOS, whatever physical medium you use to transfer the files must be formatted as exFAT. Alternatively, you can upload the file to a cloud service and have the other person download it.

To start the transfer process, make a ZIP archive of the main folder containing the sub-folders. In the above example, the ZIP archive would be of the Roots Magic folder. Making a ZIP archive does two things. First, it collapses some storage space requirements. Secondly, it preserves the integrity of the source files from possible corruption in copying over to the exFAT and in copying over to the other OS system. Rename the ZIP archive to a well-structured convention (e.g. RootsMagicTransfer_2026-04-13.zip), if for nothing else than the sake of everyone’s sanity in later administration of whether it worked or not.

Copy the ZIP archive to the exFAT formatted physical drive. Or, upload the ZIP archive to the cloud share folder.

For the macOS user who should receive the files, they must download and install the RM application before anything else. Then, they must open the RM application before they do anything else. They must set up the Settings→Folders using exactly the same naming structure that you created for your database. Here is a picture.

Two things are critical here. One: This step must be done before any data files are copied over. It establishes the folder paths before any content is added. Two: The naming conventions must adhere exactly to the conventions that you used. Note above that point to the main folder Roots Magic/ is important. The user on macOS can put this Roots Magic folder anywhere. But the name and the sub-folder layouts must be the same as what you used.

Once the macOS user has set up this folder structure, quit the RM application. Now, copy over the ZIP archive from WindowsOS exFAT or cloud folder to an easy-to-find location (on macOS, this might be on the Desktop). Open and extract the ZIP archive folder. COPY all content that is found in each of the above five folders from the ZIP archived folder into the same-named folders for the Roots Magic/ tree.

As the final step, the macOS user can now open the RM app, choose Open File, and find+open the .rmtree file (i.e. in the …/data folder) that should manage it all.

***

I hope these instruction steps are useful. Please comment with any corrections as appropriate.

Caveat: I have tested by creating a test database on macOS, ZIPping the test database, cleaning out the folder structure, recreating the folder structure, and re-initiating using the above steps. If RM does its magic with relative file paths, things should work coming from Windows. If RM stores absolute file paths even after the five folders are set, then possibly all bets are off.


JJW

1 Like

An additional issue is that RM uses a special collating sequence to sort certain non-English alphabets in a special way. For example, the Norwegian Å is sorted in this special collating sequence as if it were an English A.

RM’s Mac version of this special collating sequence does not appear to be identical to RM’s Windows version. As a result of this issue, some users have found that if they move a database between Windows and Mac in either direction, the first thing they have to do on the machine to which they moved is to run the Database tools in order. The key tool to run would be File > Tools > Rebuild Indexes, but it’s probably a good idea to run all four tools after moving a database between Mac and Windows in either direction.

Just curious. Is this because RM is not Unicode aware? If so, might this limitation be lifted in a future version?


JJW

RM is Unicode aware. RM’s database is SQLite, and SQLite uses UTF-8 for all its character data. RM therefore can store pretty much any character data from any language in any of its character fields.

The issue is that RM uses a proprietary collating sequence that attempts to sort several non-English letters as if they were the English letter they most resemble visually. Users who use RM on both a Mac and Windows have reported that RM’s proprietary collating sequence is not compatible between Windows and Mac, and that they therefore have to reindex their data when they switch machines. No data is lost. It’s just a collating issue.

The answer depends entirely on:

  • what you’re sorting
  • how you want it sorted
  • how your machine’s OS is configured

How your machine is configured (“user-chosen” language and country/region) defines a LOCALE and can obviously VARY greatly.

Computer software relies on this concept to determine which character set will be in use, which characters and how they display/sort/ etc.

Collation is the means by which ordering takes place, but slight differences exist between seemingly similar LOCALE (not just characters, but time formats, thousandths separators, OS-specific “conventions” and other dependencies).

WRT sorting/collating …

  • Very glad to hear that RM is UTF-8 compliant.
  • Sad to hear that RM uses a (proprietary) sorting/collating method that in itself cannot be consistently, robustly validated between different OS platforms.

Which only begs to ask … Suppose that I do a specifically-defined sort sequence on an RM database on WinOS. I successfully transfer that RM database from WinOS to macOS. I immediately reindex the database on macOS. I choose the same specifically-defined sort sequence as was used on WinOS. Am I thereby guaranteed to get the same results as my WinOS colleague?


JJW

thank you for taking time to put this together

That capability doesn’t exist. RM’s special collating sequence is hardwired into RM. Also, locale settings do not influence the special collating sequence.

1 Like

Let me return to something else.

My question is this → After users reindex their database, do the issues that users reported due to the non-compatibility disappear?

Otherwise, I have tried to edit my post to include instructions about running the database tools. But I cannot. So, add these instructions.

***

Before you start the processes to package your database, run the following four Database Tools on the database in this preferred order: Integrity check, Rebuild indexes, Remove phantom records, and Compact database. You can then close the database and quit/exit from RM.

After the user opens the transferred database on macOS, they should run the same four Database Tools in the same order as listed above.

***


JJW

Yes, running the database tools after opening the db on a different OS resolves the issue.

In the past the recommended order to run the tools was as they appear in the File, Tools Page - Test Integrity, Rebuild indexes, Clean phantom records, then Compact. When the top-level Tools menu was introduced there were suggestions to reorder these items so they would be in the same order in both menus. That did not happen. It’s not clear that the order is critical, though compacting as the last step seems to make more sense to me.

I’ve modified my addition to use your suggested ordering. Compacting does make sense as the last step, with testing and rebuilding as the first steps.

Thanks.


JJW

2 Likes

That is a good description, but it doesn’t transfer the database “fully” if you are using TreeShare. You’ll discover if you only move the database that you’ll need to rematch your Ancestry information.

On the Mac you’ll see:

/users/%username%/RootsMagic/AMT/AT_nnnnnn.DT8 (pre 11.0.2) or
/users/%username%/RootsMagic/AMT/AT_nnnnnn.DT11 (11.0.2+)

Which will correspond to on Windows:

/users/%username%/AppData/Local/RootsMagic/AMT/AT_nnnnnn.DT8 (pre 11.0.2) or
/users/%username%/AppData/Local/RootsMagic/AMT/AT_nnnnnn.DT11 (11.0.2+)

or:

/users/%username%/AppData/Roaming/RootsMagic/AMT/AT_nnnnnn.DT8 (pre 11.0.2) or
/users/%username%/AppData/Roaming/RootsMagic/AMT/AT_nnnnnn.DT11 (11.0.2+)

1 Like