FOCUS: Step 3 – Breaking Through Brick Walls Using Y-DNA and Mitochondrial DNA

In the first three articles of this series, we:

  1. Selected a brick-walled ancestor we’d like to find
  2. Learned how to overcome the hurdle of DNA matches without trees
  3. Discussed methods to locate our ancestors’ mitochondrial DNA (mtDNA) and Y-DNA

I suggest reading these articles in order.

In this article, we’re going to learn how to use mitochondrial DNA or Y-DNA to help identify the ancestor you’re seeking.

Multiple Levels of Information

Mitochondrial DNA and Y-DNA testers receive important information that includes matching with other testers, several interpretive tools and reports, and a haplogroup which is the key to unlocking the past.

Since people have tested at varying levels, or maybe they’ve simply obtained a partial haplogroup from autosomal testing, you may encounter varying levels of information about the same ancestor.

As we noted in Finding the Y-DNA and Mitochondrial DNA of Your Ancestors, you could be working with:

  • The most refined haplogroup possible if you or the tester has tested at either the mtFull or the Big Y-700 test level at FamilyTreeDNA.
  • A full haplogroup, whether you have access through the tester’s account, which provides additional tools, such as matches, or access to the haplogroup only, meaning not directly through the tester’s account.
  • A partial haplogroup if the tester has tested at a lower level, or the haplogroup was determined through an autosomal DNA test. Autosomal tests only provide partial haplogroups.
  • Minimum information, meaning an unknown haplogroup level without access to the tester’s account information.

All of these can be useful, but for our example, we’re assuming account-level access along with the highest testing level, which provides the most refined haplogroup possible.

Also note that both Y-DNA at the Big Y-700 level and mitochondrial DNA haplogroups at the mtFull level are evergreen. This means that when more people’s test results produce additional mutations that you share, and that qualify for a new haplogroup, you’ll automatically receive that new haplogroup.

New Y-DNA haplogroups are typically added within a few days or a couple of weeks after the new tester’s results are complete. For mitochondrial DNA, an updated Mitotree is calculated every few weeks, and your haplogroup may be refined from time to time.

Matches are the Backbone of DNA Testing

As with all types of DNA testing, matches are critically important.

With Y-DNA matching, the tester typically has the benefit of a recognizable, or at least similar, surname on their match list. However, that’s not always the case.

I’m starting with the results of one of my Estes cousins who has taken the Big Y-700 test as an example because it affords me the opportunity to review all of the genealogical benefits of the highest testing level.

My cousin’s Big Y-700 haplogroup is R-ZS3700, which was formed about 1750 CE. Note that all haplogroup origin dates are actually a range.

Using the results of Big Y-700 testers combined with genealogy, we know exactly which of the Estes males developed that mutation.

Prior to taking the Big Y-700 test, my cousin’s predicted haplogroup based on STR testing was R-M269, a difference of about 6,200 years.

If you’re a new tester, a haplogroup from 6,450 years ago versus one that places you directly as a descendant of Moses Estes, born in 1711 in King and Queen County, Virginia, is night and day.

Y-DNA Testing and Matching Levels

All Y-DNA testers receive the regular STR (Short Tandem Repeat) panel matches at the level they’ve purchased – ranging from 12-111 markers, including all markers beneath that level.

Testers at the now obsolete Big Y-500 and current Big Y-700 level also receive 500 and 700 STR markers, but the SNPs (Single Nucleotide Polymorphisms) revealed at this level of testing greatly overshadow the usefulness of those additional STR markers.

Men who take the Big Y-700 test receive Big Y-700 SNP matching separately from STR panel matching on their dashboard.

12-111 STR Panel Matches

Clicking on “Y-DNA Matches” under “Y-DNA Results and Tools” shows the tester’s STR panel matches at various levels. Big Y testers should not ignore these because not all people have tested at the Big Y-700 level.

Click any image to enlarge

At the top of the matching display, note that the STR match levels are shown. Matching defaults to the testing level of the tester. In this case, my cousin took the Big Y-700 test, so the matches he’ll see first are his 40 111-marker matches.

Not everyone has tested at that level.

The very first Y-DNA test offered in this industry 26 years ago was at FamilyTreeDNA and was only 12 markers. It was revolutionary at the time, affording genealogists the ability to determine if two men with the same surname were descended from the same paternal line. This also means that FamilyTreeDNA has men in their database that testers can match today who tested a generation ago, many of whom have since passed away.

Over the years, the tests have expanded and improved. Today, men can purchase the introductory 37-marker test, which includes the 12- and 25-marker levels, or the 111-marker test, which includes all the lower levels. Big Y-700 testers receive everything, plus a substantial amount of additional information not available with the STR tests.

Notice that our Estes tester has 40 111-marker matches, but 238 12-marker matches. This is due, in part, to the fact that many men have not upgraded to the higher-level tests. Some men will match on the 12-marker test but will have too many mismatches at higher-level testing. Generally, when both men are being compared at the same level, the higher-level tests ferret out matches that occur simply because they share a very old and distant haplogroup.

The “Genetic Distance” step number is NOT the number of generations difference, but the number of mutational steps separating the results at the level being viewed.

H Estes, the first match, tested at the 111-marker level, so 1-111 markers are being compared. My cousin and H Estes have a “1-step” difference at 111 markers. That means H Estes matches my cousin on 110 of the 111 markers in that panel.

The values of those markers can be viewed under the “Y-STR Results” under the “See More” tab, but the values themselves are not generally informative. You cannot see your matches’ values unless they have joined a group project. Some group projects are displayed publicly, and some are not.

If a tester has joined a DNA Group Project, such as the Estes Project, the values for consenting participants can be seen there, along with additional information such as the Earliest Known Ancestor (EKA).

In general, the fewer the mismatches, the closer the relationship. That said, STR (Short Tandem Repeat) markers are inherently unstable. Mutations and back-mutations can happen at any time, which sometimes makes the results misleading. Haplogroup-defining SNP mutations don’t suffer from that issue.

You can also see project members listed in Group Time Tree format as we discussed in the third FOCUS article, here.

More Hints on the Matches Page

Additional important genealogy hints on the Matches page include the “Paternal Country of Origin” and, of course, the “Earliest Known Ancestor.”

Always check the trees of your matches, even if the match has a different surname. Adoptions, both formal and informal, have been going on as long as there have been humans, and family trees can also hold location proximity information. Think, “right time, right place.”

In the second article, FOCUS: Step 1 – Seven Solutions for DNA Matches with Absent or Shrunken Trees, we discussed how to work around small or absent trees.

Be sure to inspect every match level. Some people view their 111-marker matches but ignore their 12-marker or other match levels.

In this case, there are 198 more 12-marker matches than 111-marker matches, so don’t neglect to review each one. Think of it this way – there are 198 hints you’re missing if you don’t.

Depending on where mutations randomly happened to occur, you may NOT match someone at the 12-marker level that you DO match at higher levels, so you can’t always assume that all of your 25-marker matches are shown at the 12-marker level or vice versa.

In the Estes lineage, we’ve been recruiting males and solving mysteries for 25 years now, but not every lineage has this many testers with surname matches. Then, of course, there’s mitochondrial DNA, where surnames won’t meaningfully match testers.

Mitochondrial DNA Matching

People working with mitochondrial DNA consider Y-DNA testers fortunate because their surname tends to remain the same across generations, at least in some parts of the world.

For the most part, mitochondrial DNA matching is the same as Y-DNA matches, except:

  • You seldom recognize a surname
  • If you do recognize a surname, it won’t be the tester’s surname that matches yours, but perhaps you’ll recognize the surname of their Earliest Known Ancestor
  • You have a Mitotree Haplogroup in addition to the mtDNA Haplogroup
  • You have an F number, which is your haplotype cluster number, in addition to your Mitotree Haplogroup

All people who take or upgrade to the mtFull level test will receive a new Mitotree haplogroup in addition to the older legacy haplogroup. Mitotree was released in 2025 and restructured the entire mitochondrial DNA tree of humankind.

People who only took the HVR1 (Hypervariable Region 1) or HVR1+HVR2 Plus level tests can’t receive the new haplogroup because not enough locations have been tested, so you’ll only see their legacy haplogroup when you’re viewing your lower-level matches. Don’t neglect your HVR1 and HVR2 matches, because the very hint you need may be waiting there.

Your Coding Region matches include the entire mitochondrial sequence – in other words – the mtFull test.

About Haplotype Clusters

As part of your Mitotree haplogroup, you also have a haplotype cluster number which begins with F. The number itself doesn’t matter. The message does.

The mitochondrial DNA matching system excludes several unstable markers because they may provide essentially false matches. However, they can sometimes be useful genealogically, so we have multiple matching criteria.

  • Rose’s example: The genetic distance matching excludes unstable markers such as 315.1, so it’s possible to have an “Exact Match” under Genetic Distance, but a different F number because not every location matches.
  • Anastasia’s example: It’s NOT possible to have a “1 step” Genetic Distance, but the same haplotype cluster F number. It is possible to have the same haplogroup.
  • Per’s example: An identical F number, or haplotype cluster, means you match exactly, INCLUDING any excluded or unstable markers, such as 315.1.

In other words, proceed with caution, and your mileage may vary.

Check marks in the blue boxes mean you have the same haplogroup and/or the same haplotype cluster as your match.

I wrote about haplotype clusters here and here.

Identifying Sophia

In this example, Ms. Traxler and Mr. Lyman are exact matches in the regular “Genetic Distance” matching, their haplogroup, and the new Mitotree haplotype clusters.

In the third example, Ms. Crosbie has a 1-step difference, which means, in this case, she is missing a haplogroup-defining mutation. We know this because her haplogroup is V216a instead of V216a2. And of course, she doesn’t match our tester exactly, so they don’t share an F number either.

The tester, a family member, was brick-walled at his great-grandmother, Sophia Smith, born in 1877, someplace, and died in 1950 in Richland County, Ohio. It seemed like she was dropped off by the stork in the middle of a field, because records about her didn’t seem to exist.

Even though the surnames are different, and Traxler doesn’t have a tree, the name Schmidt in the EKA field caught my eye. Smith is Schmidt in German, and I knew the tester had German heritage in other lines, but Sophia Smith was supposed to be English.

Sophia Smith was married to John Rittinger. That, plus their children’s names, was all I had, but it was eventually enough.

I clicked on the match’s EKA link, and it showed that Elizabeth Schmidt Hornung was born in 1888 and died in 1930.

At this point, I’m wondering whether Schmidt was a middle name or a birth surname.

Two days and a sleepless night later, I had discovered that Hornung was her married name, and Elizabeth Schmidt had married Karl Hornung. As these things tend to do, one thing led to another, and eventually, sorting through newspaper articles, death certificates, and a bunch of misinformation, misspelled names, dead ends, and wrong turns, I found information linking Elizabeth to her brother, Joseph, who connected to their sister, Sophia Schmidt. But was Sophia Schmidt the same person as Sophia Smith?

Finally, running on pure caffeine and determination, I found Elizabeth Hornung’s death announcement in the newspaper, where it gave the names of her siblings, including Mrs. John Rittinger. Now I needed to connect a few final dots to verify that her sister was, in fact, that same Mrs. John Rittinger (by several spellings).

I eventually connected even more dots and discovered the family was from Timisoara, Romania, even though the area where they lived changed borders more than once and fell within the multiple countries of the Austro-Hungarian Empire.

Then, I discovered their parents’ names, but the parents never immigrated, and we don’t know any more about them. Unfortunately, that area was terribly ravaged by WWII, which is what spurred immigration.

The point being that it’s incredibly important to follow every available clue, even if it seems rather pointless. You never know which tidbit is the right one, and if you skip them, you’ll never make that breakthrough.

Follow your exact haplotype cluster matches first, then your exact and one-step regular matches, then your haplogroup-only matches, and then your near-haplogroup matches.

What if the Y-DNA Match Surnames Aren’t the Same as Yours?

Let’s say you take a Y-DNA test and your surname is Estes. Furthermore, your father and grandfather carry the same surname.

So, you didn’t expect to see this on your match page.

First, breathe.

Second, you’re looking at 12-marker matches. It’s not at all uncommon for men within a core haplogroup, like R, to match at the 12-marker level even though they may not have shared a common paternal ancestor in thousands of years.

Panning for Gold

But wait, you’re saying, you just told me not to ignore 12-marker matches.

At 12 markers, you’ll need to focus on your own or similar surnames. It’s like panning for gold.

At 12 markers, my Estes cousin has a total of:

  • 35 Estes matches
  • 2 Easter matches
  • 1 Eastes match
  • 3 Eastridge matches

This means that he also has 197 non-similar surname matches.

The information you need may well be buried in the information provided by those 12-marker Estes or similar surname matches.

For example, if your surname is Eastridge or Easter, you might want to look at historical documents to compare your ancestors’ surnames. We now know that Easter happened sometime near the Civil War in North Carolina, probably because the final S in Estes was interpreted as an R. The circumstances surrounding Eastridge are less clear, but we know roughly when and where it occurred in North Carolina.

A group of researchers spent years trying to unravel the Eastridge mystery and have narrowed the event to a specific North Carolina county.

On the other hand, if an Easter or Eastridge male takes the Big Y-700 test, he will know immediately if he falls into this Estes grouping, and where, or if he belongs to a different genetic lineage.

A Genetic Detour

However, if your surname is Jones and you match a large number of Estes males at the highest testing levels, and you don’t match any or many other men by your surname, that might be a significant hint about your brick-walled ancestor.

The telltale sign may be that you can track your surname and DNA matching back a couple of generations, then nothing. I recommend working progressively upstream, testing male-line descendants of different sons in each generation, if possible.

In this example, John Jones is the progenitor of the Jones family. According to the genealogy, he had three sons, Elijah, Sidney and William.

In this hypothetical situation, Rodney Jones’ descendant tested and discovered that he matched a whole group of Estes men, many with his own haplogroup – R-ZS3700. A descendant of Nathaniel Jones, a second son of William Jones, tested and confirmed that he matches the descendant of Rodney.

So far, so good.

Next, a direct male-line descendant of Sidney Jones tested and sure enough, he’s a member of haplogroup J. Hmmm. We need another Jones male that descends from another son of John as a tiebreaker. Lucky for our tester, further investigation revealed that Sidney’s descendant matches a descendant of Elijah Jones, another son of John.

This tells us exactly where the genetic break in the Jones line occurred. Between John and William Jones. You may have heard this situation referred to as a “misattributed paternity,” or an NPE, “not parent expected,” but we really know what happened, or why, without additional research.

Caution – Don’t Jump!

A word of caution here. Never, ever jump to conclusions about “cheating wives.” While that’s one possibility, there are several other circumstances we need to consider and rule out first.

In many cases, a young widow remarried, and her baby took the stepfather’s surname. The “adoption” wasn’t remarkable. Adoptions in 1600s, 1700s, 1800s and into the 1900s were informal, not legal affairs. Everyone at the time knew about it, but over the generations it was forgotten until DNA testing shocked everyone.

In another case, a widow had two children more than 9 months after her husband died and both children took the deceased husband’s surname, which was then their mother’s surname.

When making these discoveries, we also need to keep in mind that not all sexual encounters were consensual.

Sometimes, the situation is complicated. I know of a case during the Civil War where a woman traded favors with a soldier of the opposing army for food for her children. Her husband returned home to a pregnant wife, but his wife and children had all lived, and he simply raised that child as his own. That family’s oral history was confirmed by DNA testing.

Now, in our example, given that our Jones tester carries haplogroup R-ZS3700, we know that he descends from Moses Estes, born in 1711, the progenitor of that haplogroup. We need to begin by working down the genealogical tree with Moses and look for an Estes male in the same location as William Jones’ mother about 10 months before his birth. Also consider factors like warfare and trader movement. Check the census for missing children, or a child that suddenly appears in a later census that should have been recorded with the family in an earlier census. Notice anomalies.

Look for the surname you match the most closely in that location and at that time. Right time, right place, and opportunity.

And of course, to complicate things further, don’t assume that the mother was the mother either. Sometimes both parents died and someone took the child to raise as their own. Review all of the evidence at hand with fresh eyes.

Matches Map

Another matching feature for both Y-DNA and mtDNA includes the Matches Map.

For Y-DNA, the Matches Map can be found under the “See More” tab.

For mitochondrial DNA, it’s found under “mtDNA Results and Tools.”

While the Matches page and Discover reports both provide the Country of Origin, the Matches Map provides a specific location where your match’s earliest known ancestor is found. Be sure to select the match level using the drop-down in the upper left-hand corner, or no results will display, and you’ll receive the message that there are no results available.

The Matches Map is extremely useful for quickly identifying common locations, especially when surnames don’t match.

The Matches Map utilizes the location entered for your EKA.

Add Your Earliest Known Ancestor and Locations

Please be sure to add your Earliest Known Ancestor and their location under the drop-down beside your name at the upper right-hand corner of your dashboard page. Click on the gear for “Account Settings,” then “Genealogy.”

You don’t need to know the longitude and latitude. Just click on “Update Location,” which takes you to the map where you can simply search for and select the location, which updates these fields.

An identical field for your matrilineal line is found below the paternal section. For purposes of clarification, this is NOT any woman on your “maternal” line, and NOT the “earliest known person” on your maternal side. The ancestor must be a female, and it is ONLY ever your mother’s mother’s mother’s direct matrilineal line – through all women – to the end of that line.

If you see a male EKA in your mitochondrial DNA match list, you know the tester was confused about what to enter here. Hopefully they have a tree that you can view to find the correct EKA.

In addition to your EKA, please add the list of your family surnames, your Family Tree, and a link to your profile at WikiTree while you’re there. You’ll see in just a minute why that information is so important and how it benefits your genealogy.

The Difficult Moore Line

Let’s look at a much more difficult scenario.

My James Moore line (c1720-c1798) is my decades-long brick wall. He first appears in Amelia County, VA, and then moved to Halifax County. His wife was Mary Rice. His life before that is a blank slate, despite my earlier efforts and those of several cousins. I wrote about him here and here.

My Moore cousin, who is deceased, so cannot upgrade his Y-DNA test from its original 12 markers, has only three matches at the 12-marker level. This is all I have to work with except for his autosomal Family Finder results.

Note that one of his matches tested at the 12-marker level, one at 37 markers, and one at 111 markers. Each man would have received a predicted haplogroup based on his STR marker test. Recently, if they had taken a Family Finder test, their predicted haplogroup would have been updated and overwritten by a confirmed haplogroup derived from Family Finder.

Not only are Family Finder haplogroups more specific and closer in time than predicted haplogroups from STR tests, but they are also SNP-confirmed, not predicted.

Keep in mind that not all autosomal DNA chips were programmed to read the same Y-DNA and mtDNA locations. At that time, they were never intended to be used for this purpose, which probably explains the two different haplogroups for the Moore men.

My Moore cousin’s original predicted haplogroup based on his STR test was J-M102. His Family Finder results updated his haplogroup to J-M241, while his matches are J-Z631.

Using Discover’s Compare feature, we find that:

  • J-M102 developed about 16,000 years ago
  • J-M241 developed about 9,500 years ago
  • J-Z631 developed about 2,950 years ago

While their haplogroups don’t match because they come from different sources, they are still in the same genetic lineage on the Y-DNA phylogenetic tree. In other words, they don’t preclude a common ancestor. Since they also match on their STR markers and share the same surname, we don’t need to be terribly concerned about false Y-DNA matches.

I’ve tried to break through this brick wall many times, but let’s try again using new information.

To begin with, there are many more genealogy resources available now than when my cousin and these other men tested. I had originally communicated with all three of his matches when they initially matched, and they provided me with what little they knew.

I still have that information entered into a tiny tree on my computer. I have not been able to get ahold of these men now in several years, so I’m VERY glad that I reached out when I did. Reach out and collaborate now. You never know when it’s too late.

Y-DNA Plus Family Finder Yields More Hints

Let’s move to my Moore cousin’s autosomal Family Finder matches and see if there’s any additional help buried there.

Searching his Family Finder match list for “Moore” produces 39 people with the Moore surname, and 256 people with the Moore surname either in their own name or their surname list. This is why entering your list of ancestral surnames is important.

I selected the 39 Moore surname matches, then focused on the males’ Y-DNA haplogroups. Our Moore cousin’s haplogroup is J-M241, and his Y-DNA matches’ haplogroups are all J-Z631.

Haplogroups derived from autosomal testing are very useful when viewing autosomal matches with Moore men. As you can see, these Moore men aren’t in the same major haplogroup as our line, so even though they share the same surname, it’s happenstance. Their haplogroup results preclude matches due to their Moore direct paternal line.

Autosomal transfer haplogroups do not update Y-DNA haplogroups and are not displayed to autosomal matches due to quality and consistency challenges.

Working with the rest of my Moore cousin’s autosomal matches, I did not find others who match with haplogroup J and the Moore surname.

If I had found another Moore male that fell someplace in the same branch of haplogroup J, I could use autosomal tools to view shared “in common” matches and triangulate segments to identify others who share that specific lineage. Autosomal matches’ trees plus the genealogy work I’m doing on the trees of the Y-DNA testers might lead to a breakthrough on the Moore line that is severely brick-walled in colonial Virginia.

This approach didn’t work this time, but new matches appear all the time, and autosomal matches may help.

However, we’re not done.

Advanced Matching

FamilyTreeDNA provides an Advanced Matches feature that allows you to select matching criteria across different tests to see whether anyone matches you on those combined criteria.

You’ll find “Advanced Matches” in the “Additional Tests and Tools” section.

You can select the tests to compare to see if people match you on ALL of the criteria you choose.

Yes, ALL is bold red because if you select any of the “Select All” features – that means everything. So, if you select “All Y-DNA” you must match at the 12, 25, 37, 67 and 111 marker levels – not just one of them. If someone doesn’t meet the matching criteria at any individual selected level, that person won’t show on the combined match list.

So, select one Y-DNA choice that both people have, plus Family Finder.

Then, CHECK “YES” under “Show only people I match in all selected tests.” Otherwise, you’ll see everyone you match on both tests, combined.

In this example, one of my cousins matches a Morrow male on both the 12-marker test and the Family Finder test. If I had NOT checked “yes,” I would have seen all of my cousin’s Y-DNA AND all of his Family Finder matches on this list.

Is Morrow the same paternal lineage as Moore? We don’t know. Matching on both tests DOES NOT mean your match is from the same line.

However, this possibility absolutely warrants additional investigation.

Big Y Matching

Big Y matches and tools are displayed separately from STR matches.

The only reason I look at the matches page is to see who has a tree, because the most useful information is provided on the Block Tree and in Discover.

Big Y Block Tree

The Block Tree is an alternate way to view tree relationships over time.

The block tree shows a top-down genetic view of the original Estes line out of Kent. The primary named haplogroup is R-BY482, shown at the top of the blue block labeled “Estes in Kent.” The haplogroup names, like BY483 shown in that same block, mean that all of the men within and beneath that block also have those SNP mutations. Someday, a man may come along and test who does NOT have all of those mutations, or has additional mutations, and may be a candidate to form a new haplogroup.

For genealogy, the point is to see who you’re genetically the closest to.

In this case, our Estes tester falls into the Moses descendant group with haplogroup R-ZS3700. Because other men have already tested and we’ve done that associated genealogy work, we know that this mutation occurred with the birth of Moses Estes, who was born in Virginia in 1711.

Another branch, the James Carroll Estes line, has been defined beneath Moses’ line. If you were to take a DNA test and find yourself in haplogroup R-BY154784, you would know that your ancestor was born to a son of James Carroll Estes who was born in 1860 – so not many generations back in time. You’ll notice a man with the surname of Wilbur in this branch. Sometime, and in some set of circumstances between about 1880 and the present generation, the surname became Wilbur, but the genetic line is absolutely Estes. I view this as the Wilburs having established a new genetic branch in their family line while also being Estes cousins.

Discover

For both Y-DNA and mitochondrial DNA, Discover holds a plethora of wonderful information. Lower-level haplogroups can use the free versions of Discover, but we’re going to focus on information available from the mtFull and Big Y tests when the tester clicks through to Discover from within their own account.

I wrote about Discover broadly here. All Discover reports are educational and help you understand your ancestors and their journey to you, but we are focusing only on the tools you would use to break through brick walls.

Click through on the Discover link in your account on your dashboard for either mitochondrial or Y-DNA.

You’ll arrive on the Haplogroup Story page, which provides a summary of the information available in other Discover Reports.

  1. First, read, don’t skim.
  2. Second, don’t skip the other reports because you read the summary.
  3. Third, check each report for various tabs, displays, and settings.
  4. Fourth, read all the reports.

I wrote a very detailed article about using mitochondrial DNA, Mitotree, and Discover, here.

The Match Time Tree

The Match Time Tree is one of my favorite reports.

Please note the various display options at the top of reports. Checking the “Share Mode” box obfuscates the names of your matches, which allows you to share with others without unintentionally compromising privacy.

I particularly like the Match Time Tree report because it lets you view several things in one place.

  • Your Big Y (or full sequence mitochondrial DNA) matches
  • Genetic lineages and the time when haplogroups were born
  • Globes representing the country where your match indicates that their EKA was born
  • Your matches’ EKAs and family trees, if they have provided them

Additional Bonuses:

  • Ancient Connections
  • WikiTree Connections and lineages

If you add both Ancient Connections and WikiTree Connections to your display criteria, you’ll see them on the Match Time Tree too. In this case, no Ancient Connections are found in this portion of the tree, but four matches have connected themselves to WikiTree as indicated by the rows of pearls.

This is particularly useful because EKAs only display the Earliest Known Ancestors, but you’re probably interested in the entire lineage of your match. Their entire WikiTree patrilineal lineage is displayed on the line, including their common ancestors and their linkage to each other.

In this case, the little blue circle “pearl” on the WikiTree line where I clicked is John R. Estes.

I can click on any pearl and see which ancestor that represents in that match’s tree. I think this is the best thing since sliced bread because, generally, I am looking for the missing ancestor between the tester and their common EKA with their matches. I certainly care about the EKA, but to break down brick walls, I need to know how I can connect from here to there.

Ancient Connections

Ancient Connections shows archaeological excavations from published academic papers and is an evergreen feature. This means that as new Ancient Connections are added, in order of how closely they are genetically related to the tester’s haplogroup, older Connections roll off the end.

You can select the option to view Ancient Connections on your Globetrekker™ video too.

Ancient Connections are anchored in the location where they were excavated by little trowels.

While you may think that Ancient Connections are simply interesting, they hold more information. On a different line, I found another clue about the “rumored” birth city of my ancestor, based on an Ancient Connection buried on the Roman Road just outside the city who could potentially have been his ancestor.

Some Ancient Connections are our haplo-cousins, because they belong to descendant haplogroups from our common ancestor, but sometimes their locations, cultures and artifacts can speak to the lives of our ancestors too.

I wrote in detail how to use Ancient Connections here and here. Don’t shortchange yourself by glossing over these.

Notable Connections

Notable Connections may or may not be useful genealogically. It all depends on who is included, and what the evidence reveals. Some Notable Connections are actually bonus Ancient Connections.

The Estes haplogroup R-ZS3700 connects to the Celtic Mystery Ancestor, but based on the Time Tree, the Celtic Mystery Ancestor cannot be the Ancestor of the Estes line. They do, however, share R-DF49 as their common ancestor.

Who doesn’t love a good mystery? Regardless of how we are related, I enjoyed studying the Mystery Ancestor’s cultural information and assembling it in context with the other Ancient Connections. I stood at Tara, Knowth and Newgrange long before Discover existed, but now I know it might have been where our haplo-cousin lived, and maybe where our common ancestor R-DF49 once stood too.

Notable Connections are intended to be fun facts, but sometimes there’s more.

Globetrekker™

Screenshot of Globetrekker™ video

Globetrekker™ is a video that maps the path your ancestors took across the globe. Note the several display options at the top, along with the legend. Globetrekker™ is really an amazing tool.

Haplogroup locations and connecting lines or paths are based on:

  • Locations of ancient burials which serve as anchors
  • Locations of the EKAs of various testers who carry that specific haplogroup
  • Least-cost travel, meaning given the choice between climbing over the Himalayas or taking the route through a valley beside a river – the valley was almost always the choice of people who survived to create the next generation.
  • Only extending into the Americas for the migration routes of indigenous peoples

You may notice what appears to be confusion or inconsistency in the most recent haplogroups. For example, we know that R-ZS3700 occurred in Moses Estes, born in 1711 in Virginia, son of Abraham Estes, the immigrant, who was born in Kent, England. However, that’s not what the map depicts.

The men who carry R-ZS3700 accurately show their EKA as Nicolas Ewstas born in 1495 in England.

Globetrekker™ can only work with the information it has at its disposal. Moses is not the testers’ EKA, but he is the progenitor of R-ZS3700. The way we know that R-ZS3700 occurred in Virginia in 1711 is because the tested male-line descendants of Moses all carry that SNP mutation, while tested male-line descendants of Moses’s siblings, Abraham’s other sons, do not.

Another potential reason that haplogroup placement might appear faulty is because multiple testers with that haplogroup show different locations.

Let’s say the EKA location provided by one man is Dover, Kent, England, across the Strait of Dover from France. A second man shows his EKA on the far western coast of Ireland in Galway, and a third man places his EKA in the Orkney Islands, off the Northern coast of Scotland.

The “average” of those three locations might be someplace around Dumfries in Scotland, even though none of the three men entered that location – and all three testers are equally unhappy.

Keep in mind that EKA information and locations are user-entered, and, as we know, genealogy can be incorrect and people are sometimes confused.

Another factor affecting placement is that when someone enters only a country name, maps default to the center of the country, which can pull the Globetrekker™ migration paths in one direction or another.

Globetrekker™, in combination with other tools, provides valuable evidence about your ancestor.

Globetrekker™ for mitochondrial DNA has not been released but is planned for the future.

Suggested Projects

Suggested Projects can also provide clues.

Projects are suggested for one of three reasons:

  • Other people with that surname have joined that project
  • The surname administrators have identified your surname as “of interest” to their project
  • Your haplogroup, haplogroup branches, or specific keywords

If you’re searching for your ancestor, hints about their origins or family associations may be found in the projects suggested.

Mitochondrial DNA Match Time Tree Haplotype Clusters

One important difference between the Y-DNA Match Time Tree and the mitochondrial DNA Match Time Tree is that the mitochondrial DNA version displays results within haplotype clusters.

On the Match Time Tree, your results are displayed with other members of your haplotype cluster. These are your closest matches.

That isn’t to say that some of your identifiable ancestors won’t be found in other haplotype clusters, or even neighboring haplogroups, but the place where you should start your analysis is with other people in your haplotype cluster.

I’ve written about haplotype clusters here and here.

Your Summary Checklist

Mitochondrial DNA and Y-DNA have the unique ability to look in a laser-straight line back in time. Unlike autosomal DNA, mtDNA and Y-DNA aren’t recombined, so parts of your ancestor’s DNA aren’t lost during recombination with the other parent’s DNA.

The tools on your personal page, plus Discover Reports, provide at least 25 different ways to analyze your results, several of which are critically important for genealogy and, specifically, breaking through brick walls.

  1. Y-DNA STR matching and Big Y DNA matching are different, so take advantage of both and review every level.
  2. Big Y-700 results include several features that neither STR matching nor mitochondrial DNA can offer.
  3. Mitochondrial DNA provides features not available for Y-DNA.
  4. Matching includes how close or distant the match is, their haplogroup, EKA, EKA’s country of origin, and family tree.
  5. The Matches Map provides the exact location provided for your matches’ EKAs, not just the country.
  6. Enter your patrilineal and matrilineal Earliest Known Ancestor (EKA), their ancestral location, and all of your family surnames.
  7. Be sure you’ve uploaded a tree. Also, connected yourself to your WikiTree profile.
  8. Be sure to check your matches’ trees and their WikiTree connection, if they have one, and build out as necessary to connect with your EKA and your other matches’ EKAs.
  9. Use Group Project Results to check groupings made by the volunteer administrators, EKAs, and possibly marker values.
  10. The Y-DNA Block Tree displays matches along with their mutations in a vertical phylogenetic tree format.
  11. Mitochondrial DNA matching also provides your legacy (pre-Mitotree) haplogroup, plus your Mitotree haplogroup, haplotype cluster and features like trees. Be sure to view all match levels.
  12. Haplotype clusters group mitochondrial DNA testers who match exactly, and include less-reliable markers that are excluded from general matching and haplogroup formation. Research to identify a common ancestor should begin with your haplotype cluster, but should not ignore people in different haplotype clusters.
  13. Investigate unfamiliar surnames through family histories, testing male-line descendants of different sons, and researching descendants of the identified genetic ancestor. Look for intersections and remember: right time, right place, opportunity.
  14. Advanced Matching allows you to combine two (or more) forms of DNA test to determine if someone matches you on both tests, such as either a Y-DNA or mtDNA test and the Family Finder autosomal test. Remember that they may match on both tests due to different ancestors.
  15. Y-DNA haplogroups found in Family Finder matches may identify additional family members in your lineage who have not taken a Y-DNA test (but might be willing to).
  16. Discover provides more than a dozen additional reports.
  17. The Match Time Tree plots your matches with their EKAs along a genetic timeline.
  18. The Match Time Tree also displays WikiTree Connections, which include each generation, not just the EKA.
  19. The Match Time Tree displays Ancient Connections and Notable Connections, which may prove useful.
  20. Ancient Connections provide insight into the movements of your ancestor, their culture and location at a specific point in time.
  21. Globetrekker™, an animated Y-DNA video, tracks your ancestor’s journey across the world to the locations where recent haplogroups are found, based on a variety of criteria and data points.
  22. Suggested Projects provides a list of projects that you may be interested in joining based on common interests. The suggestions alone may be especially important when surnames aren’t particularly helpful, and when you’re searching for your ancestor’s origins.
  23. Use Discover’s Compare feature to determine how different haplogroups relate to each other and whether they are in the same genetic lineage. This is particularly useful for autosomal matches with the same surname.
  24. Use shared matches, segment triangulation, and your matches’ trees to investigate possible connections identified through Family Finder surname and haplogroup searches.
  25. Contact matches, collaborate, and preserve the genealogy they provide.

Your ancestors are waiting for you to find them!

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

FOCUS: Step 1 – Seven Solutions for DNA Matches with Absent or Shrunken Trees

This is the second article in the FOCUS series.

You can read the first article, FOCUS – A New Series Focused on Breaking Down Brick Walls, here.

DNA matches without trees, or bare-bones shrunken trees, can be a significant roadblock whether you’re looking at autosomal, Y-DNA, or mitochondrial DNA matches. To help resolve that issue, I’ve listed seven ways you can create or expand those trees. Not every methodology works every time, but none will work if you don’t invest the effort to try them.

I’ll probably say this in every article because it bears repeating. Everything we are working with is a hint. Breadcrumbs along the way. Sometimes they lead to the next wonderful breadcrumb. Sometimes to a dead end. Sometimes they look like useful breadcrumbs, but they are red herrings and not relevant. And sometimes they are simply wrong. Do not throw the baby out with the bathwater. Also, do not think every hint is accurate, because they aren’t, and many rely upon other people.

Our goal in the FOCUS series is to accrue evidence from multiple sources, tools and methodologies that leads us to our ancestor. So let’s start with trees.

Trees, Trees, But Not Everywhere

DNA testing relies on trees to identify our common ancestors, at least with matches beyond the closest generation or two.

This is true at all vendors, which is why all of the main vendors, except 23andMe, integrate with or provide trees as part of their platform.

Because we need to work with trees for all types of DNA testing and matching, I’m going to share various ways to overcome partial trees or even no tree at all. I’m intentionally using examples from multiple vendors throughout this series.

23andMe is omitted in this article because they don’t support trees, although testers can include a link to a tree elsewhere.

GEDmatch is omitted in this article because they are not a testing company. They are a DNA upload and matching site, so everyone at GEDmatch has tested elsewhere and probably has a tree there. You can upload a GEDCOM file to GEDmatch, though, so it never hurts to check and see if your match is there too.

Some of these techniques are vendor specific, and others can be applied broadly.

What Is a Shrunken Tree?

A shrunken tree is a small tree in which your DNA match has included only a few people. Small or missing trees tend to frustrate genealogists – a lot. I remind myself that these folks maybe seeking their family or new genealogists, trying to piece their tree together themselves.

This is a tree provided by one of my matches. Their mother is deceased, but it’s recent enough that I’ve chosen to obfuscate her name as well, and it’s not relevant to the next steps.

There’s not a lot to work with here, but as it turns out, there’s enough.

Based on this tree, we have no idea where in their tree our Most Recent Common Ancestor (MRCA) is found, so let’s look at a few ways to indirectly expand their tree in order to find our common ancestor.

Step 1 – Check Your Own Tree

I know this sounds like a “duh” moment, but always remember to check your own tree to see if you’ve expanded that branch to include your match’a ancestors and completely forgotten about it. I maintain my primary tree on my computer with lots of notes and information that I’m not comfortable uploading to a public space. I maintain smaller public trees with a couple thousand people at both Ancestry and MyHeritage, along with a link to my ancestors at WikiTree.

If your match is a female, they may be using a married surname, so always keep that in mind. I try their complete name first. Then I search for their surname to see if it’s a “married-in” name – and cross my fingers that it’s not Smith. If they have any ancestors in their tree, I try their oldest generation next.

Step 2 – Reach Out to Your Match

Every vendor provides some way of communicating with your matches. You can either message or email, depending on the vendor, and your match may be very willing to share more about their genealogy. They may have a better tree elsewhere that they will share with you, or may know more than is in their tree.

An Ancestry survey showed that about 53% of Americans can’t name all four grandparents, and only 47% can correctly name all four. Only 4% can name all eight great-grandparents. In the Rolland tree, the tester knew more about their mother’s side, and only knew the first name of their paternal grandmother.

So while shrunken trees are exasperating, they are probably more normal that we think, and we all have to start someplace. Your match might well appreciate some help.

Step 3 – Check Other DNA Testing Sites

If your match has a real name (meaning not just initials or something indecipherable), such as Heather Jacobs (made-up name), who is predicted to be your third cousin and shares 100 cM of (unweighted) DNA at one vendor, sign on to your accounts at the other vendors and see if Heather is a match there.

You’re looking for a Heather, or maybe HJacobs or something similar, who’s approximately a 3C with roughly the same amount of shared DNA. The exact relationship prediction may not match, but it should be close, and the amount of shared DNA may not be identical either. If it varies substantially, it may not be the same person, so exercise care.

Every vendor provides the ability to search for matches by name, and if you can’t find them by name, begin paging until you reach matches at the approximate predicted relationship level. In Heather’s case, that’s third cousins. Beyond third cousins, this paging technique quickly becomes too laborious.

At Ancestry

Only one vendor, Ancestry, “downweights” your DNA with your matches, meaning that they may remove some amount of DNA that they consider “too matchy.” In my case, this is often DNA from my Acadian lines, which collectively forms pileup regions. This does NOT mean those aren’t useful, but that’s not relevant for this discussion other than to alert you that you need to check both the assigned amount of DNA and your unweighted shared DNA with a match when you’re trying to verify that the match is the same person at two vendors.

Assuming you find “HeatherJ” at Ancestry, you’ll want to verify that it’s the same person as Heather Jacobs at the other vendor.

Is your amount of shared DNA roughly the same?

Click on the relationship link to view the amount of unweighted DNA. In this case, weighted and unweighted is the same, and Heather Jacobs matches you with 100 cM at the other vendor.

Heather has a public tree here, and it’s the same size. It’s probably the same person, but check anyway.

Heather’s tree at Ancestry is exactly the same as it was at the other vendor, so this confirms it’s the same person.

There’s an important hint here, and let me emphasize the word HINT.

While Heather’s actual 15-person tree does NOT extend to our common ancestor, Ancestry has pieced together other trees that include and extend beyond her ancestors to show my (purported) common ancestor with Heather. Click on Common Ancestor, which takes you to ThruLines.

This new version of ThruLines has now replaced the older version. Unfortunately it does not show Heather’s path back to our common ancestor, Hiram Bauke Ferverda.

Click on “View all ancestors” in the upper left-hand corner.

Click on any image to enlarge

After clicking on “View all ancestors,” click on Hiram Bauke Ferverda to see the DNA matches who descend from him. Despite what Ancestry provided under my “Common ancestor” with Heather, she isn’t shown anyplace here. This could be a bug, given that I later confirmed this common ancestor using other techniques.

Regardless of the problem, this IS a hint, so don’t disregard it entirely. Just keep your “skeptic” hat handy and wear it liberally. You’ll need to use Ancestry searches and hints, including possibly Quick and Dirty Trees, to piece together the possibilities.

Make a note on Heather’s match at Ancestry so that you know what you found this time through. We’re not done with Heather. Move on to another vendor to see if Heather has tested and has a better tree elsewhere. We’re gathering evidence.

At MyHeritage

Heather is not at MyHeritage, so I’ll use a different example.

Let’s look for Cathy, a 3C match who has no tree at another vendor. I found her at MyHeritage with the same first and last name and approximately the same amount of shared DNA, so I’m confident it’s the same person.

Fortunately, at MyHeritage, Cathy has a tree, which is the first step, of course, but no common ancestor is shown in her tree.

MyHeritage has a wonderful feature called Theory of Family Relativity which are often based on “Smart Matches.” Click on “View theory.”

Click to enlarge

MyHeritage has found five possible paths to a common ancestor based on multiple documents and trees. In this case, Surrilda Claxton in my tree is the same person as Surelda Clarkson in Cathy’s tree, and MyHeritage made that connection correctly.

I confirmed this Theory at MyHeritage as accurate, and now I know how Cathy at the other vendor with no tree is related to me. I made a note about Cathy at MyHeritage on my match with Cathy at the other vendor too about our common ancestor AND where Cathy’s tree can be found. Add Cathy to her proper place in your trees.

Step 4 – Sleuth at the Same Vendor

At FamilyTreeDNA, when I find a match with no tree, I do two things.

Looking at Patricia’s profile, I immediately see that she has been assigned to the maternal side of my tree. I’ve linked other known matches which allows FamilyTreeDNA to use triangulation to assign Patricia to the proper side.

Then, I notice that even though Patricia doesn’t have a tree, she has provided her ancestral surnames.

Clicking on “View Details,” I can see if any of them match my surnames, or I can view all of her surnames.

Given that this is my mother’s side, these shared surnames give me an idea of a shared lineage.

Next, look for your closest shared match WITH a tree. Clicking on the two little people at far right displays your shared matches which are labeled “in common with.”

I share 122 matches in common with with Patricia, and our closest shared match, other than my mother who is not shown here, is Dennis. Dennis happens to be a known relative, which is why he already has a note.

But for purposes of this exercise, let’s say that I haven’t already figured out how Dennis and I are related. Viewing Dennis’s tree, I see that our common ancestors are Anthony (Antoine) Lore and Rachel Levina Hill. Hmmm, Hill is on Patricia’s list of surnames.

Sleuthing at the same vendor is MUCH EASIER when your matches have at least a couple of generations in a small tree. Having no tree is the most difficult situation at every vendor, but there are multiple ways to begin building a tree for your DNA match, or to expand a shrunken tree.

Step 5 – Google Is Your Friend

Google is your friend. Google cannot reach behind paywalled sites, so you won’t find records other than records from free indexes at Ancestry or MyHeritage in Google searches, but you will find information about people from other genealogy sites.

Let’s go back to Rolland Robison who died in 1963 and his wife, Chloe. And let’s also consider that his surname is often spelled RobiNson. We know from our match’s tree that Rolland’s wife’s first name is Chloe.

Look closely at the search box in the image below. By structuring the query as “rolland robison died 1963 wife chloe”, we combine a full name, a specific vital event year, and a spouse’s first name. This gives Google just enough precise detail to hopefully filter out (most) noise.

That’s interesting. It looks like Rolland can be spelled two ways too.

Not only is there an article (yes, I wrote about this previously), BUT there’s also an obituary and estate distribution in a local newspaper that I have never seen before.

Rolland’s wife’s birth surname is given in his obituary, even though her first name is misspelled. This is the link I need to establish our common ancestor, because Chloe is my grandfather’s sister.

Google can provide you with important links to information and articles that are not yet in genealogical databases, such as:

  • Facebook accounts for individuals: Useful for finding the tester, relatives or family connections.
  • Facebook groups and pages: Forums that contain local historical information and shared community memories.
  • LinkedIn & Instagram accounts: Social footprints that often reveal professional histories, geographic locations, and birth surnames.
  • Mentions elsewhere: Local newspaper archives, digital press releases, and published legal notices regarding estate partitions or land records.
  • Obituaries: Printed family notices that explicitly list surviving family names and relationships along with the Legacy.com tribute archives.
  • Public websites & genealogy blogs: Independent sites where genealogists sometimes publish deep-dive ancestral lineages. Always verify.

Google also provides an easy way to find free resources in public databases without having to search each one individually, including:

  • Collaborative family trees: WikiTree, FamilySearch, and Geni trees.
  • Cemetery registries: FindAGrave and BillionGraves.
  • Digital libraries: Internet Archive and Google Books, which hold a vast assortment of historical information like out-of-print town and county histories.
  • Open-Access portals: The Library of Congress (LOC) and the Digital Public Library of America (DPLA), which pulls photos, maps, and civic documents from libraries across the US.
  • Volunteer projects: Regional repositories like GenWeb.
  • Directories: Local alumni directories and digitized historical yearbooks.

Pro Tip: Resurrecting Old RootsWeb and Genealogy.com Breadcrumbs

RootsWeb was a wonderful resource for genealogists until Ancestry began systematically dismantling it in 2023.

While Google is fantastic at finding obscure text, it will occasionally point you to an old, broken RootsWeb link. Because Ancestry has frozen or removed much of the old platform, don’t let that 404 error stop you in your tracks. Copy the dead URL from Google and paste it into the Internet Archive Wayback Machine where you can sometimes resurrect the exact information you need!

The same methodology applies to the old message board, Genealogy.com.

Step 6 – Search Old Emails and Files On Your Own Computer

I know this probably sounds either ridiculous or incredibly obvious, but if you’re a typical genealogist, you probably have a quarter century of emails on your computer, not to mention reams of photos that you saved because someone gave them to you and you “might need them someday.”

I’ve never thought of myself as the family archivist, but I clearly must be, which is another name for the family packrat. Long live the packrats.

I’ve learned that I need to search all of my email folders for the names in someone’s shrunken tree. I’ve been shocked at what I’ve found there.

Don’t just search for full names. For example, Rolland Robison or Chloe Ferverda. Search for the names individually too. So, Rolland, Roland, Robison, Robinson, and Chloe. I didn’t know Chloe was a Ferverda yet when I was initially searching for her identity.

A middle-of-the-night insomnia-induced epiphany struck – “search your emails.” Who needs sleep? It’s overrated! I hopped right up, searched my emails and my computer and found even more.

As it turns out, I attended a Ferverda family reunion in 2010 where I only knew two people. Thankfully, cousin Cheryl thought to invite me, because someone brought an old photo album AND an old Ferverda family Bible. I took photos of everything in the album even though I had no idea who most of those people were and neither did the album’s owner.

Many photos had no surnames at all, or they were recorded as Mr. and Mrs. SoAndSo.

Here are “Chloe and Rolland” as they were named in the photo, with no last name or additional information.

Here are Mr and Mrs. Rolland Vincent Robison. I carelessly saved this one as Rolland RobiNson. My bad.

A search for just “Rolland” found both, which is exactly why you need to search creatively.

Finding those initially still wouldn’t have told me who they were, but I would have at least had some family context, given that a Ferverda descendant brought the album to the Ferverda reunion.

However, this article about Rolland and Chloe’s 50th wedding anniversary from that same album would have provided that missing context.

My emails revealed now-deceased cousin Cheryl referring to Aunt Chloey, but with nothing else to identify her. A search for simply “Chloe” found Cheryl’s emails.

More tidbits of evidence.

I did a very poor job of saving these images with useful names because they weren’t relevant at the time, although I did store them in a “Ferverda Reunion” folder. Now, I’m going to attach them to Chloe and Rolland’s profiles in my tree at both Ancestry and MyHeritage to make sure they don’t disappear forever.

I’m also going to send them to my match with the abbreviated tree. As Rolland and Chloe’s grandchild, if they don’t have these pictures, I’m positive they will want them.

I’m sure you’ve noticed that I got VERY squirreled during this process, but utilizing all of our resources is exactly how we make discoveries – and sometimes that includes chasing squirrels.

This is also why our research journals are important – so we don’t chase the same squirrel over and over.

Step 7 – Quick and Dirty Trees

I used the Robison example in an earlier article discussing how to build a “quick and dirty” tree. I use quick and dirty trees often because it’s the easiest way to keep track of informational tidbits from different places, including multiple vendors, during the research process.

I’ll say it again here. Quick and dirty trees aren’t meant to be public. They aren’t gospel. They are a structure for you to work through the various hints provided and to evaluate them to see if they are of sufficient quality for you to identify a common ancestor with a DNA tester who provided a minimal tree.

You can read about these investigative workbenches in the article, What is a Quick and Dirty Tree, and When Might I Need One?

What’s Next?

Have you decided which of your brick walls you’re going to focus on? Last week’s article discussed some of the criteria you might want to consider and how to prepare.

Select your ancestor, because next week, we’re going to begin using a variety of tools and techniques to track that ancestor. Bit by bit, we’re going to gather evidence that will hopefully lead to a breakthrough.

AutoKinship by Genetic Affairs Builds Family Trees from Your Matches at FamilyTreeDNA, and More

Genetic Affairs released a new AutoKinship tool designed for FamilyTreeDNA’s autosomal Family Finder matches, which also incorporates information from other sources. I must have fallen asleep at the wheel, because AutoKinship has been available for more than six months now.

I’ve been testing this tool with my matches, and it’s an immense help to those of us trying to untangle complicated family relationships using DNA evidence. I don’t know about you, but I have a long list of brick well where I could use help!

How to Use This Guide

This article is long and there are many steps involved – but it’s well worth it at the end.

My suggestion for using this article effectively is to read it through, at least once, to see what you’re going to be doing, and why.

Then, after you get things set up at Genetic Affairs, and any files you want to include, come back and use this article as a step-by-step guide to navigate these new tools.

Here’s the bottom line. The Genetic Affairs tools use matches, along with shared and bucketed matches at FamilyTreeDNA, plus their archived trees, in addition to external GEDCOM files and other information that you can provide in order to create customized, focused clusters and potential family trees for your clustered matches.

These tools combine DNA matching with internal and external trees for the composite best of both types of information.

So grab your favorite drink and let’s get started.

FamilyTreeDNA

AutoKinship works in conjunction with FamilyTreeDNA’s tools, such as Shared Matching, the Matrix tool, and Family Matching, also known as bucketing, which assigns parental sides to your matches using linked matches.

Linked matches are your matches whose relationship to you is known. If you haven’t already, link them to their profile card on your tree by clicking on “Link on Family Tree.” This allows FamilyTreeDNA, by using triangulation, to “bucket” your matches either maternally or paternally – meaning if they are related to you on your maternal side, paternal side, or both.

In my cousin Patricia’s case, the little pink icon by her profile picture shows that she has been bucketed maternally. That occurred when I linked my mother’s DNA to my tree because Patricia matches us both, plus other linked maternal cousins, on the same segments. For bucketing to occur, you don’t have to do anything except link known relatives to their proper place in your tree. FamilyTreeDNA does the rest by assigning your matches either maternally or paternally if they match on common segments.

Upload DNA Files to FamilyTreeDNA from Other Vendors

If you have not taken the Family Finder test at FamilyTreeDNA or uploaded your DNA file from 23andMe (Dec 2010 to present), Ancestry (May 2012 to present), or MyHeritage (March 2019 to May 7, 2025) to FamilyTreeDNA, you should do so now to take advantage of their tools, plus AutoKinship at Genetic Affairs.

What is AutoKinship and Why is it Different?

AutoKinship takes traditional clustering and kicks it up several notches. Instead of just showing you which matches cluster together, it actually attempts to build family trees based on the shared DNA amounts between your matches.

AutoKinship looks at how much DNA your matches share with you, and with each other, and uses that information to predict their relationships. Then AutoKinship builds potential family trees showing how everyone might connect. Additionally, you get to provide input in the process.

The timing couldn’t be better, especially since FamilyTreeDNA recently launched their updated Matrix tool, showing how your matches are related to each other. I wrote about that, here.

Two Steps

There are two primary steps in the AutoKinship process that build on each other. However, within these steps, there are many stepping-stones, so I’ve documented each one.

We’re going to use these tools, one at a time, in order.

I suggest that you join the Genetic Affairs User Group on Facebook for additional support and information.

Using AutoKinship with FamilyTreeDNA

The AutoKinship functionality for FamilyTreeDNA provides an automated approach using both AutoCluster and AutoKinship, together, then AutoLineage, where you can refine the information in a number of ways.

🔹 Step 1: Automated AutoKinship via Genetic Affairs

The first step involves running the AutoKinship tool directly from the Genetic Affairs members’ site. This process is fully automated:

  • It starts with the FamilyTreeDNA AutoCluster option, which groups DNA matches into shared clusters based on their connections to each other.
  • AutoKinship is then automatically launched on each cluster, adding the DNA tester and generating relationship hypotheses among the group.
  • Several family tree models are produced, showing how the matches and the tester could be connected based on shared DNA and cluster structure.

This step is ideal for getting quick insights into how groups of matches may relate.

🔹 Step 2: Refined Clustering & Relationship Analysis Using AutoLineage

After the automated run, downloadable files for AutoLineage are generated. These files allow you to re-import the match, shared matches, and tree data into the AutoLineage web application for further analysis.

This second step offers greater control and customization:

  • You can redo the clustering, optionally tweaking parameters to fine-tune how matches are grouped.
  • You can redo the common ancestor analysis, optionally tweaking parameters to fine-tune the discovery of MRCAs
  • The AutoKinship tool within AutoLineage becomes available again, this time with additional functionality:
    • Define known relationships between matches, such as parent-child or cousin relationships
    • Define generational information, for instance, if you know certain matches are not on the same generational level
    • Integrate MRCA (Most Recent Common Ancestor) data from reconstructed trees, e.g., from the Find Common Ancestors module.

This enhanced phase is especially useful for integrating genealogical trees for targeted clusters.

By combining both steps, automated clustering with AutoKinship, and manual refinement with known or tree-derived relationships using AutoLineage – you can leverage your FamilyTreeDNA data for in-depth relationship exploration.

Let’s Take AutoKinship for a Spin

As always, I’ll walk you through this process step by step, using my own DNA results as an example.

Getting Started

First things first – you’ll need to be a member of Genetic Affairs, so sign up for their free membership, here. Genetic Affairs’ customers purchase “credits” to spend on various features and reports, but you receive 200 free to start.

The automated AutoKinship analysis available on the Genetic Affairs website can be run using credits from the free tier – perfect for exploring the tool without any commitment. This allows users to generate relationship trees for FamilyTreeDNA clusters right away.

To access the more advanced features in the AutoLineage desktop application—including refined clustering, manual relationship input, and integration of MRCA data from reconstructed trees – you’ll need an active subscription.

To get started, sign in to the Genetic Affairs member site, here.

Let’s walk through the process step by step.

We’ll begin by registering a FamilyTreeDNA profile at Genetic Affairs. Click on “Register a new website” to get started.

FamilyTreeDNA account passwords are not stored at Genetic Affairs.

After clicking “Register profile,” you’ll see a message asking you to double-check the credentials for the kit you’re about to use. This is also a good time to log in to your FamilyTreeDNA account directly to make sure there are no pending actions — such as enabling two-factor authentication or accepting updated terms of service.

Once you click “I understand, continue,” you’ll see a list of all registered FamilyTreeDNA profiles at Genetic Affairs.

Locate the kit you want to analyze and click the blue “Start analysis” button.
This opens a guided wizard that walks you through each step of the setup.

First, select AutoKinship and click “Next.”

You’ll then be asked to define several thresholds:

  • Minimum and maximum shared cM
  • Minimum size of the largest segment
  • Minimum cluster size

A quick word of caution here: selecting a very low minimum cM value may actually reduce the number of usable matches. That’s because the system must download shared match data until it either reaches that threshold, or a preset timer expires, which can limit how much data is downloaded. When in doubt, start conservatively. You can always rerun the analysis later and change the parameters. Unfortunately, there’s no way to simoly “get everything” in one run which is, of course, what everyone would do.

Click “Next” to continue.

This section determines which matches will be included in the analysis.
For your first run, I recommend using the top matches within the selected range. This provides a strong foundation and usually produces the clearest results.

Later, once you’re more familiar with the output, you may want to experiment by analyzing only the shared matches of a specific person or group. For now, keep it simple and click “Next.”

Here, you’ll enter your FamilyTreeDNA password (twice) so the system can retrieve the required data.

If you use two-factor authentication, you can enter the 2FA code here, as well. To do that, log in to your FamilyTreeDNA account, retrieve the code from your email, and paste it into the wizard.

Then click “Next.”

You’ll now see a summary of all the settings you’ve chosen. Take a moment to review everything. When you’re ready, click “Perform analysis” in the bottom right corner.

At this point, the Genetic Affairs servers take over and begin processing your data.

The Results Arrive

When your report is ready, you’ll receive an email with a download link. You can also access it through the notification panel in the top right corner of the Genetic Affairs site.

Downloading the report will result in a zipped file. Save it in a location on your computer where you can find it.

Critical Step

This step is critical and will save you a great deal of frustration: If you’re using a PC, you MUST extract or unzip the files before you can properly use them. I can’t tell you how many people skip this step and then wonder why they’re receiving error messages. Ask me how I know!

This is your zipped file.

If you try to open the HTML file while it’s still zipped, it might appear to work at first, but when you click on any links within the file, you’ll receive an error.

If this happens to you, close everything, right-click on that yellow zipped folder, select “extract all,” and then try again.

Now you’re set up, so on to the fun part – viewing the results.

Exploring Your Results

Once you have everything properly extracted and open the HTML file, you’ll watch your AutoCluster literally fly into place on your screen. I love this part. It’s like watching my family fly into place. I wish the actual genealogy research was this easy.

The new Genetic Affairs reports include significantly more information than previous versions.

You can change what’s displayed using the dropdown menu.

By default, you’ll see the shared cM amounts between your matches, but you can change this to show paternal or maternal information if you’ve identified those lineages by linking your matches.

In my case, my maternal line has fewer matches because my mother’s ancestry includes both recent Dutch and German immigrants, so the majority of my high cM matches are US-centric on my father’s side. My father’s ancestors have been in this country since colonial times, and a lot of testers in the US are looking back to the old country for their origins.

Therefore, in my first several clusters, I see squares with the symbol P, indicating they are paternal matches – designated as such through linked family matches, aka bucketing.

You can see the faint Ps inside the orange cells.

Here’s a close-up so you can see the “P” for paternal. If you haven’t linked your matches, you won’t have bucketed matches. Your Genetic Affairs results don’t require bucketing – it’s just a really beneficial feature.

You can change your AutoCluster settings in several ways. I tend to start with the defaults and then modify from there.

Genetic Affairs functions based on the amount of server time a particular tool takes, so it’s not possible to just “run everything,” or trust me, I would.

The Common Ancestor Magic

In your report, scroll down several sections, and you’ll find Common Ancestors – my favorite feature.

This section shows you the common ancestors that have been identified between your matches’ trees.

Looking at the Common Ancestors cluster report, you can click on three things for each cluster:

  • FamilyTreeDNA Trees of Cluster #
  • Common Ancestors of Cluster #
  • Common Locations of Cluster #

Let’s examine the reconstructed trees based on the common ancestor analysis. The first cluster shows some of my close DNA matches that are descendants of my Vannoy line.

You can see that there are six testers, in addition to me, who descend from Joel Vannoy.

Next, scroll down to the AutoKinship section of your report.

The AutoKinship Analysis

The real treasure lies in the AutoKinship analysis, which is presented in a small table on the main HTML page. When you click on the AutoKinship results for any cluster, you’ll see reconstructed trees based on the shared DNA amounts between matches, meaning between you and each of them, and between each other.

You can see that I have 10 reports available based on the cluster numbers indicated.

I clicked on Cluster 1, which shows some of my close DNA matches who are Vannoy line descendants. This includes testers both with and without trees.

Since the AutoKinship algorithm doesn’t have access to age information, it sometimes struggles with generational differences – but the relationship predictions are still remarkably useful.

Alternative trees are also provided, giving you multiple hypotheses to investigate.

Some matches may not be integrated because of incompatible relationships.

The Next Step with AutoLineage – Adding Genealogical Trees to the Mix

We’ve seen AutoTree and AutoKinship. The new upgraded AutoLineage adds genealogical tree information to genetic information by allowing the user to:

  • Import other trees
  • Integrate most recent common ancestors (MRCAs) in AutoKinship trees
  • Set known relationships
  • Provide generational information.

AutoLineage, Genetic Affairs’ online clustering and tree-building tool, has been around for several years but was recently upgraded to create trees based on shared DNA and incorporate genealogical evidence.

This is where the proverbial rubber meets the road.

Setting Up AutoLineage

Return to the home page at Genetic Affairs and select AutoLineage.

If you’re new to this tool, you’ll see a simplified workflow on the start page that walks you through the process.

First, create a profile representing the DNA test taker – in my case, that’s me.

After creating the profile, you’ll be redirected to the landing page of the profile. From there, you can register DNA tests linked to the profile. From the home page, you can see the different profiles.

You’ll register a new FamilyTreeDNA test specifically for each user whose kit you manage and who took a test.

FamilyTreeDNA is the only DNA testing company for which Genetic Affairs runs automated analyses on their site.

Additionally, you can:

Importing the Data

After registering a FamilyTreeDNA test, you are redirected to the overview of this DNA page, where matches are imported.

Click on “Import matches” and select the CSV file from Genetic Affairs. Here’s where that AutoKinship report we generated earlier comes in handy. The unzipped report contains match and shared match information that we can import directly into AutoLineage.

Navigate to the gephi folder in your report and select the nodes.csv file to import your matches.

After importing the matches, a short dialog shows how many matches were imported.

After closing the dialog box, the DNA matches pane is opened.

You’ll see your DNA matches that were downloaded.

Next, import the shared match information from the edges.csv file in the same gephi folder.

Once both data sets are imported, you’ll see that the ICW (In Common With) column has populated, showing how many shared matches are available for each DNA match.

Clustering in AutoLineage

Now, with the shared match data loaded, you can perform your own clustering analysis.

The wizard allows you to set parameters for which matches to include based on:

  • The amount of shared cMs
  • Weighted or unweighted clustering
  • How much DNA is shared between shared matches

You can also define the cluster characteristics, from sparse to very dense clusters.

Last, you can select the coloring scheme. After setting the parameters, click on “Start Clustering,” at bottom right.

After clustering is finished, the clustering chart is displayed. It looks fairly similar to the ones obtained automatically from Genetic Affairs, but with some differences.

The first thing I noticed is that the large orange cluster 1 in the automated clustering is now mostly represented by the purple cluster 4.

Let’s zoom in on this cluster. By looking more closely at the numbers contained in each cluster, you can already make an estimated guess about the richness in relationship information for cluster members. This cluster has lots of close relationships. Clusters whose matches only share a small amount of DNA with each other are not the best candidates for an AutoKinship analysis because they most likely share a distant common ancestor. Unless, of course, it’s a distant ancestor you’re searching for. (Hello brick wall.)

Adding and Importing Tree Information

Now that we have the new clusters, we could continue to directly run the tree reconstruction on these clusters using the shared DNA information, but let’s wait  since we want to include the tree information as well to guide this process.

To use common ancestors, we need to import the available trees that are linked to the DNA matches. Luckily, just like (shared) match information, the tree information is provided with the automated analysis as well. Let’s import the data.

First, navigate to the tree management page. As you can see, no trees have been created or imported. Let’s start the wizard by clicking on the “Import Trees” button.

An “Import tree” wizard pops up, providing different ways to import tree information. It’s also possible to import GEDCOM files or tree data from other resources, but for now, I’m only using the archived trees at FamilyTreeDNA.

Click on the last option and select the files.

Navigate to the matches folder and select the HTML files contained in the folder.

Each file represents a DNA match report, some of which have a tree associated with them.

After importing the trees, they are automatically associated with the concerned DNA matches (using the unique identifier present in each file name). The tree overview page shows which tree is linked to a profile or DNA test, and the amount of DNA shared with the linked DNA match.

If you have created trees for your matches based on your own research (like quick and dirty trees), now is the time to import these using the “Import Tree” wizard again. This is a wonderful feature, because it means you’re not entirely dependant on your match having uploaded a tree themselves.

If you don’t import trees from GEDCOMs, you don’t need the linking wizard.

Click on the “Import Tree” wizard and select the GEDCOM option.

Now that we have imported additional trees, we need to associate them with DNA matches.

You can use a wizard to link the unlinked trees to the DNA matches, or link them from each DNA match. The wizard will try to guestimate, based on the content of the tree file name, which DNA match could be associated with the tree. Change the search criteria if it does not provide the correct results.

TIP: Save the GEDCOM files with the name of the linked DNA match as well the shared cM, which speeds up the importing process

Don’t forget to import your own tree. I imported my GEDCOM file from my computer genealogy software and associated it with my profile so it’s included in the common ancestor identification. You can easily upload your GEDCOM from your computer software, or download your tree from either Ancestry or MyHeritage to upload here.

Visit the profile, and select the tree pane. The tree pane only shows a single individual and allows you to add ancestors to it manually. To associate that individual with an existing tree, click on “Link to Existing Tree”.

A wizard will be displayed, which shows all available trees on the left side. Sort by clicking on the “Created” column to display the most recent trees.

Next, you need to select the root person.

I selected my tree.

Next, the right side of the wizard fills with the people in the selected tree. Select the root person, which is me, and click on “Save” in the lower right corner.

Finding Common Ancestors

Now that we have associated a tree with the profile and imported trees for the FamilyTreeDNA matches, it’s time to locate some common ancestors. Fingers crossed!

Go back to the profile and select the profile overview. Scroll down to the “Find common ancestors” section and click on the “Find common ancestors” button.

The “common ancestors” wizard shows trees that are associated with this profile in the table on the left and provides information about the different steps on the right. You can change the settings to make the search more restrictive or more relaxed.

After running the common ancestor identification, a dialog shows the number of trees and tree persons that were used, and the number of common ancestors that were identified.

After the analysis runs, you’ll be able to view all reconstructed trees or filter them based on common ancestors, trees, or linked DNA matches.

Common ancestors, not surprisingly, often align closely with what the automated analysis discovered.

All six testers are now shown descending from our common ancestor, in the approximate location where they will fit in our common tree.

But we aren’t quite finished yet.

The Final AutoKinship Analysis

Finally, we’ve arrived. The earlier steps were necessary to pave the way.

We have the common ancestors and clusters, and it’s time to go back to the clusters to begin the reconstruction of trees using trees combined with DNA.

Click on the profile and go to the clustering results pane. Select the 1x view, which will show the clustering chart.

Now select the matches pane that shows the different matches that are contained in each cluster. Scroll down until you reach your cluster of interest, which is four for me.

After clicking on any cluster, you’ll be redirected to a cluster view with only the information for that particular cluster.

Let’s view purple cluster 4, which looks fairly dense, with only a couple of empty cells, indicating that these shared matches with white cells did not share (enough) DNA with each other to be included in the cluster. Now select the matches pane in the dashboard at the top of this cluster, which displays the matches linked to this specific cluster. As you can see, a button is now available that allows us to run the AutoKinship analysis. Click on the button.

Single cluster matches are displayed.

Now back to the wizard.

The wizard provides several important parameters:

  • Maximum number of generations between DNA matches
  • Number of trees to analyze in each iteration
  • Final number of trees to keep
  • Whether to include known relationships and/or MRCA (Most Recent Common Ancestor) relationships

In this example, MRCA relationships were found because we performed the common ancestor identification that resulted in common ancestors between the matches of this cluster.

If you know specific relationships between matches, you can set those manually. Sometimes you might not know the exact relationship, but if you can estimate that a match is one or more generations older or younger than yourself, you can set that too.

In addition to setting the relationship between the test taker (indicated in green in the table) and the DNA matches, it’s also possible to set the relationship between shared matches, if known.

The Hybrid Results

After the analysis has finished, an overview of the identified trees is presented.

The final result is a blended tree where DNA evidence fills in the blanks for matches who haven’t uploaded trees, or you haven’t provided a tree, and known genealogy supports the structure where it exists. This hybrid approach gives us the best of both worlds – the precision of documented genealogy combined with the discovery power of DNA analysis.

I particularly like this approach, because when I identify how a DNA match is related to me from any vendor, I enter their lineage in my desktop genealogy software. Therefore, using that GEDCOM file is the most complete source of my identified relatives.

Testers 1-6 were shown using the regular AutoTree, without the integrated tree, but an additional 11 matches were placed for consideration using all available tools.

I was using this as an experiment because I know how most people in this cluster are related, and those are all placed accurately. There is one person, located on the branch between 1 and 5, who I had no idea how they fit into this puzzle. Now, at least I know where to look.

I can’t imagine trying to do all of this manually.

Why This Matters

For those of us dealing with unknown parent or grandparent situations, poorly documented lines, non-existent trees, or just plain stubborn brick walls, this combination of tools is nothing short of amazing. You can now explore relationship hypotheses even when traditional documentation is scarce.

The reconstructed trees show how common ancestor information provides the template, while the AutoLineage tool fills gaps using shared DNA information. The updated AutoLineage is the genealogical assistant that never gets tired and can deal with relationship possibilities much more effectively than traditional hand-based methods.

In Summary

If you haven’t explored Genetic Affairs recently, give it a look. The integration between AutoKinship and AutoLineage represents a significant step forward in DNA analysis.

While AutoKinship offers valuable insights on its own, its full potential is truly unlocked when you export the data into AutoLineage. The combination creates a comprehensive analysis that was previously impossible.

For researchers dealing with complex family relationships or challenging genealogical puzzles, this hybrid approach that combines matches at FamilyTreeDNA with DNA evidence and genealogical trees could be the key to breaking through stubborn brick walls that nothing else has budged.

Last but not least, I suggest reading Dr. Patricia Coleman’s blog articles about these tools and her methodologies here and here. Patricia works extensively with these tools, and I often recommend her for private autosomal research consultations. Patricia’s 2026 RootsTech Session, DNA Case Study: Finding an 1877 Birth Father with Genetic Affairs, BanyanDNA, and No Birth Record, details her work solving a long-standing problem for my cousin in the Speaks family.

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

RootsTech 2025 – The Year of Discover and the New Mitotree

Last week, RootsTech was a whirlwind and full of discoveries – which, ironically, was the 2025 theme.

I always take you along with me and share the RootsTech experience, start to finish, so here’s my 2025 “feet on the ground” report.

I might, just might, have overcommitted myself. I taught the half-day DNA Academy,  three more sessions, plus several other commitments such as book signings, get-togethers, and interviews.

One class, “DNA for Native American Genealogy,” was a live webinar from the floor of the expo hall. You can watch that here for free, if you’re interested.

Unfortunately, none of my other sessions were recorded, but I’ll see what other alternative options may be available to bring those to you.

Additionally, I did two book signings at the GenealogyBank booth, along with two other authors, Drew Smith and Sunny Morton. I’m sorry, I don’t have any pictures. I should have asked someone to take some.

There were long lines and books sold out. Still, you can order either of my books, The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA or DNA for Native American Genealogy, at Genealogical.com. Thank you to GenealogyBank for being so welcoming.

The book signing was particularly fun because people shared their success stories or their hopes of what they want to achieve. I met a couple of new cousins too! Even people waiting in line were helping each other with information about research resources.

I had created my “RootsTech plan” for sessions I wanted to attend, but I was only able to actually attend one of those. Several were happening at the same time as mine, or directly before or after. As a presenter, you arrive early to get set up and make sure everything is working correctly.

Then, after your session, attendees have questions and are interested in your topic, which is a good thing. So essentially, you can’t attend sessions either before or after your session either.

Before I share photos, I’d like to share something else.

It’s About the People

I have never attended RootsTech for the classes, although there are wonderful offerings – and I have enjoyed them immensely.

Having said that, for me, the best part of RootsTech is the people. People I know and love but never get to see – many of whom I met in-person at RootsTech initially. I get to meet my blog followers. I meet with or reconnect with friends and cousins from around the world. I am privileged to talk with people about their challenges and their victories – when they’ve broken through a brick wall using DNA that they could never have otherwise achieved. People collaborating and helping each other. It’s all beautiful.

The reason I started blogging in the first place, and the reason all 1750 articles are free, is because I wanted to help people do just that – confirm ancestors, find ancestors, and connect with their fsmily.

My cousins that I’ve met through genealogy are some of my closest friends and closest family members. Outliving everyone is a mixed blessing but it makes me extremely grateful for my various cousins since all of my siblings and close family, with the exception of the next generation, have transitioned to the land of the ancestors.

So, yea, for me, RootsTech is about connecting and reconnecting with the people.

That’s also why I never get anything done because I’m always talking with someone.

Additionally, this particular RootsTech was a celebration.

Mitotree Release

Just a few days before RootsTech, the Million Mito Team at FamilyTreeDNA released the brand new Mitotree, 5 years in the making, reconstructing the tree of humankind to reflect our combined heritage more accurately.

At RootsTech 2020, I was honored to announce the Million Mito Project, and the new Mitotree initiative was born.

At some point, I will write about the deep, personal significance of the Mitotree for me,  but for now, suffice it to say that there is something profoundly moving about rewriting the tree of humankind and in doing so, giving a voice to our ancestors from long ago. Yes, I know many of them are thousands or even tens of thousands of years old, but had they not survived, we would not be here today. Now we can identify who they are and that they lived.

Million Mito Team, left to right, Goran Runfeldt, Dr. Paul Maier, me, Dr. Miguel Vilar, Bennett Greenspan, John Detsikas

Our amazing Dream Team has given life to our ancestors and said their names once again, even if their name is a mitochondrial DNA haplogroup. Four team members, Goran, Paul, me and Bennett were at RootsTech. Where else can you actually approach and speak with the actual scientists?

When I say RootsTech is about the people, I know that I am related to every single individual at RootsTech, it’s just a matter of how far back in time. So are you.

Just think about the significance of that for a minute.

Every. Single. Person.

The other end of the mitochondrial DNA spectrum is genealogy, of course, and the new Mitotree with it’s haplotype clusters brings mitochondrial DNA results into the genealogical timeframe. In future articles, I’ll be writing about each one of the new tools, what they mean, and how to use them.

Dr. Paul Maier, lead scientist doing most of the hard science behind Mitotree, had the much-deserved honor of introducing the Mitotree to genealogists at RootsTech.

I’m not sure the audience understood they were witnessing history unfold, but they clearly were. We needed a drum roll and some balloons!

This wasn’t like most vendor announcements of a new product or feature – this was a major scientific achievement that led to genealogical benefits.

In celebration, I asked my friend to make double helix zipper pulls so that I could give them to colleagues, friends and cousins that I ran into at RootsTech. It’s my way of celebrating and sharing the joy!

Five years is a very long time to work on a project. The Mitotree is a massive accomplishment. Every customer at FamilyTreeDNA who has taken the full sequence test received their new haplogroup either the week before or during RootsTech, AND, the second updated version of the tree was released too.

While this is truly wonderful, the true highlight is the testimonials – seeing how Mitotree is actually helping people break through their brick walls.

Here’s just one.

Breathless Testimonial

I’m going to try to convey this exactly as it happened.

A lady that I don’t know literally runs up to me in the hallway. This isn’t unusual. She was so excited that what she said was one long breathless sentence, which I’m going to try to reconstruct here, although I’m adding a bit of punctuation. I also can’t remember how many “greats” were attached to the “grandmother,” but you’ll get the idea.

Roberta, Roberta, I’m so excited – I just wanted to let you know – I found my ancestor using mitochondrial DNA. I got my new haplogroup and I had like 47 matches before but now they are clustered together so I could focus…and there were three matches in my cluster…and one of them had an EKA but the other didn’t…so I built out the EKA matches’ tree and guess what??? They were from the same place and then I found that her great-great-grandmother’s sister is my great-great-grandmother but she had her surname so now I have more generations too. OMG I ‘m so excited I could never have broken through this wall without mtDNA because I had no surname. This is THE MOST CONSEQUENTIAL DNA TEST I’VE EVER TAKEN, and I’ve taken them all. Thank you, thank you!

And with that she quickly hugged me and ran off to something she was obviously late for.

I never got to say one word, which was fine, but I stood there with tears in my eyes, thinking to myself, “This – this is what it’s all about.”

It doesn’t get better than this!

I want to hear your stories too. I just scaled my fourth brick wall last night using the new Mitotree and mtDNA Discover features.

RootsTech Week

RootsTech week started early for me – as in leaving the house at 3 AM Sunday. I fly on Sunday because the flights are cheaper and because the pre-conference meetings and events begin on Monday.

We took off into the dawn, jetting our way westward through the azure blue sky.

I have never gotten over the majesty and beauty of the Rocky Mountains.

And then, of course, the Great Salt Lake, for which Salt Lake City is named.

Looking at the Salt Palace across the street from the Marriott hotel. The silver building is the new Hyatt which is attached to the conference center behind the windmills which extends another very long block to the right, out of view. The mountain range is visible in the distance, and the beautiful sunset.

Speaking of the Marriott hotel, several people have asked if it was any better this year, and if I got trapped in the fire exit again, like last year.

No, I didn’t get stuck because I didn’t tempt fate again. It looked just the same though, so I’m presuming nothing has changed. Furthermore, there was no heat in my room, so they gave me a space heater and a pass to the concierge level – which they did not do last year.

That was kind of them, but food ran out, and there was only one poor server in the restaurant. I’m not even going to mention the nauseating thing that happened with my food. Let’s just say I’m not picky, but I will NEVER eat there again, and that makes it particularly difficult because there’s very little close by, especially when you’re exhausted.

I’m hoping that RootsTech will negotiate someplace different for speakers in the future. I’ve stayed in a lot of Marriotts and most of them are just fine. I have never had issues like this with any of them, let alone repeat issues year after year.

The good news is that we’re not there for the hotel, and the fun began on Monday.

Monday

My interviews began on Monday morning with “Mondays with Myrt” at the FamilySearch Library, which you can view here beginning about 16 minutes.

Mondays with Myrt is a RootsTech tradition and Myrt incorporates people present in person and tuning in virtually as well. Left to right, Kirsty Gray from England, John Tracy Cunningham, me and Myrt. Kirsty had a huge breakthrough that she shared with us just a few minutes after it happened.

I met John at the ECGGS Conference last October. He’s one of the few people I know whose 8 great-grandparents were born in the same county. I’m so jealous. Mine were either born in or first generation immigrants from four countries.

Sometimes the broadcast waiting area is just as much fun as the actual broadcast – in part because it’s the first day of RootsTech week and everyone is so excited to see their friends that they haven’t seen in forever. Call is a reunion!

Do Kirsty Gray and I look like we’re about to get into mischief?

Behind me is the first group of folks to be interviewed.

Pat Richley-Erickson, aka Myrt, Cheryl Hudson Passey, Laura Wilkinson Hedgecock, and Jenny Horner Hawran.

This is the livestream room at the FamilySearch Library. The waiting area for the next group is to the right, and the three presently being interviewed are sitting on the left beside Myrt.

For those who know Gordon, aka Mr. Myrt, he’s coordinating interviewees outside the livestream room. His job is herding cats and he’s the nicest cat-herder you’ll ever meet!

Pre-RootsTech Library Research

I love the FamilySearch Library. It feels like coming home to me.

So many passionate genealogists at every level – learning and searching. Lots of volunteer helpers available, too.

Normally, I create a research plan for the library, but I had been so utterly slammed between preparing my several RootsTech sessions and the Mitotree release that I hadn’t really been able to prepare anything.

I did, however, have a group of ancestors in mind that settled in the Oley Valley in Pennsylvania, so I decided to focus on the Berks County books.

I won’t bore you with the details, but among other things, I found confirmation that the Hoch surname is also the same as High and Hoy, which explains some very confusing Y-DNA results. So even though I didn’t get much productive time there, I did find something very useful in the land records.

I also ran into cousins and friends, of course, which is why I didn’t get more actual research done.

I knew Judy Nimer Muhn, at left, was going to be at RootsTech as a speaker, and I knew we connected through Acadian lines, but we never took the time to really piece together that puzzle.

My cousins, Mark and Manny were also coming for RootsTech, and to visit the library, for the first time. Mark, Manny and I visited Nova Scotia together in the summer of 2024, chasing our ancestors.

You know, fate is a funny thing.

We all descend from Acadian, Francois Savoie who was born about 1621 in France, but settled in Acadia, today’s Nova Scotia. Mark, Manny and I knew that we are cousins through Francois, but Judy and I did not. Mark, Manny and I ran into a local historian, Charlie Thibodeau, the Acadian Peasant, last year, outside of Port Royal. It just so happened that he was taking another couple to see the remains of the Savoie homestead deep in the salt marshes at BelleIsle.

We asked if we could join them, and Charlie was kind enough to include us. It was a long, brutally hot, tick-infested hike through the swamp, but oh so worth it!

We also found the well, located between three homesteads.

The year before, Judy had been in the same place in Nova Scotia, found the same man, Charlie, at the BelleIsle Hall Acadian Cultural Centre, and he had taken her to the remains of the same homestead.

And here we all four are in Utah.

What are the chances?

Needless to say, we had a LOT to talk about, and still do. Unfortunately, I wasn’t able to get to Judy’s talk, but Mark and Manny attended.

I ran into Katy Rowe-Schurwanz, the FamilyTreeDNA Product Manager at the library too, and look what she’s wearing – a mitochondrial DNA scarf. How cool is that!

The rest of Tuesday and most of Wednesday morning were spent trying to update my several presentations to reflect newly released information by various vendors and practicing the timing of the presentations. I had another interview, and more people were arriving.

I found time to visit Eva’s Bakery about 3 blocks from the Salt Palace. If you’re ever in Salt Lake City, Eva’s is a must! Lunch is wonderful, and so are their French pastries.

Wednesday is “tech prep” day at RootsTech, along with speaker instructions and then the Speaker Dinner.

Steve Rockwood, President and CEO of FamilySearch always delivers an inspirational message and this year did not disappoint.

If you’ve wondered about RootsTech conference stats, they provided this information. I can’t even imagine trying to coordinate all of this – and that’s not including the vendors, expo hall, technology in the presentation rooms, food, security and so much more.

Last year, in 2024, the final attendance numbers were more than 16,000 people in person and 4 million virtual attendees. I noticed a few days ago that there were more than half a million people participating in Relatives at RootsTech, which is still live until April 12th.

On Wednesday evening, after the Speaker’s Dinner, vendors in the Expo Hall were putting the final touches on their booths and preparing for the thousands of excited genealogists who would descend Thursday morning.

Discover

This year’s RootsTech theme was “discover” and attendees were greeted with this display just inside the door.

Attendees listed their discoveries on Post-its and could either post them on the board or plastic boxes, or on the green tree.

I placed my discovery from the day before at the library on the Rootstech tree.

Some people place their wishes here, kind of like a technology wishing well.

I couldn’t help but think of the new Mitotree, now forever green and growing, so I posted a second discovery, “Mitotree.”

Thursday – Opening Day

For those who don’t know, the Salt Palace Convention Center is two lengthy blocks long, a block wide, and two or three stories high, depending on whether you are in the front or rear portion. In other words, it’s massive and you need a map!

The huge Expo Hall with vendors is located in the center on the first floor and vendors have aisle addresses. The show floor is always very busy, and this year was no exception. One of the things I love is that spontaneous conversations just spring up between people who often find commonalities – common ancestors, common locations, and more. People compliment each other and join others at tables. It’s like a big family gathering of sorts.

I always try to walk the entire Expo Hall, because I really enjoy seeing the vendors and their wares, but this year, I never actually had enough time to traverse all the aisles. I took several pictures as I was passing through and running into people, but not nearly enough. I know I missed a lot, but there just wasn’t enough time and I arrived at RootsTech already tired.

However, the energy of RootsTech is like no place else and just infects you.

It’s like you can’t drink from the genealogy firehose fast enough!

Let’s Take a Walk

Ok, come along on a walk with me.

Left to right, Lianne Kruger, a speaker, and Courtney, in the FamilyTreeDNA booth. I believe they said they are cousins.

Daniel Horowitz, genealogist extraordinaire, in the MyHeritage booth. More about MyHeritage’s announcements shortly.

Geoff Rasmussen in the Legacy Family Tree Webinars booth. For those who don’t know, there’s lots of good material at Legacy, and the freshly recorded webinars are always free for a week.

Several vendors offer booth talks, including MyHeritage. I love their photo tools and use their site in some capacity almost daily.

One of the RootsTech traditions is ribbons. Collect one, collect ‘em all. Liv’s ribbons almost reach the floor. I think she wins!

Selfies are also a RootsTech tradition. Me, here with Jonny Perl of DNAPainter fame. I owe Jonny an apology as he asked me if I had a minute, and I had to say no because I was on the way to one of my own classes. I never got back to his booth to view his new features. Sorry Jonny – don’t take it personally!

Jonny released a new Ancestral tree version titled Places, so take a look here at his blog. I need to go look at my ancestors Places.

You’ll find this new feature under Ancestral Trees, Places. These are my most recent 8 generations. Just think of all those brave souls who climbed on a ship and sailed for the unknown. Check this feature out and have fun.

In a booth talk, Dave Vance, Executive Vice-President and General Manager at FamilyTreeDNA is speaking about the three types of DNA, which are, of course, Y-DNA, mitochondrial and autosomal DNA – all useful for genealogy in different ways.

Dave is explaining how in-common-with matches, also known as shared matches, operate with the chromosome browser. You can use the chromosome browser, shared matches, the new Matrix Tool, and download your match segment information at FamilyTreeDNA, a combination of features not available at any other vendor.

WikiTree, a free a moderated one-world-tree is one of my favorite genealogy tools. One of their best features is that you find your ancestor, and in addition to lots of sources, their Y-DNA, mitochondrial DNA, and those who are related autosomally are listed. Here’s my grandfather, for example.

Several DNA connections are listed. The further back in my tree, the more DNA connections are found, becuase those ancestors have more descendants.

WikiTree volunteers were wandering around taking pictures of “WikiTreers” holding fun signs.

Paul Woodbury, a long time researcher with Legacy Tree Genealogists, who specializes in DNA. I don’t take private clients anymore, and regularly refer people to Legacy Tree.

Me with Janine Cloud taking our annual RootsTech selfie. Janine, the Group Projects Manager at FamilyTreeDNA and I co-administer one of those projects and accidentally discovered a few years ago that we are cousins too. How fun is this!!!

I wanted this shirt, but by the time I got back to the booth, it was too late. I’m going to order it online from Carlisle Creations, in case you want one too. This is so me.

Land records are critically important to genealogists. Rebecca Whitman’s class was about plotting land plats. What she’s holding is a surveyor’s chain. You’ve read about chain carriers? This is what they carried to measure land boundaries – literally metes and bounds. Some of my best discoveries have been thanks to land records.

The only session I actually got to attend was Gilad Japhet’s “What’s New and Exciting at MyHeritage.” For those who don’t know, Gilad is the founder and CEO of MyHeritage and it’s always great to hear about the new features straight from the top executive who is, himself, a seasoned genealogist. That’s why he started MyHeritage in the first place – 22 years ago in his living room.

Gilad had several wonderful announcements, but the one I’m most excited about is their new Cousin Finder. Cousin Finder finds and reveals cousins who are DNA candidates if they have not yet taken a DNA test.

I’ll be writing more about the MyHeritage announcements soon, but you can read their blog about Cousin Finder now, here, and their Roundup here about the rest of their announcements!

My Last Class – Reveal Your Maternal Ancestors & Their Stories

My last class at the end of the final day of RootsTech was “Reveal Your Maternal Ancestors & Their Stories – Solving Mitochondrial DNA Puzzles.”

Had I tried to coordinate this presentation with International Women’s Day, I could never have done it, but fate winked and here I was.

I’m often asked what it’s like from the presenters’ perspective. This is one of the smaller ballrooms. My earlier sessions were in larger rooms, maybe 3 times this size. I took this picture about 15 minutes before the session started as people were beginning to drift in.

The amazing RootsTech techs had me wired up to microphones and had verified that the audio and video equipment was working correctly, so now it was just waiting.

My cousin, John Payne, who co-administers the Speaks surname project with me, came by and took this great picture of the two of us. We’ve made huge inroads connecting the various Speake(s) lines in America, plus finally proving our home village in England, thanks to the Big Y-700 test, followed by church records. All is takes, sometimes, is that one critical match.

As I sat there, waiting to begin the mitochondrial DNA session, I couldn’t help but reflect upon all of the women who came before me and how fortunate I was to have been in the right place at the right time to be a member of the Million Mito team.

These are my direct matrilineal ancestors who give me, and my daughter, pictured at left, their mitochondrial DNA. I felt them with me as I sat there, waiting.

The woman at furthest right, Barbara Drechsel (1848-1930), immigrated to Indiana from Germany as a child with her parents in the 1850s. Before her came thousands of generations of women with no photos, of course, and no names before Barbara Freiberger, another eight generations earlier, born about 1621 in Germany.

Before that, which was before church and other records, prior to the 30 Years War, this lineage came from Scandinavia where some of my exact matches are still found today.

Before beginning, I said a positive affirmation and thanked my ancestors – so very honored to introduce them. I know they were proud of me, a member of the team that opened the door to the distant past. I wouldn’t be here if not for every one of their lives.

In this session, I would discuss, for the first time ever, the new Mitotree and my/our connection to all of humanity some 7000 generations ago, more or less.

The mutations we carry over those generations form an unbroken chain of breadcrumbs, connecting us to mitochondrial Eve who lived about 145,000 years ago. We revealed that breakthrough finding in the Haplogroup L7 paper, published in 2022.

I’m still in absolute awe that we have been able to both reach that far back in time AND, at the same time, make the newest haplogroups and haplotype clusters genealogically relevant. I will write more about that soon, but for now, I wrote about the Mitotree release here and you can find articles by Katy Rowe-Schurwanz here and here.

I’m very excited about my new mitochondrial DNA results for my ancestral lines that I track and have already made headway on several.

I’m not the only one.

Not only was I excited about my results, many other people have had breakthroughs too, including Mark Thompson, one of our genealogy AI experts who also spoke at RootsTech. I particularly love his AI generated image.

If you haven’t yet, check your mitochondrial DNA results.

It’s a Wrap

Another year done, another RootsTech under our belts. Hopefully everyone is over the “conference crud” by now and are busily applying their newfound knowledge.

You can view either live-cast sessions or RootsTech webinars, here.

I saw a meme posted sometime during the conference that coined the term “exhausterwhelmulated,” a combination of exhausted, overwhelmed and overstimulated at the same time.

I added exhilarated and elated to the mix and asked ChatGPT to draw me a picture of someone at a genealogy conference feeling those simultaneous emotions.

ChatGPT titled this request “Genealogy Conference Overload,” which made me laugh.

The first two attempts looked like the person had a headache, which I fully understood, so I asked ChatGPT to make the person look happy to be there.

This person, carrying a coffee like I often do, looks like they have just discovered the great irony that they have chased the wrong ancestor for some 20 years – with “laugh or I’ll cry” mania being their overwhelm “go to” in that minute.

This one made me laugh too!

Yes, indeed, I think every single one of us, especially at RootsTech, has experienced this exact adrenaline-fueled emotion.

We leave with a VERY long to-do list, exhausted but full of anticipation and buoyed by excitement. Filled with so much gratitude for our cousins and fellow genealogists, the speakers, vendors, DNA to solve thorny problems, new tools and records, FamilySearch who sponsors RootsTech itself and their amazing employees, plus the legions of the volunteers who make it all work.

Thank you! Thank you! Thank you!

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

FamilyTreeDNA’s New Matrix Shows How Your Matches Are Related to Each Other

Click on any image to enlarge

FamilyTreeDNA’s new reworked Matrix includes relationships, in other words, how your matches are related to each other. But there’s more. It also includes the number of shared segments and the number of cMs shared between your matches.

You can then push those matches through to the chromosome browser to see exactly which segments overlap between you and your matches.

This is a game-changer!!

Why Are These Features Important?

For genealogists, knowing how your matches are related to each other, or not, is a HUGE clue about your common ancestor. Clusters of people who match each other are an important road sign directing you to a specific ancestor who contributed the same DNA segment or segments to all of you.

FamilyTreeDNA just released several VERY cool updates for their Matrix comparison tool. Plus, you get to select a group of 10 people to compare.

The purpose of the Matrix tool is to select Family Finder autosomal matches who are then displayed in a grid matrix for comparison, showing if and how those matches match each other.

Specifically:

  • Do your matches match each other?
  • What is their estimated relationship to each other?
  • How many segments of DNA do they share with each other?
  • How many cMs (centiMorgans) of DNA do they share with each other?

You can then push 7 matches through to the chromosome browser to see if they match on any of the same segments.

Automated Triangulation

If you are comparing bucketed (maternal or paternal) matches, or matches known to belong to the same side of your tree, the shared segments are automatically triangulated.

How cool is this?!!!

Keep in mind, though, that you may be related to someone through multiple ancestors, and they could be from both parent’s sides, so pay attention to the ancestral segment history.

Remember, every segment has its own unique history.

Let’s step through the new Matrix features and see how they work.

Select the Matrix

Navigate to the Matrix tool under “See More” under Autosomal DNA Results and Tools.

Under “Select Matches” you can select “All Matches” to choose from all of your matches, or you can select a grouping of matches to be displayed in the menu, below.

These groupings are shortcuts for you so you don’t have to pick everyone individually. You can also search for a name.

Click on the individuals you want to compare in the Matrix. The people you’ve selected from the group, at left, will appear in the box, at right. That’s who will be compared to each other.

Next, select which type of data will be compared.

I’m selecting “Close Relatives” for this example and “Relationship range.” First, I added my mother so I could see who matches with her.

Then I added the rest of the people I want to compare. In this case, I’ve added my closest matches, even though they are from both sides of my tree.

Relationship Range

I’ve selected “Relationship range,” which will show me how my matches estimated relationships to each other.

Based on the identity of these matches, and how they match each other, I can now determine their ancestral connection.

If I didn’t know who was related maternally and paternally, this grid would remove all doubt became I’m comparing to one of my parents.

If you don’t have a parent, adding close, known relatives on one or both sides will help immensely.

Be sure to make notes about what you’ve discovered on your matches page, and paint to DNAPainter if that’s how you’re tracking your segments to ancestors.

Number of Segments Shared

Now, I’ve selected “Number of segments shared” to compare the same group of people.

You can see the number of shared segments between Mom’s matches. Donald and Cheryl are full siblings.

The display shows how these people match Mom, and each other.

Melissa is Mom’s paternal second cousin. I was able to piece this together with the help of how she matches Mom and Mom’s known paternal first cousins, Cheryl and Donald.

Total cMs Shared

Next, I’m selecting “Total cMs shared” for comparison.

Looking at the number of shared cMs, even if I didn’t know that Donald and Cheryl were full siblings, I would now.

You can also push these through to the chromosome browser. I’ll illustrate in a minute.

Bucketed or Parental Side Matching

My favorite groupings for the new Matrix are the bucketed, meaning parental or maternal “side” matching.”

When your matches are already bucketed, thanks to having linked known matches to their profile card in your tree, the system does a lot of the “side” work for you behind the scenes.

When you select “Maternal, “Paternal” or “Paternal and Maternal” matches, the people who have been bucket to either side, or those related to you on both sides, are listed in the selection box.

I’m selecting 7 of my maternal bucketed matches because I’m going to push them through to the chromosome browser for additional evaluation. I’m not including my mother because I already know these people are related to both me and her, because they are bucketed maternally.

They’re compared in the various matrix configurations.

From the Shared cM comparison table, I can easily click to display matches in the chromosome browser.

If you’re comparing more than 7 people, you’ll need to reduce it to 7. I excluded my Mom because I already know she matches all of them.

Click on the Compare Chromosome Browser at the bottom for the 7 people selected.

I know that cousin Charles descends from Mom’s paternal Lentz line, and has no other connection, so I know that these other cousins who also match me on that same segment are also from Mom’s Lentz line.

I can also tell that the shared segments on chromosome 1 are from Mom’s maternal Lore line.

Shown here are the common ancestors in Mom’s pedigree chart. They are 4 and 5 generations back in time for me.

Look how easy that was!

I love this new Matrix tool.

Triangulation

Because three or more people, including me, match on the same segments, this means they also triangulate.

In the example above, we have two distinct triangulation groups. I’m only showing chromosomes 1-3 for illustration purposes, but there are also more triangulation groups on the other chromosomes. If I add other people, new triangulation groups will form!

Of course, these are my maternal bucketed matches, so I’m safe to reach that conclusion. If my father’s matches were also loaded here, I would have to check the matrix and see if these people also matched each other before I could determine that they triangulate.

Check Your Matches and Upload

Be sure to upload any tests to FamilyTreeDNA that you manage at other vendors, and encourage your cousins to upload too.

This combination of features is unique to FamilyTreeDNA. The more relatives you have available to match, especially when you already know the common ancestor, the better. Be sure to link your matches to their placard in your tree so that FamilyTreeDNA can do the bucketing for you.

Even if you don’t link people, you can still benefit greatly from the new matrix tool by just having your DNA available for matching. The matrix will help you sort out matches and identify who is related to whom, and how.

Take a look! What are you discovering?

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Six Ways to Figure Out How We’re Related

In my latest Webinar, Six Ways to Figure Out How We’re Related, I discuss the various tools from Ancestry, FamilyTreeDNA, MyHeritage, and 23andMe – plus clusters from Genetic Affairs and the amazing DNAPainter.

This webinar lives in the Legacy Family Tree Webinar library, but as part of the “webtember” lineup, you can view it for free through the end of September.

It’s always exciting to discover a new match at one of the DNA testing companies, which, of course, begs the question of how you’re related.

So, what are the six ways to figure out how you’re related, and how do you use them?

Come along for a step-by-step guide!

Shared Matches

We begin with how each vendor handles shared matches, what that feature is called, where to find the information, and how to interpret what they are telling you.

23andMe goes a step further and creates a genetic tree, of sorts, although that functionality has changed since their breach last October.

Bucketing and Sides

Two vendors go a step further and provide unique tools to divide your matches maternally and paternally.

FamilyTreeDNA buckets your matches maternally and paternally (or both) based on matches you link to their profile cards in your tree. FamilyTreeDNA then uses your linked matches to triangulate with other matches and assign your matches accordingly, providing a maternal and paternal match list. Bucketing, also known as Family Matching, is one of my favorite tools.

Note that linking matches at FamilyTreeDNA requires that you have transferred your tree to MyHeritage. I wrote about that and provided instructions here and here, and produced a complimentary webinar, too.

Ancestry also divides your matches by parent, but they use a different technique based on their Sideview technology and either ethnicity or shared matches.

Surnames and Locations

Surnames and locations, either separately or together, provide HUGE hints!

MyHeritage provides a nice summary for each of your matches that includes ancestral surnames, a map of locations in common, and “Smart Matches” which shows you people in common in both of your trees. There are several ways to use these tools.

FamilyTreeDNA also provides a list of surnames. You can view either the surnames in common with a match, or all of their ancestral surnames, with locations if provided. The tester enters these surnames, and we review how to complete that step.

Ancestry also provides shared surnames, with clickable links to the number of people in your matches tree with that surname, plus common locations.

X-DNA

X-DNA is probably the most underutilized DNA matching tool. While each of the vendors actually test the X chromosome, only one, FamilyTreeDNA, provides X-matching. You can obtain X-matching results by uploading your DNA file to FamilyTreeDNA. I’ve provided upload/download instructions for all companies, here.

X-DNA has a very unique inheritance pattern because males only inherit an X chromosome from their mother which limits the number of potential common ancestors for any two testers. In other words, X-DNA matching does half your work for you!

Clustering Technology – AutoClusters, the Matrix and DNAPainter

In the past few years, match clustering has become a very useful tool. Clustering shows which of your matches match you and each other.

Genetic Affairs offers several flavors of these clusters, and both MyHeritage and GEDmatch have incorporated Genetic Affairs clusters into their product offerings.

If you haven’t used AutoClusters yet, by all means, try them out.

FamilyTreeDNA offers the Matrix, a slightly different version of clustering. You can select 10 people from your match list to see if they also match each other. Shared matches don’t automatically mean triangulation between you and those two people, or even that all three people descend from the same line. However, if the people are bucketed to your same side (parent) and they share common segments with you in the chromosome browser, they triangulate.

You’ll want to paint those matches to DNAPainter to determine which ancestor you share, especially if they haven’t provided a tree.

DNAPainter provides your chromosomes as the “canvas” upon which to paint your matches in order to correlate segments with ancestors and identify common ancestral lines with mystery matches.

Three vendors, FamilyTreeDNA, MyHeritage, and GEDmatch provide segment information with matches for you to paint. I illustrate how I walk segments back in time, identifying our most distant common ancestor possible.

Theories of Family Relativity and ThruLines

Both MyHeritage and Ancestry provide a combination of DNA matching and tree triangulation, where they search the trees of your DNA matches to find common ancestors with you – although their implementation is different.

MyHeritage’s Theories of Family Relativity provides varying theories about common ancestors for you and a specific match using both trees and historical documents. You can review the various pathways and confirm or reject theories. I love this tool.

Ancestry’s Thrulines functions a bit differently, showing you all of your matches that descend from a common ancestor in all your matches’ trees. Sometimes, the trees are incorrect, but Theories of Family Relativity and ThruLines should still be used as hints.

I showed how ThruLines helped me discover what happened to one of my ancestor’s grandchildren who was lost to the family at his mother’s death – and to all of us since. Not anymore.

Bonus – Y-DNA and Mitochondrial DNA at FamilyTreeDNA

Only FamilyTreeDNA offers both Y-DNA and Mitochondrial DNA testing and matching. All of the tools above pertain to autosomal DNA testing, which is named Family Finder at FamilyTreeDNA. Illustrated by the green arrow below, autosomal DNA testing measures and compares the DNA you inherited from each ancestral line, but that’s not the only game in town.

Y-DNA, in blue, for males, tracks the direct paternal line, which is the surname line in Western cultures. Mitochondrial DNA, in red, is passed from mothers to all of their children. Therefore, everyone can test, revealing matches and information about their mother’s direct matrilineal lineage.

Y-DNA testing includes the amazing Discover tool with a baker’s dozen different reports, including ancient DNA. Mitochondrial DNA will soon have its own MitoDiscover after the rollout of the new Mitotree.

Both tests include “Matches Maps” to help you determine how you are related to your matches, as well as where your ancestors came from before the advent of surnames.

The Advanced Matching feature allows you to select multiple tests to see if your matches match you on combined types of tests.

Tune In

Now that you know what we cover in the webinar, please tune in to see how to use these awesome tools. Be sure to fish in all four “ponds” plus GEDmatch, where you may find people who didn’t test at a company that provides a chromosome browser or matching segment information.

Tools provided by the DNA testing vendors facilitate multiple ways to determine how we match and which ancestor(s) we have in common.

You can watch the webinar, here.

Additionally, subscribers to Legacy Family Tree Webinars have access to the 25-page syllabus with even more information!

A Legacy Family Tree Webinar subscription normally costs $49.95 per year, but through the end of September, there’s a coupon code good for 20% off. Just click here, then enter webtember24 at the checkout.

Enjoy!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Great News – Both e-Pub and Print Version of “The Complete Guide to FamilyTreeDNA” Now Available Worldwide  

  • Anyone, anyplace, can order the full-color, searchable, e-pub version of The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA from the publisher, Genealogical.com, here.
  • Customers within the US can order the black and white print book from the publisher, here.
  • Customers outside the US can order the print book from their country’s Amazon website. The publisher does not ship print books outside the US due to customs, shipping costs, and associated delays. They arranged to have the book printed by an international printer so that it can be shipped directly to Amazon for order fulfillment without international customers incurring additional expenses and delays. If you ordered the book previously from Amazon and a long delivery time was projected, that should be resolved now and your book should be arriving soon.

Comprehensive

This book is truly comprehensive and includes:

  • 247 pages
  • More than 267 images
  • 288 footnotes
  • 12 charts
  • 68 tips
  • Plus, an 18-page glossary

To view the table of contents, click here. To order, click here.

Thank you, everyone, for your patience and your support.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Complete Guide to FamilyTreeDNA Released in Hardcopy

Just what many of you have been waiting for! The hardcopy print version of the Complete Guide to FamilyTreeDNA has just been released.

As shown in the table of contents below, The Complete Guide to FamilyTreeDNA contains lots of logically organized information! It includes basic education about genetic genealogy and how it works, instructions on using the FamilyTreeDNA tests and tools, plus an extensive glossary.

Enjoy!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Announcing: The Complete Guide to FamilyTreeDNA; Y-DNA, Mitochondrial, Autosomal and X-DNA

I’m so very pleased to announce the publication of my new book, The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA.

For the first time, the publisher, Genealogical.com, is making the full-color, searchable e-book version available before the hardcopy print version, here. The e-book version can be read using your favorite e-book reader such as Kindle or iBooks.

Update: The hardcopy version was released at the end of May and is available from the publisher in the US and from Amazon internationally.

This book is about more than how to use the FamilyTreeDNA products and interpreting their genealogical meaning, it’s also a primer on the four different types of DNA used for genealogy and how they work:

  • Autosomal DNA
  • Mitochondrial DNA
  • Y-DNA
  • X-DNA

There’s a LOT here, as shown by the table of contents, below

This book is chocked full of great information in one place. As an added bonus, the DNA glossary is 18 pages long.

I really hope you enjoy my new book, in whatever format you prefer.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Comparing DNA Results – Different Tests at the Same Testing Company

Several people have asked about different tests at the same DNA testing company. They wondered if matching is affected, meaning whether your matches are different if you have two different tests at the same company. Specifically, they asked if you are better off purchasing a test AT a DNA testing vendor that allows uploads, rather than uploading a test from a different vendor. Does it make a difference to the tester or their matches? Do they have the same matches?

These are great questions, and the answer isn’t conclusive. It varies based on several factors.

Having multiple tests at the same DNA testing company can occur in three ways:

  • The same person tests twice at the same DNA testing company.
  • The same person tests once at the DNA testing company and uploads a test from a different testing company. Only two of the primary four DNA testing companies accept uploads from other vendors – FamilyTreeDNA and MyHeritage.
  • The same person uploads two different files from other DNA testing companies to the DNA testing company in question. For example, the DNA company could be FamilyTreeDNA and the two uploaded DNA files could be from either MyHeritage, 23andMe or Ancestry.

All DNA testing companies allow users to download their raw DNA data files. This enables the tester to upload their DNA file to the vendors who accept uploaded files. Both FamilyTreeDNA and MyHeritage provide matching for free, but advanced tools require a small unlock fee of $19 and $29, respectively.

Testing Company Accepts Uploads from Other Companies Download Upload Instructions
23andMe No Instructions here
Ancestry No Instructions here
FamilyTreeDNA Yes, some Instructions here
MyHeritage Yes, some Instructions here

I wrote about developing a DNA testing and transfer/upload strategy, here, and about which companies accept which tests, here.

Not all DNA files are created equal. Therefore, not all files from vendors are compatible with other vendors for various reasons.

Multiple Tests at the Same DNA Testing Company

I have at least two tests at each of the four major vendors. I did this for research purposes, meaning to write articles to share with you.

If you actually test twice at a vendor, meaning purchase two separate tests and take them yourself, you will have two test results at that testing company. At some companies, specifically 23andMe, if you purchase a new test through their “upgrade” procedure, you won’t have two tests, just the newer one.

However, if you’re testing at the DNA testing company, and also uploading, I generally don’t recommend more than one test at each vendor. All it really does is clog up people’s match lists with no or little additional benefit. At 23andMe, with their restrictions on the size of your match list, if everyone had two tests, the effective match limit would be half of their stated limit of about 1500 matches for earlier testers and about 5000 for current testers with subscriptions.

So, in essence, I’m telling you to “do as I say, not as I do.” We all have better things to do with our money rather pay for the same test twice. If you haven’t tested your Y-DNA or mitochondrial DNA, that’s much more beneficial than two autosomal tests at one vendor.

Chips and Chip Evolution

Before we begin the side-by-side comparison, let’s briefly discuss DNA testing chips and how they work.

Each DNA testing company purchases DNA processing equipment. Illumina is the big dog in this arena. Illumina defines the capacity and structure of each chip. In part, how the testing companies use that capacity, or space on each chip, is up to each company. This means that the different testing companies test many of the same autosomal DNA SNP locations, but not all of the same locations.

Furthermore, the individual testing companies can specify a number of “other” locations to be included on their chip, up to the chip maximum size limit. The testing companies who offer Y-DNA or mitochondrial DNA haplogroups from autosomal tests use part of their chip array space for selected known haplogroup-defining SNP locations. This does NOT mean that Y-DNA or mitochondrial DNA is autosomal, just that the testing company used part of their chip array space to target these SNPs in your genome. Of course, for your most refined haplogroup and Y-DNA or mitochondrial DNA matching, you have to take those specific tests at FamilyTreeDNA .

This means that each testing company includes and reports many of the same, but also some different SNP locations when they scan your DNA.

In the lab, after your DNA is extracted from either your saliva or the cheek swab, it’s placed on this array chip which is then placed in the processing equipment.

There are several steps in processing your DNA. Each DNA location specified on the chip is scanned and read multiple times, and the results are recorded. The final output is the raw DNA results file that you see if/when you download your raw DNA file.

Here’s an example from my file. The RSID is the reference SNP cluster ID which is the naming convention used for specific SNPs. It’s not relevant to you, but it is to the lab, along with the chromosome number and position, which is in essence the address on the chromosome.

In the Result column, your file reports one nucleotide (T, A, C or G) that you inherited from each parent at each tested position. They are not listed in “parent order” because your DNA is not organized in that fashion. There’s no way for the lab to know which nucleotide came from which parent, unless they are the same, of course. You can read about nucleotides, here.

When you upload your raw DNA file to a different DNA testing company (vendor), they have to work with a file that isn’t entirely compatible with the files they generate, or the other files uploaded from other DNA testing companies.

In addition to dealing with different file formats and contents from multiple DNA vendors, companies change their own chips and file structure from time to time. In some cases, it’s a forced change by the chip manufacturer. Other times, the vendors want to include different locations or make improvements. For example, with 23andMe’s focus on health, they probably add new medically related SNP locations regularly. Regardless of why, some DNA files include locations not included in other files and are not 100% compatible.

Looking at the first few entries in my example file above, let’s say that the testing vendor included the first ten positions, but an uploaded file from another company did not. Or perhaps the chip changed, and a different version of the company’s own file contains different positions.

DNA testing companies have to “fill in the blanks” for compatibility, and they do this using a technique called imputation. Illumina forced their customers to adopt imputation in 2017 when they dropped the capacity of their chip. I was initially quite skeptical, but imputation has worked surprisingly well. Some of the matching differences you will see when comparing the results of two different DNA files is a result of imputation.

I wrote about imputation in an early article here. Please note the companies have fixed many issues with imputation and improved matching greatly, but the concepts and imputation processes still apply. The downloaded raw data files are your results BEFORE imputation, meaning that it’s up to any company where you upload to process your raw file in the same way they would process a file that they generated. A lot goes on behind the scenes when you upload a file to a DNA testing company.

At both 23andMe and Ancestry, you know that all of your matches tested there, meaning they did not upload a file from another testing company. You don’t know and can’t tell what chip was utilized when your matches tested. The only way to determine a chip testing version, aside from knowing the date or remembering the chip version from when you tested, is to look at the beginning of the raw data download file, although not all files contain that information.

Ok, now that you understand the landscape, let’s look at my results at each company.

23andMe

I tested twice at 23andMe on two different chip versions, V3 and V4, which tested some different locations of my DNA. Neither of these chips is the current version. I originally tested twice to evaluate the differences between the two test versions which you can read about, here.

23andMe named their ethnicity results Ancestry Composition.

They last updated my V3 test’s Ancestry Composition results on July 28, 2021.

The percentages are shown at left, and the country locations are highlighted at right for my 23andMe V3 test.

Click to enlarge any graphic

The 23andMe V4 test was also updated for the last time on July 28, 2021.

The ethnicity results differ substantially between the two chip versions, even though they were both updated on the same date.

In October of 2020, in an effort to “encourage” their customers to pay for a new test on their V5 chip, 23andMe announced that there would be no ethnicity updates on older tests. So, I really don’t know for sure when my tests were actually updated. Just note how different the results are. It’s also worth mentioning that 23andMe does not show trace amounts on their map, so even though my Indigenous American results were found, they aren’t displayed on the map.

Indigenous is, however, shown in yellow on their DNA Chromosome Painting.

No other testing company restricts updates, penalizing their customers who purchased earlier versions of tests.

Matches at 23andMe

23andMe limits your matches to about 1500 unless you have purchased the current test, including health AND pay for an annual $69 subscription which buys you about 5000 matches. I have not purchased this test.

Your number of actual matches displayed/retained is also affected by how many people you have communicated with, or at least initiated communications with. 23andMe does not roll those people off of your match list.

I have 1803 matches on both of my tests, meaning I’ve reached out to about 300 people who would have otherwise been removed from my match list. 23andMe retains your highest matches, deleting lower matches after you reach the maximum match threshold.

I’ve randomly evaluated several of the same matches at each vendor, at least five maternal and five paternal, separated by a blank row. I wanted to determine whether they match me on the same number of centimorgans, meaning the same amount of DNA, on both tests, and the same number of segments.

Match 23and Me V3 23and Me V4
Patricia 292 cM – 12 segments Same as V3
Joe 148 cM, 8 segments Same
Emily 73 cM, 4 segs 72 cM, 4 seg
Roland 27 cM, 1 seg Same
Ian 62 cM, 4 seg Same
Stacy 469 cM, 16 segments 482 cM, 16 segments
Harold 134 cM, 6 segments Same
Dean 69 cM, 3 seg Same
Carl 95 cM, 4 seg Same
Debbie 83 cM, 4 seg 84 cM, 4 seg

As you can see, the matches are either exact or xclose.

Please note that bolded matches are also found at another company. I will include a summary table at the end comparing the same match across multiple vendors.

23and Me Summary

The 23andMe V3 and V4 match results are very close. Since the match limit is the same, and the results are so close between tests, they are essentially identical in terms of matching.

The ethnicity results are similar, but the V4 test reflects a broader region. Italian baffles me in both versions.

Ethnicity should never be taken at face value at any DNA testing company, especially with smaller percentages which could be noise or a combination of other regions which just happens to resemble Italy, in my case.

I don’t know what type of comparison the current chip would yield since I suspect it has more medical and less genealogical SNPs on board.

Reprocessing Tests

This is probably a good place to note that it’s very expensive for any company to update their customer’s ethnicity results because every single customer’s DNA results file must be completely rerun. Note that this does not mean their DNA itself is retested. The output raw data file is reprocessed using a new algorithm.

Rerunning means reprocessing that specific portion of every test, meaning the vendors must rent “time in the cloud.” We are talking millions of dollars for each run. I don’t know how much it costs per test, but think about the expense if it takes $1 to rerun each test in the vendor’s database. Ancestry has more than 20 million tests.

While we, as consumers, are always chomping at the bit for new and better ethnicity results – the testing companies need to be sure it really is “better,” not just different before they invest the money to reprocess and update results.

This is probably why 23andMe decided to cease updating older kits. The newer tests require a subscription which is recurring revenue.

The same is true when DNA testing companies need to rematch their entire user base. This happens when the criteria for matching changes. For example, Ancestry purged a large number of matches for all of their customers back in 2020. While match algorithm changes necessitate rematching, with associated costs, this change also provided Ancestry with the huge benefit of eliminating approximately half of their customer’s matches. This freed up storage space, either physically in their data center or space rented in the cloud, representing substantial cost-savings.

How long can a DNA testing company reasonably be expected to continue investing in a product which never generates additional revenue but for which the maintenance and reinvestment costs never end?

Ancestry and MyHeritage both hope to offset the expenses of maintaining their customer’s DNA tests and providing free updates by selling subscriptions to their record services. 23andMe wants you to purchase a new test and a yearly subscription. FamilyTreeDNA wants you to purchase a Big Y-DNA and mitochondrial DNA test.

OK, now let’s look at my matches at Ancestry.

Ancestry

I’ve taken two Ancestry tests, V1 and V2. There were some differences, which I wrote about here and here. V2 is no longer the current chip.

Except for 23andMe who wants their customers to purchase their most current test, the other companies no longer routinely announce new chip versions. They just go about their business. The only way you know that a vendor actually changed something is when the other companies who accept uploads suddenly encounter an issue with file formats. It always takes a few weeks to sort that out.

My Ancestry V1 test’s ethnicity results don’t show my Native American ethnicity.

Ancestry results were updated in June 2022

However, my V2 results do include Native American ethnicity.

Matches at Ancestry

I have many more matches on my V1 test at Ancestry because I took steps to preserve my smaller matches when Ancestry initiated its massive purge in 2020. I wrote about that here and here.

Ancestry’s SideView breaks matches down into maternal, paternal, and unassigned based on your side selection. You tell Ancestry which side is which. You may be able to determine which “side” is maternal or paternal either by your ethnicity or shared matches. While SideView is not always accurate, it’s a good place to begin.

Match Category Ancestry V1 Test Ancestry V2 Test
Maternal 15,587 15,116
Paternal 42,247 41,870
Both 2 2
Unassigned 48,999 4,127
Total 106,835 61,115

Ancestry either displays all your matches or your matches by side, which I used to compile the table above. I suspect that Ancestry is not assigning any of the smaller preserved matches to “sides” based on the numbers above.

Ancestry implemented a process called Timber that removes DNA that they feel is “too matchy,” meaning you match enough people in this region that they think it’s a pileup region for you personally, and therefore not useful. In some cases, enough DNA is removed causing that person to no longer be considered a match because they fall beneath the match threshold. I am not a fan of Timber.

Your match amount shown is AFTER Timber has removed those segments. Unweighted shared DNA is your pre-Timber match amount.

You can view the Unweighted shared DNA by clicking on the amount of shared DNA on your match list.

You can read Ancestry’s Matching White Paper, here.

Let’s take a look at my matches. I’ve listed both weighted and unweighted where they are different.

Match Ancestry V1 Ancestry V2
Michael 755 cM, 35 seg 737 cM, 33 seg
Edward 66 cM, 4 seg (unweighted 86 cM) 65 cM, 4 seg (unweighted 86 cM)
Tom 59 cM, 3 seg (unweighted 63) Same
Jonathon 43 cM, 4 seg, (unweighted 52 cM) Same
Matthew 20 cM, 2 seg (unweighted 35 cM) Same
Harold 132 cM, 7 seg 135 cM, 6 seg
Dean 67 cM, 4 seg (unweighted 78 cM) 66 cM, 4 seg (unweighted 78 cM)
Debbie 93 cM, 5 seg Same
Valli 142 cM, 3 seg Same
Jared 20 cM, 1 seg (unweighted 22 cM) Same

Timber only removes DNA when the match is under 90 cM. Almost every match under 90 cM has some DNA removed.

Ancestry Summary

The results of the two Ancestry tests are very close.

In some circumstances, no DNA is removed by Timber, so the unweighted is the same as the weighted. However, in other cases, a significant amount is removed. 15 cM of Matthew’s 35 cM was removed by Timber, reducing his total to 20 cM.

Remember that Ancestry does not show shared matches unless they are greater than 20 cM, which is different than any other DNA testing company.

At one point, Ancestry was selling a health test that was also a genealogy test. That test utilized a different chip that is not accepted for uploads by other vendors. The results of that test might well be different that the “normal” Ancestry tests focused on genealogy. The Ancestry health test is no longer offered.

Companies that Accept Uploads

DNA testing companies that accept uploaded DNA files from other DNA testing companies need to process the uploaded file, just like a file that is generated in their own lab. Of course, they must deal with the differences between uploaded files and their own file format. The processing includes imputation and formulates the uploaded file so that it works with the tools that they provide for their customers, including ethnicity (by whatever name they use) matching, family matching (bucketing), advanced matching, the match matrix, triangulation, AutoClusters, Theories of Family Relativity, and other advanced tools.

Of course, the testing company accepting uploads can only work with the DNA locations provided by the original DNA testing company in the uploaded file.

Matching and some additional tools are free to uploaders, but advanced tools require an inexpensive unlock.

FamilyTreeDNA

I took a test at FamilyTreeDNA, plus uploaded a copy of both of my Ancestry DNA files.

FamilyTreeDNA named their population (ethnicity) test myOrigins and the current version is V3. I wrote about the rollout and comparison in September of 2020, here.

My DNA test taken at FamilyTreeDNA, above, reveals Native American segments that match reference populations found both in North and South America and the Caribbean Islands.

At FamilyTreeDNA, my Ancestry V1 uploaded file results show Native American population matches only in North America.

Interestingly, my Ancestry V1 file processed AT Ancestry did not reveal Native American ancestry, but the same file uploaded to and processed at FamilyTreeDNA did show Native American results, reflecting the difference between the vendors’ internal algorithms and reference populations utilized.

My myOrigins results from my Ancestry V2 uploaded file at FamilyTreeDNA also include my North American Native American segments. The V2 test also showed Native American ethnicity at Ancestry, so clearly something changed in Ancestry’s algorithm, locations tested, and/or reference populations between V1 and V2.

Fortunately, FamilyTreeDNA provides both chromosome painting and a population download file so I can match those Native segments with my autosomal matches to identify which of my ancestors contributed those specific segments.

One of my Native segments is shown in pink on Chromosome1. My mother has a Native segment in exactly the same location, so I know that this segment originated with my mother’s ancestors.

I downloaded the myOrigins population segment file and painted my results at DNAPainter, along with the matches where I can identify our common ancestor. This allowed me to pinpoint the ancestral line that contributed this Native segment in my maternal line. You can read about using DNAPainter, here.

FamilyTreeDNA Matches

I have significantly more matches at FamilyTreeDNA on their test than on either of my Ancestry tests that I uploaded. However, nearly the same number are maternally or paternally assigned through Family Matching, with the remainder unassigned. You can read about Family Matching here.

Match Category FamilyTreeDNA Test Ancestry V1 at FamilyTreeDNA Ancestry V2 at FamilyTreeDNA
Paternal 3,479 3,572 3,422
Maternal 1,549 1,536 1,477
Both 3 3 3
All 8,154 6,397 6,579

Family matching, aka bucketing, automatically assigns my matches as maternal and paternal by linking known relatives to their place in my tree.

I completed the following match chart using my original test taken at FamilyTreeDNA, plus the same match at FamilyTreeDNA for both of my Ancestry tests.

In other words, Cheryl matched me at 467 cM on 21 segments on the original test taken at FamilyTreeDNA. She matched me on 473 cM and 21 segments on my Ancestry V1 test uploaded to FamilyTreeDNA and on 483 cM and 22 segments on the Ancestry V2 test uploaded to FamilyTreeDNA.

Match FamilyTreeDNA Ancestry V1 at FTDNA Ancestry V2 at FTDNA
Cheryl 467 cM, 21 seg 473 cM, 21 seg 483 cM, 22 seg
Patricia 195 cM, 11 seg 189 cM, 11 seg 188 cM, 11 seg
Tom 77 cM, 4 seg 71 cM, 4 seg 76 cM, 4 seg
Thomas 72 cM, 3 seg 71 cM, 3 seg 74 cM, 3 seg
Roland 29 cM, 1 seg 35 cM, 2 seg 35 cM, 2 seg
Rex 62 cM, 4 seg 55 cM, 3 seg 57 cM, 3 seg
Don 395 cM, 18 seg 362 cM, 15 seg 398 cM, 18 seg
Ian 64 cM, 4 seg 56 cM, 4 seg 64 cM, 4 seg
Stacy 490 cM, 18 seg 494 cM, 15 seg 489 cM, 14 seg
Harold 127 cM, 5 cM 133 cM, 6 seg 143 cM, 6 seg
Dean 81 cM, 4 seg 75 cM, 3 seg 83 cM, 4 seg
Carl 103 cM, 4 seg 101 cM, 4 seg 102 cM, 4 seg
Debbie 99 cM, 5 seg 97 cM, 5 seg 99 cM, 5 seg
David 373 cM, 16 seg 435 cM, 19 seg 417 cM, 18 seg
Amos 176 cM, 7 seg 177 cM. 8 seg 177 cM, 7 seg
Buster 387 cM, 15 seg 396 cM, 16 seg 402 cM, 17 seg
Charlene 461 cM, 21 seg 450 cM, 21 seg 448 cM, 20 seg
Carol 65 cM, 6 seg 64 cM, 6 seg 65 cM, 6 seg

I have tested many of my cousins at FamilyTreeDNA and encouraged others to test or upload. I’ve attempted to include enough people so that I can have common matches at least at one other DNA testing company for comparison.

FamilyTreeDNA Summary

The matches are relatively close, with a few being exact.

Interestingly, some of the segment counts are different. In most cases, this results from one segment being broken into multiple segments by one or more of the tests, but not always. In the couple that I checked, the entire segment seems to descend from the same ancestral couple, so the break is likely a result of not all of the same DNA locations being tested, plus the limits of imputation.

MyHeritage

I have two tests at MyHeritage. One taken at MyHeritage, and an uploaded file from FamilyTreeDNA.

MyHeritage displays both ethnicity results and Genetic Groups which maps groups of people that you match. I left the Genetic Groups setting at the highest confidence level. Shifting it to lower displays additional Genetic Groups, some of which overlap with or are within ethnicity regions.

My test taken at MyHeritage, above, shows several ethnicities and Genetic Groups, but no Native American.

My FamilyTreeDNA kit processed at MyHeritage shows the same ethnicity regions, one additional Genetic Group, plus Native American heritage in the Amazon which is rather surprising given that I don’t show Native in North American regions where I’m positive my Native ancestors lived.

MyHeritage Matching

At MyHeritage, I compared the results of the test I took with MyHeritage, and a test I uploaded from FamilyTreeDNA. Fewer than half of my matches can be assigned to a parent via shared matching.

Matches MyHeritage Test FamilyTreeDNA at MyHeritage
Paternal 4,422 6,501
Maternal 2,660 3,655
Total 13,233 16,147

I have rounded my matches at MyHeritage to the closest cM.

Match MyHeritage Test FamilyTreeDNA at MyHeritage
Michael 801 cM, 32 seg 823 cM, 31 segments
Cheryl 467 cM, 23 seg 477 cM, 23 seg
Roland No match 28 cM, 1 seg
Patty 156 cM, 9 seg 151 cM, 9 seg
Rex 43 cM, 4 seg 53 cM, 3 seg
Don 369 cM, 16 seg 382 cM, 17 seg
 
David 449 cM, 17 seg 460 cM, 17 seg
Charlene 454 cM, 23 seg 477 cM, 24 seg
Buster 408 cM, 15 seg 410 cM, 16 seg
Amos 183 cM, 8 seg Same
Carol 78 cM, 6 seg 87 cM, 7 seg

MyHeritage Summary

I was surprised to discover that Roland had no match with the MyHeritage test, but did with the FamilyTreeDNA test. I wonder if this is a searching or matching glitch, especially since both companies use the same chip. 28 cM in one segment is a reasonably large match, and even if it was divided in two, it would still be over the matching threshold. I know this is a valid match because Roland triangulates with me and several cousins, I’m positive of our common ancestor, and he also matches me at both FamilyTreeDNA and 23andMe.

Other than that, the matches are reasonably close, with one being exact.

Your Matches Aren’t Everyplace

I unsuccessfully searched for someone who was a match to me in all four databases. Ancestry does not permit match downloads, so I had to search manually. People don’t always use the same names in different databases.

Surprisingly, I was unable to find one match who is in all of the databases. Many people only suggest testing at Ancestry because they have the largest database, but if you look at the following comparison chart that I’ve created, you’ll see that 16 of 26 people, or 62% were not at Ancestry. Conversely, many people were at Ancestry and not elsewhere. I could not find five maternal and five paternal matches at Ancestry that I could identify as matches in another database. 40% were not elsewhere.

If you think for one minute that it doesn’t matter for genealogy if you’re in all four major databases, please reconsider. It surely does matter.

Every single vendor has matches that the others don’t. Substantial, important matches. I have found first and second-cousin matches in every database that weren’t elsewhere.

Many of the original testers have passed away and can’t test again. My mother can never test at either 23andMe or Ancestry, but she is at both FamilyTreeDNA and MyHeritage because I could upgrade her kit at FamilyTreeDNA after she died. I uploaded her to MyHeritage. Of course, because she is a generation closer to our ancestors, she has many valuable matches that I don’t.

Each vendor provides either an email address or a messaging platform for you to contact your matches. Don’t be discouraged if they don’t answer. Just today, I received a reply that was years in the making.

Genealogists hope for immediate gratification, but we are actually in this for the long game. Play it with every tool at your disposal.

The Answer

Does it matter if you test at a DNA testing company, or upload a file?

I know this was a very long answer to what my readers hoped was a simple yes or no question.

There is no consistent answer at either FamilyTreeDNA or MyHeritage, the two DNA testing companies that accept uploads. Be sure you’re in both databases. My closest two matches that I did not test were found at MyHeritage. Here’s a direct link to upload at MyHeritage.

Of the vendors, those two should be the closest to each other because they are both processed in the GenebyGene lab, but again, the actual chip version, when the test was originally taken, and each vendor’s internal processing will result in differences. Neither the original test at the DNA testing company nor the uploaded files have consistently higher or lower matches. Neither type of test or upload appears to be universally more or less accurate. Differences in either direction seem to occur on a match-by-match basis. Many are so close as to be virtually equivalent, with a few seemingly random exceptions. Of course, we always have to consider Timber.

If you upload, unlock the advanced features at both FamilyTreeDNA and MyHeritage.

If you upload to a DNA testing company, you may discover in the future that some features and functions will only be available to original testers.

Personally, if I had the option, I would test at the company directly simply because it eliminates or at least reduces the possibility of future incompatibilities – with the exception of 23andMe which has chosen to not provide consistent updates to older tests. I’m incredibly grateful I didn’t test my mother or now deceased family members at 23andMe, and only there. I would be heartsick, heartbroken, and furious.

Our DNA is an extremely valuable resource for our genealogy. It’s the gift that truly keeps on giving, day after day, even when other records don’t exist. Be sure you and your family members are in each database one way or another, and test your Y-DNA (for males) and mitochondrial DNA (for everyone) to have a complete arsenal at your disposal.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research