Family Tree Maker 2017 – 24 June 2017 Update

Quite a bit of progress has been made over the past few weeks. If you look at the FTM 2017 Release Page, you will see that they are currently in the midst of the Test Drive 2.0 release, and are looking at a July 15, 2017 release date for everybody, as in it will be out of beta.

Note/Commentary: MacKiev (and by proxy) continue to receive a lot of criticism in regards to the delayed release/launch, and the length of the beta testing. If you remove the synchronizing of the family trees with, I believe Family Tree Maker 2017 could have been released in March of this year. However, that synchronizing is exactly why a lot of people use FTM. A lot of people do not realize that FTM 2017 is using a new synchronizing service that rolled out (to replace the older service), and it could not be tested until the older synchronizing service was shut down. Additionally, because it was a new service from, it had to be debugged and had to be checked to guarantee that people would not lose data when synchronizing between their local family trees and their online trees hosted through It became especially difficult the larger your family tree is (getting into the tens of thousands and above), and this new service was found to have some issues, including negatively impacting the performance of other infrastructure. Those issues are very nearly worked out, and we are reaching a point where people can be comfortable with synchronizing their genealogy information and not worrying about losing data.

While there has been criticism/noise about the lengthy beta-testing, the amount of outcry that would have ensued had FTM 2017 been rolled out without adequate testing of the new services would have been tremendous if people started losing data, or were unable to fully synchronize (as in, during the actual process, the services timed out and stopped synchronizing). And keep in mind that has not only had to improve/fix the new service multiple times just for FTM 2017 syncing, they are facing the fact that RootsMagic will also be synchronizing genealogy data with for the first time in an upcoming update, putting more load/stress on the infrastructure.

All of this is not helped by the fact that there are plenty of people who do not use FTM and/or, and felt the need to jump in and criticize the companies involved without knowing the issues involved. This is reminiscent of the Mac vs PC flame wars, Intel vs AMD, etc., and it’s something the genealogy community has always had (FTM vs RootsMagic vs Legacy, etc.).

Back to the update: MacKiev posted this message earlier this week, discussing the improvements that have been made as far as synchronizing your Family Tree Maker 2017 database and
Continue reading

Heredis 2017 – 50% Sale Through May 28

Heredis 2017 World is 50% off through Sunday night, May 28. Heredis is a cross-platform genealogy application, complete with macOS, iOS, and Windows versions. Heredis 2017 is a major upgrade, focused on tracking your genealogical research and progress.

If you’d like to try a demo version, you can download it through

Available through the Mac App Store: Heredis 2017 World – BSD Concept

Family Tree Maker 2017 – May 19 Update – Official Launch Soon

We are getting extremely close to the official launch of Family Tree Maker 2017. I don’t know if it will be this month, since we have less than two weeks, but from information that MacKiev released yesterday, I think we are just a few weeks ago – has been working out issues with performance on their end, and all limits on the number of Family Tree Maker users accessing have just about been lifted:

We’re continuing to beta test builds with the streamlined process for syncing changes made on the Ancestry side, and that looks to be coming along nicely. When completed it will allow us to remove all limits from adding FTM 2017 users to the system. We expect to provide a new build to our test drivers in a week or so, and assuming success there, roll it out to the rest of the world shortly after.

If you pre-purchased already, you should have received one or more emails about an invitation:

We reached out to all who had pre-purchased FTM 2017 with an invitation to take a test drive – 48 hours to try out the new edition under controlled conditions. Nearly all test drivers elect to continue using it rather than rolling back at the end of the two day test period. We’ve now processed all the new applications received this week and have accepted more than 80% to test drive immediately.

If you want to read the full message, and keep an eye on the release schedule, check MacKiev’s Release of FTM 2017 page every few days, or check back here.

I have still had no problems with synchronizing my family trees with, but mine are very small these days (a few hundred people) as I’m working through a “genealogy do-over”.

Branches Pro 1.6 for macOS and iOS (iPad)

Branches Pro for macOS, along Branches Pro for iPad, and Branches for iPad (free), has recently been updated. Branches is referred to by its developers as a “full featured record manager for your family tree information.” It uses GEDCOM files to import/export data, and is cross-platform between Macs, iPads, and Windows.

This may seem like a small update, but for some genealogists, it’s actually going to be very important. Version 1.6 brings “support for downloading and updating LDS ordinance information to be compatible with upcoming changes on FamilySearch.™”

Likewise, Branches for iPad (the free version) and Branches Pro for iPad have been updated. They also use GEDCOM files (and can load them from Dropbox), and can also interact with/download FamilySearch family trees. Branches Pro for iPad 4.5 adds updated FamilySearch features, and minor fixes, and the free version has received “enhancements” for FamilySearch and minor fixes.

Branches Pro for macOS: Branches Pro – Mac App Store – $29.99

Branches Pro for iOS (iPad): Branches Pro for iPad – App Store – $0.99 (current promotional pricing, normally it’s $2.99).

Branches for iOS (iPad): Branches for iPad – App Store – Free

There is a Branches for Windows available through the Sherwood Electronics Laboratories website, with a 30-day free trial, and a final cost of $14.99 if you choose to keep using it.

Family Tree Maker 2017 – May 11, Adding More Testers

It’s been just over a week since the last update to the Family Tree Maker 2017 testing, and this afternoon, another update was released:

Working with Ancestry we’ve decided it’s time to let a whole lot more test drivers join the first 25,000 who’ve been happily using FTM 2017 for the past two weeks. We have already started earlier this week tapping those on the “alternate” list and hope to add the rest of you by the end of the weekend.

Then starting on Monday next week, we’ll be opening up as many as 10,000 places a day until we reach 75,000 test drivers by the end of the week. New drivers will start with the same 48-hour trial followed by a diagnostic test. If all goes well, test drivers just continue using the software.

If you are already test driving you are all set, just keep at it. We will let you know when we have a newer well-tested build for you. If you stopped test driving, watch for an email from us tomorrow, in which we’ll have instructions on how to get your test drive started again.

What it sounds like, is that Ancestry has been busy improving their infrastructure/back-end. As I’ve mentioned before, sometime later this year, RootsMagic will also be synchronizing with, so the load on’s servers will increase substantially.

As such, is allowing the FTM developers to remove user limits, which opens the door for Family Tree Maker 2017 to be released to the general public later this month:

We are now beta testing builds made with the final adjustments from Ancestry that we received a week and a half ago. Those provide a much streamlined process for syncing changes made on the Ancestry side and will allow us to remove all limits from adding FTM 2017 users to the system.

So when will that be done? We’ll update you when the beta testing tells us we’ve been successful. The next step would be to provide a new build to our test drivers, and then the rest of the world. We can’t provide an exact date yet, but we’re optimistically guessing a couple of weeks.

Update on Family Tree Maker 2017 (May 3) / First Impressions

Note: I will be posting my impressions of the beta version of FTM 2017 at the end of this article. I think the end is nearly in sight for the official release of Family Tree Maker 2017, for both Mac and Windows. MacKiev has updated their status of Family Tree Maker 2017 page, and the signs are very encouraging:

For performance, a majority found FTM 2017 faster than their previous edition:
– 56% Faster or Much Faster
– 35% About the Same
– 9% Slower or Much Slower

– Most test drivers (94.8%) reported being able to sync.
– Nearly all (98.2%) of test drivers elected to continue driving after the first 48 hours.

This was the latest on the side:

We are conducting tests with Ancestry engineers tonight to check modifications made for handling the largest trees. We are grateful for the participation of a volunteer beta tester with 270,646 people in her tree who agreed to stay up late to help (thank you, Tracy!) When these tests are complete we hope to be able to make a decision on a partial or full rollout. We’ll announce that as soon as analysis of the results are available. Stay tuned.

Last week, MacKiev sent FTM 2017 to 25,000 new beta testers, and this is what they were looking at:

We will lbe measuring syncing success, performance and stability. Additionally, Ancestry will be monitoring what happens when tens of thousands of Family Tree Maker users all get started using the new edition at the same time. We’ll meet with Ancestry on Tuesday to decide whether to expand the test drive program or go for a general release.

And this was from April 20th:

Results from expanded beta testing this week showed 94% are now able to sync (up from 89% last week) with all but the largest of trees. And Ancestry continued to roll out modifications to their connection systems to help ensure that syncing works reliably for all users. The last major Ancestry system update will be live tomorrow (Friday) and we expect to start building our part over the weekend and have it ready to test and put into builds early next week.

The Saga of TreeSync and FamilySync
I’m oversimplifying all of this, but I want to briefly discuss it (because it’s a very long and complex topic). I’ve seen some people that are frustrated with the process, since TreeSync was shutdown in March (the lack of synchronization of trees between’s online version, and the FTM desktop software caused a LOT of frustration). TreeSync is the feature that allowed FTM users to sync their online trees with the Family Tree Maker software. After sold FTM, TreeSync was originally going to be closed down back in 2016, with its replacement, FamilySync coming sometime in 2017.

That would mean that for several months, there would be no syncing of trees between and the desktop version of Family Tree Maker 2017.

MacKiev convinced to keep TreeSync available through March, with the idea that Family Tree Maker 2017 would launch with FamilySync, the replacement for TreeSync, shortly after.

Note that FamilySync would NOT be compatible with previous versions of Family Tree Maker. I will talk about FamilySync at a later date, but keep in mind that in the near future, RootsMagic will also be syncing with’s family trees, putting even more of a load on the servers.. From what I understand, RootsMagic is currently testing the syncing of family trees between the RootsMagic desktop software and, although I do not believe it’s in the same numbers as FTM 2017.

Back to the topic – unfortunately, this meant that testing of FamilySync would have to wait until TreeSync was closed down, because the two could not function at the same time, and so any and all issues with FamilySync and FTM 2017 would not be discovered until then, and it would feel like it was a very compressed time frame. There were some communications issues as well, which MacKiev acknowledged, but the bigger issue was still that a lot of FTM 2017 users would be using FamilySync at nearly the same time, putting a lot of strain on the side.

If you have played online games, particularly online games with lots of players who are on at the same time, it’s very similar – during a game’s launch, or a major update, there are many people connecting to the servers at the same time to download the new game data, a much larger number than the normal amount of users who are online at any one time, and it causes problems.

In this instance though, the issue is compounded by the fact that the data being transferred is genealogical in nature, and MacKiev and both want to make sure that nothing is lost. Nothing would hurt either company more than news that they are losing customers’ genealogical information. It’s easy to re-download a video game patch. It’s not so easy if your family tree has thousands of people in it, and you aren’t sure if they were all uploaded/downloaded between your desktop software and, or if something was overwritten that shouldn’t have been.

As you can see from the comments above and in previous updates on MacKiev’s site, all of this is putting a strain on’s servers, and so it’s not just a matter of MacKiev testing FTM 2017 with their beta testers (which they had been doing well before all of this),’s engineers are heavily involved, and having to adjust and possibly upgrade their servers.

And keep in mind that both MacKiev and have to be satisfied with the results on their ends, that the users of FTM 2017 will not be losing data. And is having to prepare for RootsMagic as well.

Where Does That Leave Us?
Yes, all of this has taken longer than expected, but as I mentioned, FamilySync couldn’t go live and be tested until TreeSync had shut down. I’m not making excuses – the easy call on’s and MacKiev’s part would have been to shut down TreeSync last year, and then launch FamilySync with FTM 2017 several months later (March or April), but they made the decision to keep things going as long as possible for users of older versions of FTM. The end is in sight though.

Okay, My Impressions
Now that beta testers can talk about FTM 2017 a bit (but not too much from what I understand), I’ve got some thoughts:
– I have not seen anybody losing data when synchronizing between FTM 2017 and That doesn’t mean it hasn’t happened, but I haven’t seen it myself, and I haven’t read about it from others who are beta testing.
– I have had no issues synchronizing my trees between and FTM 2017. With that said, my trees are substantially smaller these days – only a few hundred people and a few dozen media files. That’s because I’m in the process of a genealogy do-over and rebuilding my trees from the ground up. I’m motivated in part because of DNA tests I have done, as well as those of relatives. I’m trying to make sure that my personal family trees are as accurate as possible.
– I’m not going to comment too much on the FamilySync interface, because I think that we beta testers possibly have a different interface than what will be released with public versions of FTM 2017, but I will say it’s been very informative – MacKiev has added information that lets you know how well/fast syncing is occurring, and if there is anything you need to be aware of.
– I do think that the syncing is faster than previous versions of FTM, but I haven’t been what you would call a heavy user of FTM.

I have been familiar with FTM for well over 10 years, but I’ve rarely used it as my main genealogy program – in recent years, I’ve been using it mainly to synchronize very limited trees with, mainly as a means to easily check for hints on, and to make contact with others researching the same lines. Now that I’m more heavily involved in DNA-related genealogy, both with myself and family members, I will use it quite a bit, but I don’t know if it would become my main genealogical program. I tend to use multiple programs, for different projects/needs.

I will say this much: I think MacKiev is doing a better job of supporting Family Tree Maker than had done in recent years. I understand why wanted to move away from having their own desktop genealogy software, and I give them credit for being willing to let MacKiev take it over. They could have easily just killed it off – it would not be the first time something was shut down like that.