FOCUS: Step 4 – Why Segments Are Important Keys to Identifying Your Ancestor

In this article, we’ll cover the importance of segments, how to find yours at the various vendors that provide that information, and an amazing tool called DNAPainter to keep track of it all.

If you are new to the FOCUS series, which is focused on breaking down your genealogical brick walls, I suggest reading the earlier articles in order.

Why Are Segments Important?

Years ago, my mother and I used to have a discussion that went something like this:

Me: Look at that pretty orange shirt.

Mom: That’s not orange. It’s red.

Me, pointing across the room at someone else: No, that’s red over there.

And so the good-hearted banter went on for years. The fun part was that we could never tell who was “right.” What was really “red”?

How would we know the difference if we couldn’t compare them to each other, side by side, and maybe to colored paint chips too?

The answer is that we couldn’t. We were both “close” but when specifics and details mattered, we were flying blind based on our preconceived notions of red and orange, plus looking at both shirts from across a room.

In autosomal DNA, segments afford us the ability to compare actual pieces of DNA with our various matches to determine whether we share the same pieces, or segments, of DNA.

Segments are the arbiter of relatedness, both IF we are related, and HOW we are related. They allow us to compare our DNA with our matches’ DNA in order to assign ancestors to shared segments.

How Do Segments Work?

Let’s say that Buster is my second cousin (2C), which means that our shared ancestors are our great-grandparents, Lazarus Estes and Elizabeth Vannoy.

We both match another person, Joe, but we don’t know exactly how.

In this example, I match both Buster and Joe, and Joe and Buster match each other too.

  • I match Buster on segments 3, 4, and 5.
  • I match Joe on segments 1 and 2.
  • Buster matches Joe on segments 6 and 7.

So, we must all share a common ancestor, right?

Nope!

Not based on these DNA segments.

We might share a common ancestor, but not based on these matches.

Here’s the important part. Without being able to look at those segments, we would never know that we actually don’t all match each other on any of the same segments, because we all three match each other.

What does this mean?

Each pair shares DNA, but no segment is shared by all three of us. So if we share a common ancestor, it’s not evident in these three matches. This is exactly why viewing shared matches without being able to view segments can be very misleading.

Let’s look at segments.

We know that segments where Buster and I match had to have been inherited from our great-grandparents, Lazarus and Elizabeth. After working with other matches from known ancestors, I can determine that we both inherited orange segments 3 and 4 from Lazarus, and I inherited blue segments 5, 6 and 7 from Elizabeth. Buster, however, inherited only segment 5 from Elizabeth.

Buster inherited his purple segments 6 and 7 from another ancestor named John. Buster shares that ancestor with Joe, but not with me.

I, on the other hand, inherited my pink segments 1 and 2 from Sarah, and Joe inherited the same segments from Sarah too.

Buster inherited green segments 1 and 2 from a different ancestor. Neither segment matches Joe or me. Joe inherited grey segments 3, 4, and 5 that don’t match either me or Buster.

It’s happenstance that Buster and I both happen to match Joe.

The fact that the three of us happen to all match each other has nothing to do with any universally common segments that we share. It probably has to do with the fact that so many families lived in the hollers of eastern Tennessee together for generations.

However, if we couldn’t SEE those segments, it would be very easy to assume (danger word) otherwise.

Now, let’s look at a slightly different scenario.

Let’s say that Elizabeth’s father is Joel. Joe doesn’t descend from Lazarus and Elizabeth, but he descends from Joel through a different wife who is not Elizabeth’s mother. All three people share the same DNA on segment #8, so this segment triangulates. Triangulation occurs when each person matches both of the others on the same stretch of DNA.

We can tell that this segment descends from Joel, through Elizabeth to me and Buster, because Joe doesn’t descend from Lazarus and Elizabeth. Therefore, light blue segment #8 has to descend from Joel, not his two different wives.

Walking Segments Back in Time Identifies Earlier Ancestors

Identifying segments that descend from specific ancestors allows us to walk the segment back in time – and it’s also how we can identify brick-walled ancestors.

For each group of segments that you can assign to a particular ancestral couple, part of those segments will descend from their father, and part from their mother. Look for additional matches to work out which segments came from each member of the couple.

Let’s look at an example of how this works, and how we use it to connect the dots.

In this illustration, I carry segments from all eight of my great-grandparents, but without being able to assign them to ancestors, I don’t know who contributed what.

So let’s walk this back in time.

My father contributed the four segments on the left, and my mother contributed the four on the right. I know this based on who I match on those segments.

Each of their parents, my grandparents, contributed two segments, beginning with FF (father’s father) on the left and moving across to the right.

At the great-grandparent level, the eight colors now make sense, and I can attribute the segments to ancestors. However, I don’t know the identity of my mother’s father’s mother, Ezekiel’s wife, identified by the mustard-colored segment.

Ezekiel’s wife may be unknown, but people who match me on that segment will also share the lineage of my unknown mustard-colored great-grandmother. They may not match through her, but through her ancestors, who are also my ancestors except I don’t know who they are. Yet.

Some of your matches will know their ancestral lineage and who is in it – and they will match each other and you on a common segment.

Now it’s time to connect the dots.

It’s their genealogical information that you need. If Match 1 descends from Mary, and Match 2 descends from Lydia, then we need to figure out how Mary’s and Lydia’s trees connect to each other, then look at the trees of other people who triangulate with us on that segment.

There are really only three groups of people who match on this segment.

  1. Those we can determine descend from a known ancestor in my line based on the match’s tree.
  2. Those who don’t have trees.
  3. Those who don’t descend from a known ancestor on my known line, but have trees that connect to different ancestors, such as Mary and Lydia.

Eventually, using both genealogy and genetic matching, we’ll be able to connect the dots between our unknown ancestor, ?????, and Lydia. If my unknown great-grandmother is the daughter of Lydia, I will probably match people who match not only Lydia, but Lydia’s husband’s line too, presuming he was the father of ?????, especially if we match on multiple segments.

Identifying unknown ancestors is a large puzzle with no picture on the lid, and we’re assembling the pieces, working from all directions.

If your parents are living, use their results for this exercise since you only inherited half of each parent’s autosomal DNA.

If your parents aren’t available, your next best options are siblings, aunts, uncles, or cousins who descend from this same ancestor. Use their results in addition to your own. They will match people and segments that you don’t, which increases your chances of solving this puzzle.

Tracking Your Segments

Once you identify segments, you want a way to track them so you don’t have to do this over and over for the same segments. Plus, there are benefits to working with identified segments.

There are a couple of different ways to track segments as they are assigned to ancestors.

I used to track segments by forming triangulation groups in a massive spreadsheet, but I use a different methodology now.

Jim Bartlett, on his wonderful blog, Segmentology, steps his readers through how to do this successfully. Even if you don’t want to use the spreadsheet methodology, learning why this works is incredibly important.

You can see by looking at the right-hand side of his page that he’s been writing since April 2015. There’s so much to learn there, and I highly recommend his educational articles.

DNAPainter

DNAPainter Chromosome Map with Ancestor color legend

Instead of a massive spreadsheet that I maintain myself, I now use DNAPainter, a tool for you to:

  • Easily paint your segments on your chromosomes
  • Associate them with an ancestral couple

I’ve written about DNAPainter several times, but the article DNAPainter Instructions and Resources serves as a repository for all of the articles.

My goal in this article is not to teach you how to use DNAPainter, although it’s very easy, but to explain why you want to, and how to find the segments at each vendor to paint. DNAPainter also provides instructions about where to find segment data here, and how to assign segments to ancestors, here.

Why Do Ancestral Segments Matter?

Let’s say I’m searching for the unknown mother of Nancy Ann Moore. Her first name is Lucy, but I don’t know her birth surname or who her parents are.

At DNAPainter, from the bottom right menu on my chromosome map, I’ve selected the couple, John R. Estes and Nancy Ann Moore. This displays all of the matches I’ve already painted along with the segments attributed to those matches.

For privacy reasons, I’ve unselected “Show match names on segments” above. In the following image, the match name and anything else I entered would normally be displayed too.

These segments descend from the couple, John R. Estes and Nancy Ann Moore. Some of those segments will descend from John Estes’s ancestors, and some from Nancy Moore’s ancestors.

On Nancy’s side, some will have been inherited from her mother, Lucy, and some from her father, William Moore.

In a future article, we’ll work with our “best” matches for each brick-walled ancestral line. In this visual, it’s easy to see that the “best” matches are the longest segments because we have a greater chance of matching people on a longer segment than a shorter one. Furthermore, a longer segment is more likely to be identical by descent and not by chance.

If you paint your highest cM matches, meaning the closest relationships that you can identify at each of these vendors, you’ll already have a head start on our next article.

Segments At Each Vendor

Ancestry does not provide segment address information, so you can’t paint segments from Ancestry.

However, FamilyTreeDNA, MyHeritage, and GEDmatch do, and 23andMe used to. Some Ancestry and 23andMe users upload their DNA files to GEDmatch, so you may be able to find some Ancestry and 23andMe matches that you can identify among your highest matches on GEDmatch.

At FamilyTreeDNA

I’ve tested a lot of my family members at FamilyTreeDNA, so I know exactly which ancestors I share with my top matches.

Let’s start with my first match who is not a parent, sibling, or my descendant.

In my case, my closest match is Cheryl, my 1C1R on my Mom’s side.

You can see that Cheryl is a match on my maternal side. How do we know that? I linked Cheryl to her place in my tree on Mom’s side. This allows FamilyTreeDNA to triangulate behind the scenes and assign other people who match Cheryl and me on common segments to the same side of my tree.

Be sure to link everyone you can identify to their proper place in your tree, beginning with your highest matches. Of my 9075 matches, FamilyTreeDNA was able to identify 3759 as paternal and 1657 as maternal.

Next, click the box beside your match’s name, at far left.

This pops up a box where you can select “Compare Chromosome Browser.”

My chromosomes are displayed as the background, in grey, and the locations where Cheryl matches me are shown in blue.

You can download the segments being displayed into a file, but it’s actually easier to click on “Detailed Segment Data.”

You can simply copy this data, then go to your account at DNAPainter.

  1. Click on “Paint a New Match”
  2. Paste these segments into the box and save
  3. Proceed to associate this match with your common ancestral couple

Please note that in these examples, I’m only showing the first few chromosomes because it’s the process that matters.

At MyHeritage

At MyHeritage, for the match you want to view, click “Review DNA Match”.

Scroll down quite a way, past Shared Matches.

If the tester has authorized the comparison of their DNA with their matches, you’ll see a chromosome browser.

At right, click on the arrow beside “Advanced options” and then on “Download shared DNA info.”

A CSV file listing the segments you share with that person will be downloaded. Open the file and copy the contents of the rows and paste them into “Paint a New Match” at DNAPainter.

At 23andMe

Unfortunately, 23andMe removed the chromosome browser following their 2023 data breach. They eventually partially restored it, but only for subscribers. So, you may not have access to a chromosome browser at 23andMe.

If you saved a 2023 match download from before the October 2023 issues, it includes segment coordinates, and you can still use those.

Even if you do have access to the chromosome browser through a subscription, all 23andMe shows you is a picture with no associated segment information.

When you compare yourself with two or more matches, you can obtain the segment information for how they match each other, but not how you match either of them.

Yes, it’s insane that I can’t see how my match matches me. This information is not radioactive, especially since 23andMe is perfectly willing to show me the segment data for how two of my matches match each other.

Where this might come in handy as a partial workaround is if you have a sibling at 23andMe. This would provide you with how your sibling matches your match, but only on the same segments where they both match you. Incredibly frustrating, especially since you must subscribe to obtain even this much.

23andMe apparently does not wish to be a genealogy company when they grow up.

At GEDmatch

Fortunately, there’s a third-party tool where people from various testing companies can upload their raw data files and match.

You may be able to pick up some of your high-value testers from Ancestry and 23andMe at GEDmatch. You will need to correlate the name at GEDmatch with the test at Ancestry or 23andMe to be sure it’s the same person, and to view their tree at Ancestry.

Whether you have a subscription or free account at GEDmatch, select “One to Many” results. I’m demonstrating the free “One-to-Many Original” version, but it doesn’t matter because you’ll be able to see where the person tested with each version. Please note that X-DNA matching requires running that tool separately. If you match on the X-chromosome, you’ll want to paste that too.

What will matter to you is that the “One-to-Many Limited” version includes a column for a GEDCOM file or WikiTree link. Both display the testing company.

You can see where your matches tested. At one point, GEDmatch migrated from one platform to another internally, and the letter at the end of the “Migration” indicates the company, while the middle letter+number means the (now-irrelevant) test version.

Tests uploaded since the migration simply have the testing company name.

Select the match you want to view and copy their kit number from the far-left column.

Return to the menu and select “One-to-One Autosomal Comparison.”

Enter your kit number and the kit number of the match you want to compare with. Then, at the bottom left, select “Position only” so that the chromosome images won’t display between the rows of segment data.

Then click “Compare.”

Now, just copy the data in this entire table, go to DNAPainter, click “Paint a Match,” and paste the data into the box. You’ll be able to add the name of the tester.

Do you have to use DNAPainter?

No, of course not, but there are simply too many matches across different companies to keep them organized without a tool.

Here’s the benefit and where this is going.

How Segment Tracking Breaks Through Brick Walls

Let’s say that someone is a match on your mother’s side.

When you copy and paste the segments into DNAPainter, it shows which groups you’ve already painted and identified by ancestor that contain segments overlapping your new match.

Notice that you need to tell DNAPainter whether this match is maternal or paternal, because this segment location is found on both your maternal and paternal chromosomes. It points to one group of ancestors on the paternal side and another on the maternal side.

The people who carry this segment of maternal DNA are the exact people whose trees you want to view. Even if you can’t determine initially how you’re related to them, and through which ancestral line – your DNA and matches with people whose ancestors you can identify are doing the heavy lifting for you.

The ancestors you know, through their segments, lead to the brick-walled ancestors you’d like to know!

Based on these matches and the known genealogy of these ancestors, my cousin Roland is a descendant of Jacob Lentz and Fredericka Reuhl. Eva Miller, my great-grandmother, is Fredericka Reuhl’s granddaughter, so that one 26 cM segment that Roland and I share descended to both of us from either or both Jacob Lentz and Fredericka Reuhl. This was confirmed by Roland’s genealogy. The beauty of this is that now we know that the next person who matches us on that segment either descends from Jacob Lentz and Fredericka Reuhl, or one of their ancestors upstream.

One day, someone who does not descend through this couple, but from another Lentz or Reuhl ancestor will test and match, which will reveal who this segment belongs to.

If we’re searching for the ancestor of Jacob or Fredericka as our brick wall, matches on this segment plus their associated genealogy will provide hints about the identity of that unknown ancestor too.

The segments of DNA gifted to you by your ancestors are literally the keys to the kingdom, unlocking the door through that brick wall.

_____________________________________________________________

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 2 – Finding the Y-DNA and Mitochondrial DNA of Your Ancestors

This is the third article in our FOCUS series, providing step-by-step instructions for identifying brick-walled ancestors.

These two articles detail the initial steps:

By now, you will have selected the ancestor you want to focus on identifying, and you have tools in your toolkit for working with DNA matches who have no trees.

You may have ordered DNA tests from multiple vendors and are waiting on results, so while you wait, we’ll start with finding the Y-DNA and mitochondrial DNA of your ancestors and identifying DNA testing candidates.

While it may sound counterintuitive, we’re going to be working with all of the major vendors, including FamilyTreeDNA, who actually tests for Y-DNA and mitochondrial DNA, plus WikiTree, 23andMe, MyHeritage, Ancestry, GEDmatch and FamilySearch. They are all quite useful in different ways.

This Type of Searching Is Different

Normally, when we search for brick-walled ancestors, we are searching backward in time. In other words, we begin with the last person we know and work back from there, hoping to identify the previous generation.

If we don’t know Lucy’s birth surname and she was born about 1750, and married William Moore in the late 1770s, we begin with what we do know in that timeframe.

Searching for our ancestor’s Y-DNA or mitochondrial DNA, and testers who carry that DNA, is fundamentally different because we begin with that ancestor and work forward in time.

In other words, if we want to find Lucy’s mitochondrial DNA, we begin with her daughters and track forward in time to the present. Hopefully, someone has already tested, and we can locate that result, but if not, we need to find people who descend through a specific path that carry Lucy’s mitochondrial DNA.

If we were searching for the Y-DNA of William Moore, we would look for his direct paternal descendant males who would carry the Moore surname.

Chicken or Egg?

I’ve been debating whether I should show you:

  1. How to locate and identify the Y-DNA and mitochondrial DNA of your ancestors first, or
  2. How to use Y-DNA and mitochondrial DNA (mtDNA) to help break through your brick wall first

I decided to write the “how to locate” article first because I don’t want you to skim over and ignore the ‘how to use’ article, thinking it’s irrelevant to your research because you don’t carry the Y-DNA and/or mtDNA of your brick-walled ancestor.

There are lots of avenues to locate the Y-DNA or mitochondrial DNA of your ancestors, something you definitely want to do. You’ll soon see that Y-DNA and mtDNA information can also assist with autosomal DNA results.

These are all pieces of your ancestor’s puzzle, and you never know which one will be the one to topple that wall.

Plus, you don’t know what you don’t know about that ancestor.

Let’s jump right in!

Who Carries the Y-DNA and Mitochondrial DNA of Your Ancestor?

As a quick refresher, only men can test for Y-DNA because only men have a Y chromosome which is inherited from their father. It’s passed in a direct paternal line from father to son, never mixed with DNA from the mother. Because it’s never divided during recombination like autosomal DNA, it’s uniquely useful for connecting lineages both recently and back in time hundreds and thousands of years.

Both Y-DNA and mitochondrial DNA incur occasional mutations that function as genetic breadcrumbs, making them incredibly useful for reassembling those specific family lines where genealogy paper trails have broken or been interrupted.

Mitochondrial DNA is passed from mothers to their children of both sexes, but only daughters pass it on. This means that in the current generation, males and females can both test for the mtDNA of their direct, mother-to-mother, matrilineal line.

Anyone, including males, who descends from an ancestor through all females can test for that ancestor’s mitochondrial DNA.

If you’re lucky, you’ll carry the Y-DNA or mitochondrial DNA of the ancestor you are seeking. If not, you’ll need to do one of two things:

  1. Determine if someone has already tested for that ancestor
  2. If not, find candidates to test

Y-DNA is generally easier because you at least (hopefully) have a surname to work with that has been passed from father to son, along with their Y chromosome.

Mitochondrial DNA is more challenging since surnames change each generation, so I’ve included several mitochondrial examples. Don’t skip over them, because the same research techniques apply to Y-DNA too, especially difficult cases.

If you’re a male, I strongly recommend that you order:

If you’re a female, you can only order the mtFull test, but you may be able to ask your father or brother or a male relative (with the surname in the lineage you seek) to take the Big Y-700 to represent your father’s family line. In other words, if you’re looking for a male Estes, you can ask your 2C Estes male who descends in a direct paternal line of all Estes men from your common ancestor.

Complete Versus Partial Tests

Haplogroup-only results derived from autosomal tests are fine as far as they go – but they don’t go very far. Most are what I would call midrange, providing testers with a haplogroup from maybe 2000 years ago, and some are much more distant than that. That isn’t to say they can’t be useful in a limited capacity, but Y-DNA and mtDNA have so much more potential.

You need comprehensive Y-DNA and mtDNA test results that identify all your haplogroup-defining mutations and can be refined as more people test and match family-level mutations.

Haplogroups are important, but you also need to match with other testers. Additionally, you’ll want the most complete haplogroup possible, because it will help you genealogically by providing a complete breadcrumb trail with the ability to identify your most recent common ancestor (MRCA).

FamilyTreeDNA is the only vendor that offers these complete tests that include matching with other testers, plus additional genealogy tools.

The Big Y-700 test scans for mutations in the stable portion of the Y chromosome and is the only way to obtain that personal-level information. It’s those recent mutations that will help place you within a biological family – or eliminate you from other lines, which prevents barking up the wrong tree.

The benefit of taking the test yourself, or sponsoring a test for someone willing to share their results with you, is that you have ready access to information through FamilyTreeDNA’s tools such as:

  • Matches with other Y-DNA and mtDNA testers
  • Matches Map (ancestor locations)
  • Advanced Matching, which provides a filtered list of people who match you on BOTH your Y-DNA or mitochondrial DNA AND your Family Finder autosomal test
  • Haplotype clusters (for mtDNA)
  • Your mutations
  • Block Tree (for Y-DNA)
  • Customized Discover tools

Click any image to enlarge

  • Discover’s Advanced Tools like the Match Time Tree, shown above, which displays your matches with their earliest known ancestors (EKA) together on the Time Tree
  • Globetrekker™ (for Y-DNA with mtDNA coming soon)
  • Up to 30 Ancient Connections
  • Up to 20 Notable Connections

FamilyTreeDNA’s free Discover tool, here, provides public information for everyone about haplogroups, but if you haven’t taken the test, you won’t receive matching and customized information described above, which is essential to genealogy.

Upgrades for Partial Tests

You may have previously tested at a lower level at FamilyTreeDNA.

For mtDNA, the early mtPlus test examined a portion of the mitochondria and provided matching at lower levels, as do the 12-111 marker Y-DNA tests. Both provide a predicted high-level basic or midrange haplogroup based on the mutation information available in those limited tests.

If you took an earlier, partial test, you can sign on to your account to upgrade by clicking on the “Big Y,” even though it’s greyed out. Grey simply indicates that you don’t currently have that level of test.

Click on “Full” to upgrade to the mtFull test.

Test Features at Various Levels

Depending on the type of test you take, and at which vendor, you may have a fully refined or partial haplogroup.

Discover provides a substantial amount of information if you receive a partial haplogroup:

A partial haplogroup is better than no haplogroup, but it’s also like working with one hand tied behind your back. If at all possible, you need to work with a full haplogroup and matches.

Testers who click through to Discover from their own test, or a test they manage, can view additional features not available in the free version.

The table below shows the four different ways you can access and view your ancestor’s haplogroup. Based on the testing level and/or how they tested, the haplogroup level will vary.

Clearly, the best scenario is when you either take the Big Y-700 or mtFull test yourself, or you have access to the test results of someone who takes that test to represent your ancestor’s DNA. Primary access confers the greatest amount of information, but you can still glean information in other ways.

Feature Introductory Level Test at FamilyTreeDNA* Tester’s Big Y-700 or mtFull Test – Full Access Partial Haplogroup from Autosomal Test Your Ancestor’s Haplogroup but without Full Access
Matching Yes, at that lower level Best – at all levels No No
Matches Map Yes, at lower level Yes No No
Mutation Values Yes, STR markers at lower Y-DNA level Yes, STRs (Y-DNA) and SNPs Not directly but through Discover Not directly but through Discover
Haplotree & SNPs with surnames (Y-DNA only) Yes, at lower level Yes No No
Block Tree (Big Y test only) No Yes No No

 

Advanced Matching (multiple types of tests) Yes, at that level Yes No No
Ability to Join Group Projects Yes Yes Only test owner or manager can join Only test owner or manager can join
Discover Reports Yes, same information as the free version due to lower coverage Yes, when clicking through from your FamilyTreeDNA account Free version Free version
Haplogroup Story Yes, at lower haplogroup level Yes – best and highest level Yes, at lower haplogroup level Yes, at lower haplogroup level
Country Frequency Map and Table views Yes, at lower haplogroup level Yes, at most refined haplogroup level Yes, at lower haplogroup level Yes, at most refined haplogroup level
Notable Connections Same as free version About 20 for Y-DNA, 11 for mtDNA About 10 for Y-DNA, 3 for mtDNA About 10 for Y-DNA, 3 for mtDNA
Migration Map Yes, at lower level Yes, at advanced level Yes, at lower level Yes, at advanced level
Globetrekker (Y-DNA only, mtDNA coming soon) No Yes No No
Ancient Connections Same as free version About 30 About 10 for Y-DNA, 3 for mtDNA About 10 for Y-DNA, 3 for mtDNA
Time Tree Yes, at lower haplogroup level – generally 2,000 years or older Yes, at most refined haplogroup level, often within genealogical timeframe Yes, at lower haplogroup level – generally 2,000 years or older Yes, at most refined level
Match Time Tree No Yes – your matches & their EKA on the Time Tree including WikiTree Connections and Ancient DNA No No
Ancestral Path Yes, at lower haplogroup level Yes Yes, at lower haplogroup level Yes
Suggested Projects Yes Yes, at more refined level Yes, but must test with FamilyTreeDNA to join Yes, but must test with FamilyTreeDNA to join
Scientific Details, ages and variants Yes, at lower level Yes Yes, at lower level Yes
Compare Haplogroups Yes Yes Yes Yes

*Note that often your ancestor’s haplogroup as reported by the Family Finder (autosomal) test is more refined, meaning closer in time, than the Y-DNA haplogroups predicted by STR tests, but both are always substantially less specific than the Big Y-700 test. As of the publication date of this article, Family Finder does not yet report a mitochondrial DNA haplogroup, but that is planned for the future.

This chart only includes features you would specifically use to identify an ancestor or ancestral lineage. There are other reports provided with your test that will be of interest. Discover provides about 14 reports that include various options.

Now we can envision:

  • The benefits of finding our ancestors’ Y-DNA and mtDNA
  • The benefits of obtaining the most refined haplogroup possible
  • The benefits of being able to view the results directly

You may not be able to achieve all of these, but even a partial haplogroup is better than no haplogroup at all, and a fully refined haplogroup, even if you can’t see everything in another tester’s account, is better than a partial haplogroup.

So, let’s see how to find your ancestors’ haplogroups. I collect them all, not just for brick-walled ancestors, but because they tell a part of our story not available through any other means.

Finding Your Ancestor’s Mitochondrial and Y-DNA

If you are the DNA tester for your brick-wall ancestor, then you’re golden, but chances are that you’re not.

If you’re searching for Y-DNA, and you don’t carry that Y-DNA yourself, you’ll need a male relative who carries that Y chromosome to test.

Males carry the Y-DNA of their direct patrilineal ancestors, shown in the image below on the left side in blue, plus the mitochondrial DNA (mtDNA) of their mother, shown with yellow hearts at far right.

At the 4th generation level, we have 4 Y-DNA lineages to collect (light blue, dark green, medium green, and teal), and a total of 8 mtDNA lineages.

Let’s say you’re searching for your father’s mother’s mother as your brick-wall ancestor.

Your father (and his siblings) carry the mtDNA of his mother, shown above in fuchsia, as do her grandchildren through her daughters. That’s why your father has a fuchsia heart. If close family members test, chances are you can arrange to manage their test or view their results. (Be sure they take the autosomal Family Finder test too. You’ll need that later.

If you don’t manage their test for them, you’ll need to ask to see their results to view matches and work with trees.

I have a family project at FamilyTreeDNA that I manage. I ask people who have tested for a particular ancestor to join that project so I can easily view their results while they continue to manage their test, and can select how much they want me to see or do.

FamilyTreeDNA is currently working on a multi-kit management feature that will address the challenge of sharing results.

But I Don’t Know of Any Cousins…

Let’s say you don’t know of and can’t readily identify anyone who descends from your ancestor appropriately.

If the ancestor you seek is a male, mitochondrial DNA is probably not going to help you because men don’t pass their mitochondrial DNA on to their descendants. In order to obtain a male ancestor’s mitochondrial DNA, you’d need to be able to identify a sister or someone known to descend from his mother (or sisters) through all females to the current generation. Needless to say, if you know who his mother is, you probably already know who he is.

If your brick wall is a female ancestor, your first order of business is to find someone who descends from her through all females to the current generation, where the tester can be male or female.

Why is this so important?

Mitochondrial DNA isn’t admixed with the father’s DNA, so it’s not divided in each generation. This means that mitochondrial DNA is the only direct line-of-sight we have that bypasses both changing surnames and genetic recombination for females.

Who Has Tested for Your Ancestor?

If you’re NOT the tester for your brick-walled ancestor or aren’t the curator of the test, your first step is to see if someone else has already tested.

This can sometimes be challenging.

It’s impossible to obtain mitochondrial DNA for an unknown ancestor if there are no known daughters, and for Y-DNA if there are no known sons. You may need to review genealogical resources to make sure you’ve identified all of that ancestor’s children.

Barring those scenarios, there are a surprising number of resources available to find descendants.

WikiTree

The first place I check to see if someone has already tested for a particular ancestor is WikiTree.

WikiTree is the one place where you find the ancestor along with the people who have taken DNA tests who descend from that ancestor. It’s invaluable.

Normally, you have to work with matches to identify your common ancestor. WikiTree works the other way around. Your starting place is with the ancestor.

You can’t Google your mystery ancestor’s name because if you knew their name, they wouldn’t be a mystery ancestor – but you can Google their spouse or a child.

I’m using an example from my own line because my mitochondrial DNA results are connected to her.

I’m Googling:

Barbara Mehlheimer born 1822 died 1906 in Indiana at WikiTree

Google was slightly confused but the results got me to where I needed to go.

Barbara Mehlheimer married George Drechsel and her daughter was Barbara Drechsel who married Jacob Kirsch.

First, check Barbara’s WikiTree profile card to confirm you’ve found the correct person.

Next, click on the DNA tab beneath her profile information (or just scroll down). She has four DNA Connections.

You can see that one person, me, who carries Barbara’s mitochondrial DNA has connected their DNA to Barbara’s profile. I did this by entering my DNA information on my WikiTree profile, then WikiTree connects my DNA haplogroup information from mother to mother to mother to Barbara and propagates my DNA haplogroup to her, her matrilineal ancestors, and their female descendants. If you click on the haplogroup, it takes you directly to that haplogroup in Discover.

Three people have connected their autosomal results to Barbara. This information can be very important, and not just for mitochondrial DNA. It allows us to identify autosomal testers we may match at different testing companies who descend from Barbara.

In your research journal, make notes of these names, testing companies, and kit numbers. Remember that this doesn’t mean the company noted is the only place someone has taken an autosomal DNA test. I’ve tested at all of the major companies, but only GEDmatch and FamilyTreeDNA are listed here.

For Y-DNA and mitochondrial DNA, the haplogroup is shown, although when testers receive a new Y-DNA or Mitotree haplogroup, they seldom think to revise it in WikiTree. This means their current haplogroup may be more specific and improved since the WikiTree information was entered.

Some people may have tested at different levels too. In this case, Buster Estes, who is now deceased, was one of the earliest testers, long before the Big Y tests were available. He only took a 25-marker test, so his haplogroup was predicted as R-M269. Garmon, on the other hand, was able to upgrade his Y-DNA test to the Big Y-700, and his haplogroup is much more refined at R-ZS3700. Their haplogroups don’t match exactly due to the levels at which they tested, but they also don’t preclude the two testers from belonging to the same genetic line.

This screenshot of Discover’s Compare function illustrates how important the Big Y-700 test is when compared to the STR test’s predicted haplogroups. The man who developed the mutation that defines R-ZS3700 lived about 1750 CE, and the man who developed R-M269 lived about 4450 BCE, or 6,450 years ago. That’s a big difference.

Using a combination of multiple testers and genealogy, we’ve identified the man who developed R-ZS3700 and passed it on to his sons. Moses Estes was born in 1711 in Virginia and all of his descendant testers carry R-ZS3700.

Now that’s extremely useful information, because we know that any man with haplogroup R-ZS3700 descends from Moses Estes in a direct paternal line, and any man whose haplogroup is not R-ZS3700 or doesn’t include R-ZS3700 upstream of his haplogroup does not descend from Moses Estes in that way.

Please add your DNA tests, including haplogroups and your kit number, to your profile at WikiTree so that the haplogroup information can be populated appropriately to your ancestors.

Searching for a Test Candidate Using Autosomal Descendants

When you’re searching for a testing candidate at WikiTree, you can click through to the tester’s profile and view exactly how they descend from the ancestor shown.

Let’s say that no one has linked a mitochondrial DNA test to the ancestor you’re searching for, but several people have linked autosomal tests to that ancestor’s profile card.

Click on the tester’s name and then on the DNA Ancestors tab to see how they descend from that ancestor. If you’re lucky, you’ll find someone in the autosomal list who is a mitochondrial DNA testing candidate.

If you’re looking for a Y-DNA tester, begin by looking for a male with the same surname as that ancestor. If you’re looking for a mitochondrial DNA tester, you’ll need to view each tester’s ancestors.

Regardless of whether they are a mitochondrial or Y-DNA testing candidate, you’ll identify your most recent common ancestor (MRCA) for each person, information that will become essential for the autosomal tools that we’ll be discussing in future articles.

In your research journal, I suggest that you record all of their descent information now, including their names, where they tested, your MRCA, kit numbers and any other relevant notes.

If you’d like to ask them to take a specific test, or if they already have and you’d like to know more, you can message WikiTree users by clicking on their profile, and then on the little envelope beside the profile manager’s name.

Finding Your Ancestor’s DNA Descendants at WikiTree

Let’s say that no one in the DNA list of people who have already taken tests descends from your ancestor matrilineally. Don’t worry, there are still more options!

At the top of the WikiTree page for that ancestor, click the down arrow, then on DNA.

The default tab shows the DNA Ancestors of the profile you’re viewing. You’ll see Y-DNA for males, and both mitochondrial and X-chromosome ancestors for everyone.

You may notice that there’s an ancestor listed for your brick wall ancestor. That’s wonderful, but don’t jump for joy quite yet. Remember, WikiTree is a one-world tree, and you need to verify the underlying genealogy in every tree here, and at every vendor.

Always confirm using multiple sources, meaning resources other than trees. The great thing about WikiTree is that there are often several sources listed in each person’s profile, and other resources that can help immensely. I love WikiTree, but I’m always skeptical of information in any tree, and I prove everything to my own satisfaction. I wrote several articles about that topic in the Genealogy Proof Series, here.

To find testers, you’ll need to view your ancestor’s DNA Descendants.

Click on the DNA Descendants tab.

The Mitochondrial DNA Descendants view shows potential candidates for mtDNA testing. Remember, in the current generation, males and females can both test so long as they descend from that ancestor through all females.

In the case of Barbara Mehlheimer Drechsel and her descendants, there are several males who are immediately eliminated because they’ve been deceased for more than a century, and several daughters who didn’t have children.

Not every person’s line on WikiTree has been added or developed. You can see that three daughters’ lines that might hold candidates don’t list all their children, and I still need to research two additional people. That means I still have five candidate lines to extend that have potential mtDNA testers.

So, in summary, if Barbara was the ancestor I was seeking:

  • One person has already tested
  • Three daughters don’t have their families extended.
  • Two have daughters that I need to research.

For both Y-DNA and mitochondrial DNA, I like to have at least two people who descend from different children of the ancestor, and whose tests match at a level that does not preclude that lineage. This helps confirm both the genetic line and the genealogy of both testers.

With male ancestors, having more than one tester for each line through different siblings is essential.

Kit Numbers, Earliest Known Ancestors and Google

When DNA kit numbers are included at WikiTree, you’ll want to Google to see if that kit number is shown in a public Group Project at FamilyTreeDNA where you may find more information.

The exact search string to use to find a specific kit at FamilyTreeDNA within projects is:

“9993” site:familytreedna.com

Replace 9993 with the kit number you’re interested in. You can also add the word “projects”, without quotes, to the end of that string to omit forums and limit the search to within projects. This string both focuses and limits the search, filtering out most noise.

By clicking on “read more,” you’re taken directly to the Estes Family Surname Project Y-DNA page.

The green haplogroups are SNP-confirmed, unlike the red predicted haplogroups from the lower-level 12, 25, 37, 67 or 111-marker tests. The R-ZS3700 haplogroup was obtained from the Big Y-700 test, so it is the most granular and specific. If this is your line, you’ve just found your ancestor’s haplogroup. It’s also possible that, by testing, you could receive an even more specific haplogroup.

Please note that haplogroup R-M269 is the most common haplogroup in Europe, and isn’t specific enough to use for anything other than very basic information. It can rule out two people with different base haplogroups, like haplogroup I or J, for example, as descending from a common patrilineal ancestor.

Project administrators are all volunteers, and each administrator groups their Group Project members differently, so take a few minutes to review the project pages. You may find additional testers who have joined this project who descend from your ancestors or your ancestral line.

You may also find other lines with the same surname and a substantially different haplogroup, which tells you that there are multiple genetic lines with the same surname. I have one example of this in the same county, at the same time, found in men by the same exact name – think John Smith. So frustrating. Without DNA testing, we would NEVER have sorted through those two same-name but completely different lines.

However, finding people who match your ancestor’s DNA but don’t have your earliest known ancestor (EKA) may be just the clue you need to knock down that brick wall. How are your ancestor and that other person’s EKA connected, and in what timeframe? Do they share a surname? A location? Are there other clues?

It’s unlikely that you’ll be able to use a kit number to Google unless you find one at WikiTree, but you can still search using the oldest name in that line that you know.

nicholas ewstas site:familytreedna.com

Replace the kit number with your EKA, in this case, “Nicholas Ewstas” in the search string, either with or without quotes. This takes you to the same page and any other projects that someone may have joined using exactly that earliest known ancestor’s name. Keep in mind that you’re only looking at their oldest ancestor, not every ancestor between them and their EKA. Your brick wall may lie someplace in there, which is why you need to check matches and view their trees.

Since women’s surnames change in every generation, they generally won’t be found in specific ancestral surname projects like men. This makes Googling using the ancestor’s name even more important.

catherine lejeune site:familytreedna.com

We don’t know who Catherine LeJeune’s mother is, so finding that someone has entered Catherine as their EKA may be critically important.

This is especially important for female brick-walled ancestors, since using this Google string with their daughters’ names may reveal someone else’s EKA in that genetic line within a project.

After clicking through to the project page, be sure to enlarge the page to display the full project, and use your browser search since partial results with predicted haplogroups may not be grouped with full mitochondrial sequence results.

Multiple people who descend from Catherine LeJeune have tested. The first six only took the partial test years ago. The bottom two testers took the full sequence test and have a new Mitotree haplogroup – U6a7a1a. We know that Catherine was born about 1633, in France, and we can see that other people have also tested and list different EKAs. Next, it’s time to research the other ancestors shown, or check WikiTree to see if any of these testers are listed there so you can contact them.

Now that you have found your ancestor’s haplogroup, you can use the free version of Discover to learn more. I wrote about using mitochondrial DNA and Discover in the article Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree, and mtDNA Discover.

Now, let’s move to the DNA testing companies to see how we can find our ancestors’ Y-DNA, mitochondrial DNA, or testers, at 23andMe, FamilyTreeDNA, Ancestry, and MyHeritage.

At 23andMe

23andMe is not a genealogy company. That said, if you can figure out how people are related to you, you might be able to obtain a partial haplogroup for an ancestor. 23andMe shows both Y-DNA and mitochondrial DNA haplogroups to autosomal matches, but there is no Y-DNA or mitochondrial DNA matching, or associated tools.

23andMe caps matches without a subscription at only 1,500, and they don’t support trees, so I struggle to find useful haplogroups without an associated surname.

Browsing or searching your 1,500 allowed matches (you can have around 5,000 with a subscription) for a particular surname may provide you with an abbreviated haplogroup for both male and female ancestors.

Despite my best efforts, while my maternal grandfather’s mother is not unknown, nor are her ancestors for several generations reaching back into Germany, I’ve been unable to find her mitochondrial haplogroup. Evaline Miller (1857-1939) was born and died in Kosciusko County, Indiana, where she married Hiram Bauke Ferverda, an immigrant from the Netherlands.

Ferverda is an unusual surname, so let’s use it for our example. Thankfully, I’m not dealing with something like Smith.

I entered Ferverda in the 23andMe search bar and it shows four results, two of which are in the 2C-3C range, and one that’s further distant.

I already have the Ferverda Y-DNA, so I don’t need that, but I do need the mitochondrial DNA of Eva Miller Ferverda, and I really don’t want to sift through Miller surnames.

I know who Mr. Ferverda is on my match list, and which ancestor we share. His mitochondrial DNA is not Eva Miller’s.

Fortunately, I know who Eva’s parents were, as shown above on my MyHeritage tree, so I can search for Ferverda, Miller, Lentz, Ruhle, Wolflin, and Heubach, several of which are unusual. Reaching back into Germany is difficult.

It’s likely I match all four of those people at 23andMe through a common lineage that descends from either Hiram Ferverda, Eva Miller, or both. Let’s see what I can put together.

Emily is estimated to be a 2C2R. She is younger than I am based on the birth year she provided in her profile which I am not showing for privacy reasons. Emily also stated that her maternal grandmother was born in Warsaw, Kosciusko County, Indiana, and provided family surnames that include Ferverda, Miller, Glant, Zimmermann, and others.

Kosciusko County is where Evaline Miller lived with Hiram Ferverda, and their daughter, Margaret, married Chester Glant. Margaret Ferverda Glant’s daughter, Joyce, was born in Kosciusko County and married a Zimmerman.

But now, I was stuck. That’s all I had in my desktop genealogy software.

I shifted to Ancestry, where I discovered a death certificate and other information that provided what I needed to close the gap.

This information confirmed Emily’s statement that her maternal grandmother was born in Warsaw, Kosciusko County, Indiana.

Therefore, drum roll…Emily carries Eva’s mitochondrial DNA haplogroup, which is T2b.

Let’s move on to the other two matches, both of whom carry haplogroup T2b.

Ian’s maternal grandmother’s birthplace is Leesburg, Kosciusko County, Indiana, and his surnames include both Ferverda and Robison.

Eva Miller Ferverda’s daughter, Chloe Ferverda, married Rolland Robison and had a daughter, Charlotte, whose daughter married a man with Ian’s surname. Their information allowed me to connect the dots appropriately. Ian’s mitochondrial haplogroup is also T2b, which confirms Eva Miller’s mtDNA haplogroup through a second child.

Shirley, the third match who carries haplogroup T2b, also shows the surnames of Ferverda and Robison, and tracks back matrilineally to Eva Miller.

In spite of the many challenges at 23andMe, and thanks to the rare surname of Ferverda, I’ve identified Eva Miller’s partial haplogroup, but not her full haplogroup. A partial haplogroup is much better than nothing and gives me something to work with.

I checked at Ancestry, MyHeritage and FamilyTreeDNA to see if any of those three people have tested there and have trees. Indeed, Ian tested at FamilyTreeDNA and I had corresponded with him and made a note that he is a matrilineal descendant of Eva Miller Ferverda, but he has not taken a mitochondrial DNA test there.

We know that if Emily, Ian, Shirley, or another appropriately descended person were to take a full-sequence mitochondrial DNA test, we would learn a LOT more about Eva’s mitochondrial DNA. If I can’t locate someone who has already tested, I’ll reach out to these people at 23andMe and offer a scholarship for a full-sequence mtDNA test.

It’s ironic that at the most restricted and least likely testing company, I found three people descended from Eva Miller. Hope springs eternal.

Unfortunately, T2b was formed about 8450 years ago and is a very broad haplogroup made up of many subclades, but at least I have something now – and this partial haplogroup may be just the seed I need to lead to more.

Now, let’s move to FamilyTreeDNA and hope that someone there has already taken the mtFull test.

At FamilyTreeDNA

There are multiple ways to find the Y-DNA or mitochondrial DNA of your ancestors at FamilyTreeDNA.

Project Search

You can search for surname projects along with other types of projects.

On FamilyTreeDNA’s main page, without signing in, scroll all the way to the very bottom footer where you will see the Group Projects link.

If you’re searching for a surname, enter that surname in the search box.

The next screen shows projects that people with the Estes surname, including females, have joined. This includes all types of projects and does NOT mean that these projects are relevant to your line, but it does include two surname projects you may find useful.

Scrolling down shows you how many people with the surname of Estes have tested. Keep in mind that some will be females, some use married names, and sometimes people use an alias, so they aren’t included in this count.

Surname projects for females aren’t terribly helpful since the surname typically changes in each generation, at least in Western cultures.

You can also search for keywords, such as Acadian. If you know that ancestral line is Acadian, you may find clues there, including descendants of your brick-wall ancestor.

Group Project Time Tree

Many Group Projects at FamilyTreeDNA have enabled the Y-DNA Group Time Tree feature. When visiting the project, if the administrator has the Group Time Tree enabled, click on that link under the DNA results tab.

The Group Time Tree is a genetic tree of Y-DNA testers within that project based on the groups created by the project administrator.

The groups constructed by the administrator are shown at left, the Time Tree in the middle, and the testers with their EKAs and country of origin flags at right. I’ve added the red text to reflect the Estes genealogical lineage.

Based on the timeline at the top, you can see how closely these Y-DNA testers are related in time. Each haplogroup shown represents a different branching genetic lineage – breadcrumbs at work. If you are a genetic Estes male who descends from the Estes family that originated in Kent, England, and you take the Big Y-700 test, you’ll be a member of R-BY482 or its descendant haplogroups.

Keep in mind that not all testers join group projects, so it’s likely that there will be matches on your match list that aren’t here. Furthermore, only Big Y testers appear on any Time Tree.

The Group Time Tree is public, but when you sign in to your account and click on the Match Time Tree from your account, you’ll be able to view more, including testers’ trees and WikiTree connections if your matches have connected themselves to WikiTree.

Click to enlarge

I’ve converted the Estes genetic tree into a genealogical tree in a spreadsheet based on the trees of DNA matches. I’ve also included STR testers, because they are good candidates to upgrade to Big Y tests, and they are shown in the Estes Group Project. They can’t be included in the Time Trees because they don’t have the SNPs discovered with the Big Y tests. Please note that not all testers were included in this spreadsheet.

You can follow the paths of the various haplogroups. All of the red-background, black-outlined cells are Big Y-500 or Big Y-700 testers. The Big Y-500 was obsoleted several years ago in favor of the much more informative Big Y-700 test, which reveals additional haplogroups because it tests more of the Y chromosome. I’m still hoping that people will upgrade, although some testers are deceased and can’t.

The Big Y-500 tests with red stars are candidates to be upgraded to the Big Y-700 to potentially receive a more specific haplogroup. The balance of the tests in red cells are Big Y-700 tests, which identify several additional Estes haplogroup paths.

Let’s look at an example.

Beginning at the top, we know that R-BY482 is present in Nicholas Ewstas, born in 1496 in Kent, England, because all of his descendant testers carry that haplogroup too. Additionally, three generations later, in Silvester’s generation, he developed the additional mutation named R-BY490. We know it developed in Silvester’s generation for two reasons:

  • The descendants of Silvester’s brother, Robert, born in 1603, do NOT carry R-BY490. Robert’s son Matthew’s descendants only carry R-BY482.
  • The descendants of both of Silvester’s sons, Richard (pink column) and Abraham (the entire green row), all carry R-BY490.

All of the descendants of Silvester’s son, Abraham, born about 1647, the Virginia settler, who have taken the Big Y test carry R-BY490. Additionally, descendants of several of Abraham’s sons, color-coded columns beneath the green row, have developed additional haplogroups. Several more testers would likely have new haplogroups if they took the Big Y-700 test. A new haplogroup requires at least two men with the same unique mutation (breadcrumb), in addition to R-BY490 (in this case), to identify a specific lineage and assign it a new haplogroup name.

Abraham’s son, Moses Estes, born in 1711, is a good example. We know that Moses developed the mutation R-ZS3700 because four of his descendants have taken the Big Y-700 test and have that mutation that is not found in Moses’s brothers’ lines. All four Moses descendants carry R-ZS3700, and two, in the James Carroll Estes line, have developed an additional mutation, haplogroup R-BY154784.

Until Big Y testing became available, descendants of the R-BY154784 lineage didn’t know where they fit in the Estes tree, because the connecting genealogical records between Missouri, where their ancestors are found, and Virginia, where they came from, were missing.

Therefore, if you don’t carry the Estes Y-DNA, but you can find your ancestral line in projects, you can potentially do two things:

  1. Identify the specific lineage to which you belong, especially if you have access to your relative’s test results, including matches and trees.
  2. Without matches, you may still be able to identify at least some haplogroup levels, such as R-BY482 or R-BY490, which opens the door to:
    • Using autosomal results to find matches with Estes-specific haplogroups
    • Using Discover to utilize the dozen+ public reports available for everyone
    • Asking people to upgrade

While I’ve been using the Estes DNA results because it’s a project I administer and the one with which I’m the most familiar, this same approach works for mitochondrial DNA as well, especially if you can identify your ancestor’s DNA in a project.

Finding Projects in Discover

The public version of Discover provides surname and project searches as well, but works a little differently.

Select Group Project and enter the term you wish to search for.

Clicking on the project takes you directly to that project’s Group Time Tree where you can identify your ancestral line.

People who have tested at FamilyTreeDNA can join projects. Many projects accept autosomal testers who descend from that family line.

To join projects, sign in, then from your home page, click on “Group Projects” in the header, and make your selection.

Search for Surnames in Family Finder Autosomal Matches

Now that you’ve identified your ancestor’s haplogroup, you can use that information to find, rule in, or rule out various people in your Family Finder match list as your ancestors’ haplogroup carriers.

FamilyTreeDNA displays the haplogroups of your autosomal matches who have taken the:

The Family Finder test doesn’t test either the Y chromosome or mitochondria fully, but it target-tests a selected number of non-autosomal haplogroup-defining locations. The haplogroups that Family Finder identifies are typically midrange, meaning they are from roughly 2,000 to 5,000 years old. Furthermore, different tests on different chips at different times didn’t always test the same locations. This relatively new Family Finder haplogroup feature is free.

Uploaded DNA tests from other vendors may or may not receive a haplogroup, but regardless, it will NOT be displayed to their matches. Not all other vendors test or include Y-DNA or mtDNA SNP locations in their upload files, and your mileage may vary widely.

My cousin David has taken the mtFull test, so his mitochondrial haplogroup is the most refined possible, but his Y-DNA haplogroup of R-L151 was derived from his Family Finder test. Haplogroup R-L151 is about 5,000 years old. If I needed his haplogroup, it’s useful to rule out other major haplogroup branches that might be found in other men by the same surname. Plus, I can learn quite a bit from Discover.

Haplogroups are displayed in your Family Finder match list for everyone who has taken a Y-DNA or mtDNA test, but currently, only Y-DNA haplogroups are provided for Family Finder results. Midrange mtDNA haplogroups are planned for sometime in the future.

There are several methods to search for either a specific surname or haplogroup within Family Finder matches.

Let’s use my Ferverda/Miller/Lentz haplogroup T2b revealed at 23andMe. That haplogroup would almost assuredly be broken down further with full-sequence testing, and it might have been renamed as a different subgroup of haplogroup T in the new Mitotree.

Let’s begin with searching for haplogroup T2b.

The search bar allows users to select Name, Ancestral Surname, mtDNA Haplogroup or Y-DNA Haplogroup.

You’ll notice that there are a total of 59 results that include T2b as a part of the haplogroup. The mitochondrial lineage I’m seeking is my mother’s paternal grandmother, so the matches should be on my mother’s side, although there is no guarantee I don’t match someone autosomally on my father’s side too.

I checked the trees of all 59 people in the T2b category, and unfortunately, none descended from the line I need.

If you change search terms or categories, be sure to clear your filters.

Under the Filter option, you can filter for several options in addition to searching.

For our next example, I’ve selected both the Big Y-500 and Big Y-700 tests, and searched for Ferverda.

I already have the Ferverda Big Y-700 haplogroup, but if I didn’t, I would now!

Don’t forget that you can sort by any number of fields, and you can download your entire match list into a csv file. I find that easier because I can search, sort and filter at will.

Don’t forget to check back from time to time as more matches are added.

Utilizing Haplogroup Projects

Under the Group Projects header, or by Googling for a haplogroup T2 (or T, or T2b, etc.) at FamilyTreeDNA, you can view the haplogroup T2 project, and filter for haplogroup T2b or any subclade.

Be sure to expand the project’s page size to display the entire project. It defaults to displaying 25 rows at a time, but you can see the number of pages at the bottom of the page. I expanded the page size to 5000 so that I can use my browser search for known surnames in the mitochondrial line.

By using my browser search and searching for each known surname by generation, I searched for Ferverda, Miller, Lentz, Ruhle, Wolflin and Heubach.

I was VERY excited for a minute when I found a Lydia Lentz listed as a tester’s EKA.

Because the female’s surname changes in every generation, there’s only one family in this lineage that Lydia Lentz could have been a member of to represent the mitochondrial DNA of Eva Miller whose mother was Margaret Elizabeth Lentz.

So, the question is whether or not Lydia Lentz is the sister of Margaret Elizabeth Lentz.

Shifting to my desktop software, it’s easy to see that Jacob Lentz and Johanna Frederica Ruhle had four Lentz daughters who lived to marry and have children. None of those daughters were named Lydia, so the Lydia Lentz EKA in the haplogroup T2 project is not representative of Eva Miller’s mother and grandmother.

Margaret Elizabeth Lentz is Eva Miller’s mother, and I had already searched within the project for Miller. I added Yost, Gallagher, and Overlease to the browser search in the haplogroup T2 project with the hope that someone might have listed a woman with one of those surnames as their EKA, but no such luck.

Not everyone joins projects, or provides their earliest known ancestors, but I didn’t find the surnames of any of the females in my known line here.

Let’s see if Ancestry can help.

At Ancestry

Ancestry doesn’t do Y-DNA or mitochondrial DNA testing, so you won’t find your ancestors’ Y-DNA or mtDNA at Ancestry, but their trees can help you find testers.

Let’s shift to Louisa Drechsel, one of the daughters in the Mehlheimer/Drechsel line we were working with earlier that needed more research.

I looked at the hints for Emma Louisa Drechsel, who was always called Louise or Aunt Lou in my family, and discovered another Ancestry member with Emma in their tree.

I clicked through to the tree to discover that the tree’s home person does not descend from Barbara matrilineally, which means they are not a candidate for Barbara’s mitochondrial DNA.

I then clicked on the tree owner’s name to see whether they happen to be an autosomal DNA match to me. They are not. Without messaging them, there’s no way to know whether they have taken a DNA test, and there’s really no point since they are not a mitochondrial DNA candidate.

While I’m at Ancestry, I’m going to check ThruLines to see if anyone who is an autosomal DNA match to me also descends matrilineally from Barbara. There are no autosomal matches shown who have our common ancestor in their tree, and who are mitochondrial candidates.

Remember, a male between the ancestor and the testing candidate always blocks the mitochondrial DNA path.

These people are all autosomal DNA matches.

There may be descendants who either aren’t DNA matches or who haven’t tested who might be mitochondrial candidates. They can be located by checking Ancestry’s trees for our common ancestors and determining how the tree owner relates to that ancestor, if they do.

Compare Trees is New

Ancestry recently introduced “Compare trees”, a new beta feature. It may not be fully rolled out to everyone yet, and because it’s in beta, the feature may change.

To access this feature, go to your tree, not their profile card.

I clicked on Barbara Mehlheimer’s link in my tree, which displays this little mini-profile. Then click on “Compare trees” at the bottom.

Ancestry displays your tree, at right, and the other tree, at left. You can select another tree to compare at top right.

Ancestry’s comparison only shows a total of three generations – the selected person, their parents, and their children.

The person I actually want to follow is Louisa, but if you click on Louisa’s card here, it simply compares the two Louisas – it doesn’t shift down a generation.

This means that to follow more recent generations, you have to go back to your tree, select someone further down in the tree and repeat the process.

This process is cumbersome, but doable thanks to the new Compare Tree function. I’ll come back to this after checking the rest of the “easier to harvest” fruit from other resources. Remember to make notes in your research journal so you don’t forget where you left off – although trees are always changing.

MyHeritage has one of my favorite tools.

At MyHeritage

Recently, MyHeritage has begun providing midrange Y-DNA haplogroups for some of their DNA testers. If you’re one of the lucky testers, you can use the free Discover tool to learn about your haplogroup, but a haplogroup alone won’t help you much with genealogy. You need matching and advanced tools for that.

Unfortunately, you can’t see the haplogroups of your matches, so you can’t search or filter using that criterion. You can, however, ask any men with the surname you’re seeking if their haplogroup is displayed.

Cousin Finder

MyHeritage has an ingenious tool called Cousin Finder that I wrote about here. Cousin Finder helps you find cousins who share common ancestors with you, regardless of whether or not you are a DNA match.

MyHeritage found 531 people in their database that share ancestors according to both their and my trees.

This list of matches doesn’t page; it scrolls, so I made a spreadsheet of the people who are relevant to my search for my brick-walled ancestor. Scrolling becomes difficult and very slow as you proceed down the list. I didn’t want to have to do this twice.

You can improve performance by using the relationship side filter. Because your ancestors match, MyHeritage knows on which “side” of your tree your common ancestor is found.

At this point, I’m interested primarily in identifying Y-DNA or mitochondrial DNA candidates for a specific ancestor.

Using the Drechsel/Mehlheimer line as our example, I’ll search on my mother’s mother’s side.

We already met Patty at WikiTree, but let’s pretend we don’t know Patty. I can click on “View her tree” to see Patty’s whole tree, or I can click on “View Relationship,” which shows how we are both related to our common ancestor.

As we know, for mitochondrial DNA, any male in the line between the ancestor and the testing candidate blocks the mitochondrial DNA path. Patty inherited her mother’s mtDNA, not her father’s.

I didn’t forget about Eva Miller Ferverda either.

I searched for cousins who descended from my mother’s father’s side to find mtDNA candidates for Eva Miller and didn’t find any. But I did find an entirely unexpected bonus.

My mother’s father’s line shows all the connections on that side. While clicking through each one, I quite serendipitously discovered a mitochondrial DNA candidate for Eva Miller’s husband’s great-grandmother, Anna Elizabeth Jonker, AND, separately, a potential Camstra Y-DNA tester too. Oh, happy day!

It was only later, while working on my genealogy for Frederica Ruhle and hoping to discover where she actually lived in Pennsylvania, that I discovered that MyHeritage has put a Cousin Finder link in each ancestor’s profile.

Who doesn’t love a pleasant surprise?!

You no longer need to sift through all of your cousins on a particular side, but remember, had I not done that, I wouldn’t have found either the mitochondrial descendant of Anna Elizabeth Jonker nor the Camstra Y-DNA candidate.

At FamilySearch

FamilySearch is more challenging and is best for fleshing out trees where not much research has been done. Remember that FamilySearch has access to records that are not available at either Ancestry or MyHeritage.

FamilySearch is a one-world tree. Like all trees, it’s subject to errors, so caution is always advised.

At FamilySearch, from your profile card in the tree, locate the ancestor whose Y-DNA or mtDNA you seek.

Then click on that person. Their profile card will pop up. Click on “Tree,” then, at the top right, select Portrait.

Now you can expand their children downward. Note that the little “two people” in the top left corner of the profile card means there are multiple spouses. The only way to view all of the children is to click on that person’s placard, then select the alternate spouse.

Living people have no placeholders on this tree.

You can contact contributors who provided information on a profile in the tree.

Click on the source provider’s name to see if they are related, and click on the little tree icon to see how.

However, once a year, there’s a great way to contact interested descendants.

Relatives at RootsTech

RootsTech is the largest genealogy conference in the world, and it’s sponsored by FamilySearch.

About six weeks before RootsTech takes place each year, and for about a month after, you can participate in Relatives at RootsTech.

During that time, you can select an ancestor and see which other people who have signed up for RootsTech also descend from that ancestor. I wrote about how to do that in the article, Relatives at RootsTech Reveals Cousins and Provides DNA Candidates. I almost always find someone who descends from an ancestor whose Y-DNA or mtDNA I need for my tree.

It’s a wonderful opportunity to meet new cousins and collaborate.

At GEDmatch

GEDmatch is an autosomal DNA upload site that offers a variety of matching and display options. While they don’t attempt to calculate a haplogroup, uploaders can enter their mtDNA and Y-DNA haplogroups, if known.

GEDmatch isn’t normally a resource we think of for either Y-DNA or mtDNA, but it can be useful under some circumstances.

In the One-To-Many limited free version and the Tier 1 subscription model, you can view haplogroups if someone has entered their haplogroup name, but you can’t filter without the Tier 1 version.

I filtered for haplogroup T2b and found one person in the match list with haplogroup T2b4. I then viewed the GEDCOM that this person has also uploaded, but they do not descend from Eva Miller Ferverda’s line.

GEDmatch isn’t built for haplogroups, but sometimes, if you have a known haplogroup that isn’t terribly common, you can catch a lucky break there.

Where AM I?

OK, so where am I in all of this?

I feel like I’ve searched the corners of the earth!

I’ve primarily used two examples.

  • My own mtDNA line which is the Drechsel/Mehlheimer line that I chose because it’s a great example that I knew well.

If I had actually been searching for a testing candidate, we would easily have eliminated several possibilities. Five female lines remained as possibilities that need additional research, plus my own test if someone were actually searching.

  • Then there was Eva Miller Ferverda (1857-1939), whose partial haplogroup, T2b, was discovered at 23andMe in three matches. I was able to reconstruct their trees, confirming that this was her line, but I was unable to find any testing candidates elsewhere.

Each of the DNA testing and genealogy vendors provides a way to communicate with other users of their platform.

  • At both 23andMe and MyHeritage, you can message through their platform.
  • At FamilyTreeDNA and GEDmatch, you can email your matches.
  • At WikiTree, you send an email through their platform to the profile card manager.
  • At FamilySearch, you cannot see placeholder cards for living people, so you need to check to see if people making changes to that ancestor’s profile are related. Then check their children closest to the present day for the same information. You can message through the FamilySearch platform.
  • During Relatives at RootsTech, you can message your cousins through their platform. The great thing about these folks is that you know they are interested and engaged, because they’ve just signed up for RootsTech.

Communicating With Testing Candidates

I’m fortunate that there are three mitochondrial descendants of Eva Miller Ferverda at 23andMe, one of whom is also at FamilyTreeDNA. I will message or email all three of them individually with a short, customized message that contains:

  • How I am related to our common ancestor.
  • A question about whether they have taken the mtFull test, or any test, at FamilyTreeDNA. If they have taken any test there, it’s easy to upgrade.
  • A sentence about how FamilyTreeDNA was the original genetic genealogy founder of this industry and the only company to offer the full mtDNA and Y-DNA tests.
  • Why they can benefit from taking the mtFull test and how it can help us learn more about our common ancestor.
  • An offer for a full-sequence mitochondrial DNA testing scholarship if they have not already taken that test.
  • I ask if they are interested and provide my email in case they have questions or want to discuss further.

Depending on how much space I have for the message, there are two articles I often provide links to in case they are unfamiliar with either Y-DNA or mtDNA testing.

  1. 4 Kinds of DNA for Genetic Genealogy is a very basic article for people who might be unaware that there is any type of DNA testing other than autosomal. This is often the case with Ancestry.
  2. The article Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree, and mtDNA Discover is an in-depth article about using mtDNA. This is a wonderfully educational how-to article, but I always hesitate before sending this one because I don’t want their eyes to glaze over.

Scholarships

I gladly and eagerly offer scholarships for both Y-DNA and mtDNA testers from lines I need to represent my ancestors.

I equate scholarships to finding a rare out-of-print book about that exact family line, with only one or two copies still in existence, and only one accessible in a rare book shop in Podunk, Idaho. I would book a flight tomorrow at 5 AM to go and pick it up in person even if I had to eat beans and hot dogs for the next six months to pay for it. If you know me, you know I’m not kidding! I’ve gone on many wonderful road trips to meet with and collect DNA samples from cousins.

A Y-DNA or mtDNA test doesn’t cost nearly as much as that excursion and is even more reliable, because we know the DNA results are accurate – assuming the tester’s genealogy is accurate, which you should verify, and no undocumented adoptions or broken lineages have occurred.

Good luck on your treasure hunt!

____________________________________________________________

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 – A New Series Focused on Breaking Down Brick Walls

When I teach about genetic genealogy, people often ask, “What’s next? How can I break down my brick wall?” Sometimes I can reply that a Y-DNA test or mitochondrial DNA will help them under specific circumstances. But more often than not, what they really need is a precise, step-by-step methodology that includes autosomal DNA and utilizes multiple tools and techniques across vendors.

Even after people have taken Y-DNA and/or mitochondrial DNA tests PLUS autosomal tests at the major vendors, we still need a methodology to work with combinations of those results. Often, the answers we need aren’t just sitting there like a pretty rock, waiting to be picked up and admired, but depend on us using the results and matches as tools to help focus our search in the right direction.

It’s more like a scavenger hunt than a single discovery.

Focus

Sometimes I feel like a fish out of water – flip-flopping from ancestor to ancestor, match to match and hint to hint, hoping that the magic bullet will fall into my lap, but that almost never happens.

By this point in my research, I’ve perused all the easy records and many of the not-so-easy ones. If you don’t have a surname, or you don’t have a first name, or worse yet, you don’t have either, how is one supposed to search for records?

The good news is that you still carry at least one record in your own body and/or the bodies of your relatives. The DNA of your ancestors.

This is where we’re going to focus our efforts – hence FOCUS, the name of this new series.

Everyone is going to select their closest, or one of their closest, brick-walled ancestors, and we’re going to use several methods and tools to focus on identifying that ancestor.

Prepare

Before I publish the next article in the series, there are a few things that I’d like you to think about and do in preparation.

  • First, there’s no guarantee that you’ll break through your brick wall during this series. You might, and you also might not. You stand a much better chance of breaking through that brick wall if you focus and follow these steps than if you don’t.

Keep in mind that even negative evidence is evidence, and just because you don’t break through right away doesn’t mean you won’t. New people test everyday and new records become available too. If nothing else, your ancestor will have more meat on their bones, and you’ll have a process to build upon.

  • Second, if your brick wall is very close in time, meaning parents or grandparents, you’ll want the already-written “In Search Of Unknown Family” series, which you can find, here.
  • Third, you’ll need to keep a research journal or log by ancestor, family or location, which will also include your other related ancestors. For example, if you’re looking for Lucy whose surname you don’t know, but you know that she married William Moore, then your research journal will apply to William Moore too, and other people including their children and either spouse’s parents and siblings, whether that was your intention or not. The neighbors are probably relevant as well.

That “it takes a village” saying is particularly relevant here. People didn’t tend to move to the next location alone, and often their community consisted of their cousins and relatives – who are also your relatives, and hold clues to the identity of your ancestor. When I’m extracting records for the Moore surname in Halifax County, VA, for example, I extract everything for that and similarly spelled surnames, not just one particular person, so I don’t have to replow that field.

Tracking and Recording Your Research

If you don’t already have a research journal methodology, I would suggest a spreadsheet.

Here’s a screenshot of two rows in my “Halifax County” spreadsheet where I’ve recorded separate rows for each person in every record. Note that I started this spreadsheet years ago and omitted some columns that I later wished I had included, like the access date.

You’ll want to record:

  • Item number beginning with 1. In the example above, the item number is 6, and it’s 6 for every person in that record. Each person in this transaction gets their own separate row, with the same item number. The next record I extracted would be item 7.
  • Access date (date you found and retrieved the record)
  • Last name
  • First name
  • State (add a column for country if multiple countries are relevant for this family)
  • County
  • Town, township or city
  • Geographic places like road or creek names (these can be VERY important)
  • Year, month and day that the record occurred
  • Record repository or source (including a link if applicable – you may want to add a separate column for the link)
  • Record type (deed, will, tax list, etc.)
  • Role of individual (buyer, seller, witness, etc.)
  • Names of additional people in the record (I retain the same item number and other information, changing the name of the person, their role and sometimes an associated comment)
  • Transcribed text of the record itself
  • Comment, which can include things like the name of an image, something about what you were searching for when you found the record, links, or anything else relevant

You will want to be able to sort and filter this spreadsheet when you are finished. Hint – be sure your date fields and formats are sortable in the way you wish. I normally use filters instead of the sort feature.

The goal isn’t just to record your findings, but to make this spreadsheet as useful as possible to make discoveries that are only available by comparing and incorporating multiple records.

For example, let’s say that you’re extracting all of the Moore records in a Halifax County, VA deed book, and you want to know how many times the surname Henderson is found in the Moore deeds or in conjunction with the Moore family. Is there a pattern? You won’t recognize a pattern from any ONE record, but you may eventually wonder if the Henderson’s are related to the Moore family, and if so, how.

You’ll also want to record nonproductive or negative evidence. For example, let’s say you searched the Halifax County Plea Book for William Moore (including More and Mohr) and found no occurrences. That’s important, because otherwise you‘ll eventually search again, so enter that as a record item.

Note that with the full text search feature introduced by FamilySearch a couple of years ago, if you extracted records from a book that did NOT include every-name indexing including property lines, creek names and witnesses – you’ll want to redo that search using the full text feature at FamilySearch. There’s often LOTS of valuable information buried in records that won’t be found if you’re only viewing records indexed by buyer and seller, for example.

Your To-Do List Before the Series Begins

The In Search Of Unknown Family Series introduces important concepts, so reading that series is your first assignment in preparation for the upcoming FOCUS articles.

Test Your DNA With the Major Vendors

It’s important to test with the major vendors. Each vendor has matches and tools that the others don’t, and we need to identify and work with as many relevant matches as possible.

If you have NOT taken an autosomal DNA test at the first three following vendors, order these tests now so you have results to work with.

  1. AncestryDNA
  2. FamilyTreeDNA – Purchase a Family Finder test or upgrade an earlier Family Finder test to the new Family Finder NGS test. You should upgrade if you uploaded your autosomal DNA file from another vendor at any time, or tested at FamilyTreeDNA directly before March of 2026. The upgrade is only $29.
  3. MyHeritage DNA
  4. A fourth vendor, 23andMe, is optional, but testing there certainly won’t hurt.

23andMe Sidebar

I have an issue with 23andMe’s policy of forcing customers to repurchase a DNA test at $199 PLUS a subscription at $149 for the first year, renewable at $69 per year, in order to obtain any of their latest tools. This happened around the time of their data breach and subsequent bankruptcy.

I would feel much better about the situation as a whole if a new owner had taken the wheel, but the original owner resigned from the 23andMe board, formed another corporation, and was allowed to buy 23andMe out of the bankruptcy that occurred on her watch.

Furthermore, 23andMe does not support genealogy trees, nor do they have Y-DNA or mitochondrial DNA testing and matching, or research records.

I have (begrudgingly) ordered an upgrade for my own 23andMe test in order to include accurate information in these articles, but I won’t be focusing on 23andMe specifically aside from any unique feature. You can apply the same concepts and techniques to results at 23andMe where possible.

Test Your Relatives

If you have close upstream relatives, such as parents, grandparents, aunts, uncles, and cousins who also descend from your brick-walled ancestor, please ask them to test too.

I explain what I’m trying to achieve, why their test is important, and offer scholarships to sweeten the pie. I view purchasing their DNA tests in the same way I view purchasing a rare research book that I KNOW includes my ancestors but it not available anyplace else.

Your shared matches are extremely important and may provide that brick-wall-breaker. Perhaps even more importantly, they will have relevant matches that you don’t.

So how do you know who to test? You certainly want to test everyone relevant, without wasting money.

Let’s look at this example where Lucy is the brick-walled ancestor I’m seeking to identify. Her children (labeled siblings) and grandchildren (1C) are all deceased, but second cousins (2C), Rhonda, Charles and Sally are all available to test. Test each of them because they will all have some different segments of DNA from Lucy that the others don’t have.

Lazarus is also a second cousin, but he’s deceased. However, William, my father (in this example, not my real pedigree), and his sister, Jane are both available to test.

You ALWAYS want to test both of your parents and every available grandparent or direct ancestor. In this example, I’ll only inherit some portion of Lucy’s DNA that my father has, but Jane, my aunt, will carry segments of Lucy’s DNA that my father didn’t inherit from Lazarus. Jane’s matches on those segments that neither my father nor I have may be just what we need to identify Lucy.

If Lazarus has other children not shown in this example, we certainly want to test them too.

If the relevant parent has tested, you don’t need to test any of their children. However, if the parent hasn’t tested, absolutely test as many of their children or descendants as possible.

In this case, Rhonda, Jane, Charles and Sally have all tested, so I don’t need to test their children. Their children can only have as much of Lucy’s DNA as their parents had.

However, if any of them had been deceased, then I should test as many of their children as I can to “gather up” as much of Lucy’s DNA as possible.

If any of the people upstream of the bold red people have other children, those children or their descendants would be testing candidates too. Ideally, you want as many descendant testers as possible to increase your chances of identifying that ancestor.

Selecting Your Brick-Wall Ancestor

I want you to be successful, so you’re going to select your closest brick-walled ancestor within certain parameters. If you have multiple brick-walled ancestors at the at the same genealogical distance, you’ll choose one to focus on.

Why your closest brick-walled ancestor? If your brick wall is 5 generations back from you, and they are 5 generations back from your DNA match as well, that means you’re dealing with a 4th cousin match.

This also means that ancestor’s DNA has been divided a total of 10 times – five times on the path of descent to you, and five times on the path of descent to your match.

A 4th cousin match is likely to be in the 35 cM range. You can view the matching ranges for various relationships at DNAPainter, here.

The entire 4th cousin (4C) matching range is 0-139 cM. You won’t match all of your 4th cousins and are likely to match only 50-70% of your 4th cousins.

That said, the average person has between 1,500 and 4,000 4th cousins. At the 4th cousin level, you have 32 ancestors, so only between 46 and125 4th cousins will descend from any given ancestor, and of those, only a few will have taken a DNA test. The more children that ancestor had that lived to marry and have children of their own, the better your chances of more matches.

The Selection Process

I’m going to be stepping through the ancestor selection process with you, discussing who is and isn’t a good candidate, and why. I’m also going to be using this same methodology to (hopefully) identify one of my own mystery ancestors too.

I have no brick walls closer than 4th cousins. If I did, I’d choose the closest brick wall. You should too in order to have the best chance of solving this puzzle. The further back in time, the more difficult the solve will be.

In my tree, I have four mystery ancestors at the 5X great-grandparent level on my father’s side, and one on my mother’s side.

Those will be the four ancestors I consider selecting. And no, before you do it, I don’t recommend working on all four of them at the same time. Remember, the purpose is to FOCUS.

  • Select an ancestor as close generationally as possible, because it’s more likely that both you and other people will carry at least some of their DNA, and the same segment(s) of DNA. Matches closer in time generally carry more total DNA in common, which means better matching and more shared matches.
  • Given that the majority of testers are from the US, and assuming you are from the US too, I don’t recommend selecting an ancestor from another country unless you are very comfortable with that language and working with those records. Generally, there will be fewer people who have tested from other countries. If you are going to work with an ancestor from another country, be sure you are in both the MyHeritage and FamilyTreeDNA databases.

My mother’s entire paternal line is either Dutch or German Brethren, and her Dutch ancestors only immigrated in the mid 1800s, so have few descendants in the databases.

My closest brick wall on her paternal line is Traut Enterlein, a German man who was named in an out-of-wedlock baptism for his daughter in Germany in 1823. He is not found in any other records in that part of Germany, so actually identifying “who he is”, even with a name, would be extremely difficult, and I have nothing to “anchor to” here.  He is eliminated as a candidate because he’s found in a country where I don’t speak the language, where fewer people have taken DNA tests, and we’ve already spent a substantial amount of time trying to identify him in the records.

Brick-walled ancestors on Mom’s maternal side are two generations further back in time. Half are German and the other half are a combination of English and Acadian.

  • Avoid both endogamy and pedigree collapse, if possible. I don’t recommend a line with baked-in challenges that will make DNA more difficult.

Acadians are heavily endogamous and often suffer from pedigree collapse since there were so few founding families in the mid-1600s. The same goes for Brethren families who immigrated in the early 1700s. Those lines are too far back generationally anyway, so they have already been eliminated, but if they weren’t, I’d eliminate them because of heavy endogamy and pedigree collapse, both, not to mention record loss.

My father’s side has much better candidates.

  • Try to select an ancestor where you have some familiarity with the location, the culture, and the records. If you have printed resources at the ready, possibly ones that are not online, that’s a plus.
  • When you’re trying to decide between ancestors, select one whose spouse you are sure of, and who has children you can document. Do you know important things about them like their religion, where they lived during specific times, and who their neighbors were? If not, take some time now to brush up on what you do know about their spouse and children.
  • Check back at all of the records vendors and resources, including Ancestry, MyHeritage, WikiTree, and FamilySearch, to see if anything new is easily available for either your brick-wall candidate or their spouse.
  • I do NOT recommend selecting an ancestral couple, neither of whom you can identify, unless you’re “lucky” enough to have no other brick-walled ancestors to choose from. It’s possible to solve this “double-blind” couple, but it’s substantially more difficult because you have no same-generation anchor.

My Candidates

I’m selecting one of my brick walls and hope to solve it during this process. Let’s run through the decision-making process so you’ll understand some of the considerations and why they weigh as factors. I wish I didn’t have so many choices, and I’d like to solve them all, but my best chance is to work on one at a time.

Most candidates are women because their birth surnames tend to easily become lost after they marry, and with their surname, their parents are lost too. Given how little we know, we have to presume (dangerous word), at least for now, that your missing female ancestor was the mother of all of their husband’s children, unless we know or subsequently prove otherwise.

Let’s review my candidates.

  1. Lucy was born about 1754, probably in Virginia, and died in 1832 in Halifax County, VA. She married William Moore between 1772 and 1774, who may or may not have been a circuit-riding minister at that time. She is found under her own name on the 1830 census, there’s an 1826 chancery suit, and I know who her children and neighbors are, so she might be a good candidate. One vote against selecting Lucy is that I don’t know where she was born, nor do I know where they were married, although there’s a very strong possibility that it took place in Halifax County. The fact that he was a circuit-rider means he could have met her anyplace. If they were married in Halifax County, their families could have been allied before arriving there. William Moore’s family came from Prince Edward County about 1770, and we know who his parents were. One good thing is that Lucy is a fairly uncommon name, but there are multiple William Moores in Halifax County, and there are two other Lucy Moores. One is her daughter, and one is her daughter-in-law. The fact that Lucy and William Moore had 12 known children, with at least 8 who married, means there is a good chance of matching at least some descendants. Unfortunately, I don’t have her mitochondrial DNA, which removes one possible tool unless I can find a tester.
  2. Jane, born about 1760 in an unknown location, but probably Virginia, was the wife of Lazarus Dodson. They moved across multiple frontiers into what would become early Tennessee, an area that sustained substantial record loss. Jane died between 1830 and 1840. There’s a lot of uncertainty about Jane’s life. She probably had at least 8 children, and we know something about six of them. Given that we already have a better candidate with Lucy, I’ll eliminate Jane for now.
  3. William Crumley’s wife, whose name I don’t know, was born around 1765 or 1770, possibly in Virginia. She was married to William Crumley around 1786 or 1787, probably in Frederick County, VA, or nearby. I do have her mitochondrial DNA and we know the family was Quaker which are both benefits. I’ve been working with a cousin who has delved deeply into Quaker records, and I have some records from a trip to the FamilySearch Library in Salt Lake City that I have not yet processed. She and William had at least 10 children who married, and I know quite a bit about them. She would probably be an excellent choice. For lack of another name, I’ve been calling her H2a1, her legacy mitochondrial haplogroup before Mitotree, but she has a much more complete haplogroup now. She would be a good candidate, and I REALLY want to identify her.
  4. Mary, wife of John Harrold (by various spellings), was born about 1750, possibly in Ireland, although it would be unusual for a first-generation Irish immigrant to end up deep in the Appalachian frontier. Mary died in 1826 in Wilkes County, NC. We know nothing about John’s background, other than he served in the Revolutionary War, in Virginia. He may have been living in Botetourt County, although we don’t know for sure, and there are multiple men by that name. Mary had at least 7 children, six of whom were married. We do not have her mitochondrial DNA. Given that we know so little about John, and we have better candidates with both Lucy, William Moore’s wife, and William Crumley’s wife, I’m eliminating Mary for now.
  5. Isabel, the wife of Michael McDowell – another couple from Wilkes County, NC. Their daughter married the son of Mary and John Harrold. Isabel was probably born about 1750, someplace in Virginia. We don’t know where they were married, but it could have been in Franklin County, VA. They lived in Wilkes County for several decades before moving on to Claiborne County, TN. We know very little about Michael’s early life, other than his Revolutionary War service, although I’ve written about him four times as additional information dribbles out. They had at least 8 children, and a deposition after Michael’s death tells us where they moved and settled, which is a very big plus. We know her first name thanks to a 1793 deed. Isabel is a reasonable candidate, but I eliminated her after comparison to the other candidates, in part because of multiple frontier moves with few records and no known point of origin.
  6. Elizabeth, wife of Andrew McKee, was born about 1767, possibly someplace in Virginia. They were in Washington Co., VA by 1789, although we don’t know where either originated. They may have married before they moved to Washington County, where we find several records. They had 14 children. Twelve are known to have married, and the other two probably did as well. We know who their neighbors were. We also have Elizabeth’s mitochondrial DNA. Unfortunately, we know nothing about Andrew McKee’s family or where he was from. However, Elizabeth is a strong candidate because so many records exist in Washington County, they had a large number of children, and many continued to live in Washington County or nearby, making them easier to track.
  7. If I didn’t already have good candidates, there’s one more ancestor I’d consider, even though James Lee Claxton/Clarkson is a generation further back in my tree, born about 1775, and his unknown parents are the brick walls. I know I just told you NOT to do this, so I won’t either, but the reason I might have considered his parents, or more specifically his father, as a strong candidate is because we have several Y-DNA matches, including Big-Y testers, and we know the ancestors of his matches came from NC. We also have many autosomal testers and matches, which would help immensely, and there’s a Clarkson/Claxton DNA Surname Project. A contiguous surname is a HUGE benefit not available with female ancestors, and I just feel that I’m SO CLOSE to solving this mystery. For now, James’s parents are eliminated because they are two generations further back in time than our other candidates, we know nothing about either of them, except Y-DNA results, and we have better candidates for this exercise.

After evaluation, I still have two candidates in the running – Lucy, wife of William Moore, and H2a1, William Crumley’s wife. I haven’t decided for sure yet, but right now, William Crumley’s wife is leading because I have an amazing collaborator along with some unprocessed records that may hold important information. I know there probably aren’t any smoking guns there, but when combined with DNA, we may well ignite that gunpowder.

FOCUS

Are you ready to focus?

Let’s get our ducks in a row.

  • Order any DNA tests you need to order for yourself and relatives now.
  • Select your ancestor.
  • Prepare your research journal by reviewing which records you’ve already researched and record what you have.
  • Refamiliarize yourself. Take a look at those results again with fresh eyes. It helps when reviewing match results to be able to view surnames in your matches trees and recall that you’ve seen that name before, and where.
  • Check to see if any new records or resources are now available.

Who do you want to find?

_____________________________________________________________

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

The New Family Finder NGS Test Results, Comparison, and Preparation

This article is focused on two things.

  1. Comparison of my new NGS and the earlier Family Finder tests
  2. How to prepare for yours if you’ve ordered the upgrade

I compared my results from my older Family Finder test with my new NGS Family Finder test results. As an early beta tester, I have two separate tests, a strategy that is not recommended because it causes duplicate matches for people within the database. Additionally, multiple kits for one person doubles the results and could skew future ethnicity research for myOrigins.

Therefore, FamilyTreeDNA has announced very attractively priced upgrades at $29 for both:

  • People who have taken Family Finder test directly at FamilyTreeDNA
  • People who have uploaded their DNA files into Family Finder from other companies

After seeing my comparison, you may want to compare your own results when they arrive, so I’ve documented that process. Warning: this took between 4 and five days because I was working with a spreadsheet with more than 15,000 rows, and I had to write scripts to perform multiple functions. It was NOT fun and I do not recommend it.

Personally, had I known then what I know now about how reliable the new NGS test is, I wouldn’t have bothered with the comparison. However, I would have downloaded my original match list for posterity, just in case.

If you purchase an upgrade to the new NGS Family Finder, your new test results will replace your older Family Finder test results, but will preserve important account features such as linked matches, any notes you have taken, and more. That’s another reason to upgrade rather than order a separate new test. They’ve done the heavy lifting, not to mention that you’ll save about $50 when compared to the price of a new test.

Why is the New NGS Family Finder Test Better?

The new NGS test holds immense promise for the future. This includes better matching, beginning now. Essentially, FamilyTreeDNA is skating to where the puck is going to be (hockey analogy) and preparing for future tools. That future is not far away!

An amazing new set of tools is goaled for release around the end of the year. And I do mean amazing. They are being beta-tested internally now.

Dave Vance spoke about the new Family Finder NGS test at the ECGGC conference in late August, which you can view through the end of 2026 if you register for the virtual  conference, here, and watch the recorded sessions. You’re looking for the DNA Academy on Saturday evening. I can’t share specific preview slides with you as they are noted in his presentation as “not for distribution,” so my pen is capped for now.

All I can say is that after seeing what’s in store, people were literally throwing their billfold at the folks at the FamilyTreeDNA booth – and I do mean literally. “Here – take my money, please!” as the billfold went sailing. We all had a good laugh, but he was serious.

One presenter (not me, just in case you are wondering) left her credit card and a list of tests to upgrade while she was presenting.

They ran out of swab kits at the conference shortly after Dave’s presentation about what the future holds.

Additionally, you will also be treated to THE absolute best presentation I’ve ever seen about what NGS testing is, how it works, and how it compares to traditional tests, low-pass whole-genome tests, and medical-grade whole-genome tests.

You’ll be a passenger on the Genome Valley train, so climb aboard!

So, without spilling any beans, what’s so great about the NGS test?

To begin with, the older Family Finder tests won’t be able to provide everything the new NGS test will be able to offer – and those completely new tools are in active development today.

Why?

The NGS test targets over 280 million base pairs, up from the currently available 700,000.

That’s more than 400 TIMES the coverage.

This increases coverage in the human genome from about .02% to about 9%.

To quote FamilyTreeDNA, “This change allows us to deliver more precise autosomal results today while creating a strong foundation for future reports and tools.”

You can read the FamilyTreeDNA FAQ here.

Before we move on to the comparison, let’s talk for a minute about test types and uploads from other vendors.

Tests and Uploads

All new Family Finder tests purchased at FamilyTreeDNA since March 2, 2026 have been tested using Next Generation Sequencing (NGS), so the following matrix does not apply to those tests. Those tests don’t need to be upgraded.

If you sign on to your account, on the Family Ancestry dashboard, and see that your NGS button is grey, then you have not upgraded. Click on that grey button to read more and to upgrade. Right now the upgrade is $29, but I don’t know if that is a promotional price or permanent.

If you tested at FamilyTreeDNA prior to March 2, 2026, or uploaded a DNA file from another vendor, your test will fall into one of the following upgrade path categories.

Tested at FamilyTreeDNA before March 2, 2026 Uploaded and purchased the Unlock Uploaded but did not purchase the Unlock
Upgrade Path Can use sample stored in lab if enough DNA remains* If you purchased any other type of test at FamilyTreeDNA, they will use DNA stored in the lab if enough remains. Otherwise, you will be sent swabs. If you purchased any other type of test at FamilyTreeDNA, they will use DNA stored in the lab if enough remains. Otherwise, you will be sent swabs.
New Swabs* If needed, they will notify you Yes, if needed, will notify or send swabs if you have not taken a direct test at FamilyTreeDNA Yes, if needed, will notify or send swabs if you have not taken a direct test at FamilyTreeDNA
NGS Results Will replace existing results Will replace existing results Will replace existing results

*You will be notified if enough DNA does not remain, and you will be sent new swabs. Be sure your address is current.

One of the reasons the NGS test performs better, even with existing matches from earlier tests, is because less imputation is involved. Let’s talk for a minute about imputation and how it works.

The Concept of Imputation

Most vendors change chips internally from time to time, and FamilyTreeDNA is no different. The difference this time is that the new NGS test covers exponentially more DNA than any earlier test, and all earlier tests combined. This means more than 400 times greater coverage, which in turn means less imputation is needed to compensate for the inevitable no-reads and to be compatible with files that tested different DNA locations.

Imputation is also used when comparing DNA files between vendors who don’t test the same locations.

Click to enlarge any image

Here’s an illustration of the concept of how imputation works.

All of the FamilyTreeDNA chip versions over the years have included about 700,000 locations, as have most other vendors. But the locations tested are not universally the same.

In our simplified concept example, FamilyTreeDNA’s tested “locations” are shown with blue cells.

The total of 20 squares shows the maximum amount of DNA tested by any of the three vendors shown, combined.

Green Vendor 1 in our illustration tests the same amount of DNA that FamilyTreeDNA tests, 12 squares, but some locations are the same and some are different. Of the 12 colored squares for both vendors, seven are the same locations, and five are not. The locations that are the same can be compared directly, but the locations that are different have to undergo special handling called imputation.

Looking at any location in our DNA, one of four nucleotides, or letters, can be present: T, A, C or G on each strand of our chromosomes, although we are only looking at one strand in our example.

Using a very simplified model of imputation, think of imputation as “filling in the blanks” using clues from surrounding letters – kind of like a crossword puzzle.

When two vendors’ data doesn’t overlap, imputation is used to fill in the blanks, as accurately as possible, for the missing data.

Using a word analogy, for vendors one and two only, we see that blue location three has no Family Finder data, where green Vendor 1 does, and the same with location five. If blue locations two and four are C and T, and three has to make a word, then there are few options. In this case, let’s say it’s cat, and location five is imputed to an A too.

Now moving to green Vendor 1, their locations two and five need to be imputed. Moving away from the word analogy, let’s look to the human genome, and let’s say that most of the time, location two is a C if location one and three are Gs. So green location two is imputed to C.

If there’s not enough quality surrounding data, imputation can’t be performed reliably. Hence, location six is still in limbo here.

You can see that in our scenario, location three is the only mismatch, out of three imputed locations. Does location three mismatch because imputation was wrong? We don’t know. Do locations two and five match because imputation was wrong? We don’t know.

All things considered, imputation is based on the science of probability, and is usually relatively reliable, but it’s still not the same as comparing actual data. The more locations that have to be imputed, and the longer the stretch, the greater the possibility of error. Every vendor implements imputation differently too. Even vendors who don’t and have never accepted uploads still use imputation internally to equalize their own legacy files from earlier test versions.

Stepping back once again to compare the four vendors, you’ll notice that pink Vendor 3 only tested half as much DNA as the blue Family Finder test and green Vendor 1, and again, not all of the same locations. That’s exactly what happened with one of the vendors last December – they dropped the number of DNA locations tested to about 400,000 from about 700,000. In our example, you can see how much would have to be imputed. Locations 11, 15, 19 and 20 can’t be imputed for the pink vendor’s file because there’s no surrounding DNA. Location 17 can’t be imputed for the green vendor for the same reason.

When vendors impute to match multiple versions of other vendors’ uploaded files, it can quickly become messy.

The answer, of course, is a “supertest,” which tests all of the locations that overlap everyone, including that vendor’s own earlier tests.

Welcome to Family Finder NGS, shown in orange at the bottom of our example comparison.

As you can see, the orange NGS test covers all of the locations tested by all of the other tests.

NGS is targeted testing for a specific set of locations that are known to undergo mutations in the human genome and provides extremely high-quality results. Imputation for the NGS file is rarely necessary, although imputation for the other vendors’ and earlier file versions is still required for them to match to each other.

This is exactly why the upgrade is recommended, and why there’s no benefit to retaining your old test. The NGS test tests far more data and provides much more reliable matching.

NGS is the great equalizer.

NGS Test Comparison Process

I took my NGS test during the initial R&D development and testing phase, so my original Family Finder test was not upgraded. This afforded me the opportunity to compare the two results.

I downloaded the match files for both of my tests, the original Family Finder and the new NGS Family Finder test, color-coded the background of the cells, not the text inside the cells, and dropped them into a single combined spreadsheet.

It doesn’t matter what colors you choose, but be sure you can easily see the difference. I used apricot for the original Family Finder test matches and light purple for the new NGS test.

As we walk through these results together, you’ll notice that I continue to refer to them by color. In part, that’s so I can maintain my own sanity as I compare results. When I write these types of articles, I have to check and recheck results.

When the same person showed as a match to both tests (meaning they had both an apricot and purple row), I calculated the difference in matching amounts of DNA (cMs) between the match’s results on both tests. I added several calculation columns, which are not shown above.

I’ll tell you, this was not a trivial exercise. It was painful and I really don’t recommend it.

Let’s take a look at the results.

Total Matches

I have some matches with the new NGS test that I do not have with the legacy Family Finder, and I have some matches on the older test that are no longer present on the NGS test.

  Old Family Finder (apricot) NGS Family Finder (purple) Difference
Total Matches 9014 7719 1,295
Maternal 1665 Not linked
Paternal 3783 Not linked
X-Matches 2198 1849 349

I have not yet linked the same matches in my NGS test, so I can’t compare the number of maternal and paternal matches. Fortunately, when you upgrade an existing test, FamilyTreeDNA preserves your linked matches, so you won’t need to relink.

Relationship Estimates

  Old Family Finder (apricot) NGS Family Finder (purple)
1st-2nd cousins, Great/Half Uncle/Aunt/Niece/Nephew, Great-Grandparent/Grandchild 6 6
1st-3rd cousin 1 1
2nd-3rd cousin 5 4
2nd-4th cousin 127 132
3rd-5th cousin 1937 1900
4th to remote 6938 5676
Total 9014 7719

The closest relationships remained the same. One 2nd-3rd cousin moved to the 2nd-4th cousin range by losing 10 cM, 194 cM to 184 cM, but they were apparently on the threshold anyway. That match is actually my second cousin, so both ranges are accurate. It was also a transfer kit, so they did not test at FamilyTreeDNA. This revised match is probably the difference between actual reads and imputed reads in some regions, meaning the match is now more accurate.

275 matches had a predicted relationship change, but not uniformly in one direction, and no one moved more than one category in either direction. This all makes sense.

Match Differences

  Number
Matches found in both the apricot and purple spreadsheets 7,352
Unique (comparable) matches in both spreadsheets 7,174
Matches in original Family Finder apricot only 1,681
Matches in NGS purple only 400

A total of 7,352 matches appear in both spreadsheets, meaning the apricot and purple names matched exactly.

Unfortunately, some people had multiple tests, so I couldn’t always compare apples to apples because they appear three times or more on the combined spreadsheet, and I don’t know which of their kits are which.

If someone with the same exact name had more than one match for either or both tests, I did not compare them because their matching amounts were different, and I didn’t know which one(s) my old test matched, versus which one(s) my new test matched. Usually, one was an upload and one was a test at FamilyTreeDNA, but not always. I excluded those 178 match rows from the analysis.

Therefore, 7,174 matches could be directly compared.

There were 1,681 people who match ONLY on the old Family Finder test, and 400 that match only on the new NGS test. And yes, I downloaded the match files at the same time on the same day, so this comparison was controlled for any time difference.

cM Differences

  Number
Largest apricot match not in purple (NGS) list 26.3 cM
Largest purple (NGS) match not in apricot list 27.63 cM
Largest difference 69.86 cM NGS kit more
NGS detected greater over 10 cMs 19
NGS detected less over 10 cM 7
Total NGS greater 2,924
Total NGS less 3,040
No change 1,090

The largest value difference where a match appeared in the original apricot Family Finder test, and not in the purple NGS test, was 26.3 cMs.

The largest value difference where a match appeared in the NGS purple Family Finder test, and not in the apricot original Family Finder test was 27.63 cMs.

The largest difference between the two tests was 69.86 cMs larger detected by the NGS test. This match was a known second cousin whose matching cMs went from 373.06 to 442.92, but the longest block only increased a negligible amount from 87.47 to 87.69.

The next largest difference was with a 1C1R with a 41.56 cMs difference, also with the NGS-detected value being larger.

In all cases where the number of differing cMs was 16 or greater, the NGS had detected more.

There were very few tests that differed more than 10 cMs. In 19 cases, the NGS test detected a greater difference of 10 cMs or higher, meaning if the original test value was 100 cMs, in the NGS test, it was 110 cMs or greater.

In 7 cases the NGS test detected a smaller difference of 10 cMs or more, meaning that if the original test value was 100 cMs, in the NGS test, it was 90 cMs or smaller.

Out of the 7,174 tests being compared, 19 tests with greater than a 10 cM variation isn’t very many, around 0.26%.

In total, 1,090 matches had no change at all, while 2,924 NGS matches had more matching DNA detected, and 3,160 matches had less.

All but 287 of those differences were less than 5 cMs, and 6778 were less than 1 cM. In other words, literally not worth counting.

myOrigins Ethnicity

We all know to expect changes in our ethnicity from time to time at all vendors. The NGS test is exciting because it covers a much larger portion of our genome. As more people test, the reference library also becomes larger, which means that the ethnicity predictions can and will become more refined too

myOrigins Old Family Finder (apricot) NGS Family Finder (purple)
Central Europe 57% 52%
England, Wales, Scotland 28% 33%
Ireland 15% 14%
Magyar <1% <2%
AmerIndian Andes and Caribbean <1 (see below) N/A
AmerIndian North America <1% (chr 1 & 13) <1 (chr 1 & 2)
Anatolia, Armenia, Mesopotamia, North Africa <1 (chr 13) <1% (chr 10)

None of my major categories changed, but the amounts attributed to each category changed somewhat.

Trace regions, which are less than 1%, shifted some as well, as did their chromosome locations.

For me, this is particularly interesting, because I paint my ethnicity segments at DNAPainter in order to overlay my Native American segments over the matches with whom I’ve identified common ancestors.

Those segments, matches, and ancestors, taken together, help identify the source of the Native American segments.

My Native segment on chromosome one stayed essentially the same, but the Native segment on chromosome 13 is not present on the new NGS test. However, a new Native American segment is now shown on chromosome 2 in the same location that 23andMe also shows a Native American segment.

Chromosome one has already been proven to a Native American ancestor on my mother’s side, but I have hit a brick wall on the chromosome 13 segment. Now, I’ve painted the Native Segment on chromosome 2 and it aligns with the same ancestral line as my Native American segment on chromosome 1.

My Middle Eastern/North African segment still exists, but the location has changed. This segment was adjacent to my Native American segment on chromosome 13 before, on my father’s side, which suggested a history of enslavement. I thought I knew which ancestral line they both descend from, but now I need to review my matches and reconsider.

Unfortunately, my parents are both deceased and there’s no DNA available, so I cannot upgrade their tests or purchase new ones for them. No aunts or uncles are available either. In this case, cousin matches and their associated genealogy on those segments become critically important.

Native American and African American segments are often the best, and sometimes the only hints we have to find and identify those ancestors.

Preparing for Your NGS Results

To be very clear, you don’t necessarily need to compare or prepare, BUT, if you order an upgrade to an existing test, your old match list will be replaced with the new one. Your old match list will not be preserved unless you do it.

What may change?

  • Your ethnicity results will probably change somewhat
  • You will have matches you did not have before
  • Some existing matches, especially at low matching levels, will no longer be there
  • The amount of DNA you share with some people will change

Important: Any notes you have recorded on your matches and any matches that you have linked will be preserved and carried over to your new results when your new test is complete.

If you want to preserve your matches from your earlier test, or your myOrigins results, you’ll need to download your match list, and either download or take screenshots of your ethnicity information.

Ability to Download Tested at FamilyTreeDNA before March 2, 2026 Uploaded and purchased the Unlock Uploaded but did not purchase the Unlock
myOrigins Can download Can download Cannot download
Chromosome Painter (ethnicity) Can download Can download Cannot download
Match list with segment and other information Can download Can download Cannot download
Raw data file Can download Cannot download* Cannot download*

*On tests you uploaded, you don’t need to download the raw data file because you already have it from the originating vendor.

What information is included in your Match List download file?

  • Match name
  • Relationship Range
  • Shared Data cMs
  • Longest Block cMs
  • Linked Relationship (if you linked them in your tree) – this feature is what allows FamilyTreeDNA to assign your matches maternally, paternally or to both sides using triangulation
  • Ancestral Surnames that they’ve entered
  • Y-DNA Haplogroup if applicable
  • mtDNA Haplogroup if applicable
  • Notes
  • Paternal/Maternal or Both side(s) match (if you’ve linked people and this match can be assigned using triangulation. (This is why it’s important to link as many people as possible to their place in your tree.)
  • X-Match cMs
  • Autosomal Transfer yes/no

If you match the same person on the NGS test, this information is preserved for that match.

Where to Download

You must have 2FA (Two-Factor Authentication) enabled for all downloads.

The files you may want to download are found on your dashboard in two locations.

  • Family Finder Matches
  • Chromosome Painter (ethnicity)

Family Finder Matches Download

To download your list of matches with their complete information, click on Family Finder Matches on the dashboard, then on “Export CSV.”

This download provides all the fields mentioned above, whereas the Chromosome Browser segment download provides only your matching segment data, without the additional information.

Download MyOrigins Ethnicity Segment Data

To download your myOrigins ethnicity segments, click on Chromosome Painter on your dashboard, then on “Download Segments.” You can also view or copy those segments by viewing the Detailed Segments tab.

I paint these segments at DNAPainter so that I can correlate my ethnicity regions with my ancestors’ segments.

To assign segments accurately, it helps immensely to have at least one parent’s DNA results too, and preferably both.

You may also want to take a screenshot of your myOrigins map. Note the left-side scroll bar when you’re taking screenshots.

What’s Next?

What else can you do at FamilyTreeDNA to benefit your genealogy?

  • If you haven’t already, upload a GEDCOM file or create a tree at MyHeritage, and link your Family Finder test to your results.
  • Link your individual matches to their place in your tree. This allows FamilyTreeDNA to use segments triangulated with linked matches to assign other matches to either the maternal or paternal side of your tree, or both.
  • Add your line to WikiTree. It’s easy. Begin with yourself and add ancestors until you connect with someone who is already in WikiTree. For me, it was the grandparent level.
  • Add your WikiTree link to your FamilyTreeDNA account under the gear in the upper right-hand corner, then Genealogy, then Family Tree. This gives your matches an easy way to identify common ancestors by using WikiTree’s Find Relationships feature, and provides two types of tree resources for you and your matches – MyHeritage and WikiTree.
  • Make sure your Earliest Known Ancestor information is correct and up-to-date with your most recent research, including a specific map location. You’ll find that under the gear too, then Genealogy, then Earliest Known Ancestors.
  • Add your surname list to your profile under the gear, Genealogy, Surnames tab.
  • Use the Matrix tool at FamilyTreeDNA to see how much DNA your shared matches share with each other.
  • Y-DNA – If you’re a male, test your Y-DNA, which is your father’s direct paternal line. The Big Y-700 test provides you with matches and the most detailed information possible.
  • mtDNA – Everyone can take a mitochondrial DNA test, which shows matches and provides information about your mother’s direct matrilineal line.
  • Use Advanced Matching, found under Additional Tests and Tools on your dashboard page, near the bottom, which allows you to select from multiple tests to see who matches you on both types of tests. For example, those who match you on both your full sequence mtDNA test and your Family Finder test.
  • Join projects relevant to your family surname, geography or broader interests. You’ll find Group Projects in the top banner of your dashboard page after signing in.
  • Utilize the Discover tools for both Y-DNA and mitochondrial DNA results.

Check your matches often to see who is new and what might have changed as people upgrade to the new NGS test and more people test.

_____________________________________________________________

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

Mitotree: First, the Tree – Now the Paper

It’s definitely a red-letter day.

Dr. Paul Maier, the lead author on the new paper Mitotree: The Universal Human Mitochondrial Reference Phylogeny at 10x the Resolution has uploaded the paper to the bioRxiv preprint server, here.

I want to congratulate all of the authors, most of whom are members of the FamilyTreeDNA R&D team as either employees or contractors. I’m a contractor and have had the honor of working with these amazing colleagues on this project since 2020.

About Mitotree

Mitotree was officially “born” on February 25, 2025, and the tree has been updated several times since. About 75% of FamilyTreeDNA’s customers who have taken the full-sequence mitochondrial DNA test received a more refined haplogroup with the release of Mitotree or subsequent updates. Those haplogroups are, on average, 2000 years newer than the person’s legacy Phylotree haplogroup, and some are much more recent.

This means that the tree branches have gotten much, much bushier close to the tips. In other words, lots more twigs and leaves!

Unfortunately, about 25% of testers did not receive a new haplogroup because they do not have any qualifying mutations:

  • Either because they have no additional mutations
  • Or because they have mutations, but they are unstable
  • Or because they have mutations, but no other testers have yet tested that match them to split a branch

The good news is that with the addition of haplotype clusters, everyone benefits from new matching and grouping tools. Testers are grouped into clusters on their matches page, and on the Match Time Tree in Discover, which is much more useful for genealogy.

I know this paper has been a long time coming, but it’s well worth the wait.

Mitotree was a massive undertaking. We began with PhyloTree v17 which had 5,438 hand-curated branches constructed from 24,275 full and partial mitochondrial sequences. Phylotree was last updated in 2016 before subsequently being abandoned.

The Million Mito Team developed Mitotree, a robust phylogeny with more than 54,000 branches formed from over 330,000 complete mitochondrial sequences, of which 177,196 are unique sequences.

Let’s Look Under the Hood

There are three critical pieces of information in those statements.

First, the PhyloTree curation and maintenance was not automated, and a paper detailing their build process, what mutations were included or excluded, and under what circumstances was never published.

Approximately once a year, a new PhyloTree was published where newer samples were individually evaluated and new haplogroups were hand-grafted onto an existing backbone tree.

This methodology did not allow for deep splits to become apparent, because the tree itself was never recalculated. This is exactly how haplogroup L7 went undetected until the Million Mito Team recalculated the tree, including the backbone, in 2022, and published this paper about L7’s discovery.

In other words, while PhyloTree was publicly available, there was no recipe for how it was created or maintained.

Clearly, the tree-building process had to be automated, as hand-curation was unsustainable. There were no academic programs in existence capable of handling the number of samples involved. Not even in 2016 for fewer than 25,000 samples, let alone today.

To maintain haplogroup naming consistency, the first thing our team had to do was write software to phylogenetically reverse engineer PhyloTree v17 to establish a common foundation on which to build. This step was essential for consistency and maintaining the established haplogroup naming pattern.

That software also had to be capable of scaling up exponentially. The first versions took weeks to run, which clearly wasn’t an acceptable long-term solution. Still, being able to establish a foundational backbone to build on programmatically was a victory in and of itself.

Second, PhyloTree used partial sequences, meaning HVR1 and HVR2 samples. Early academic researchers did not perform full sequence testing, so the curators of PhyloTree used what was available to the best of their ability.

With over 330,000 full-sequence samples available today, we no longer include partial samples.

Third, 177,196 of the 331,221 full sequence samples used were unique. Before launching the program to construct the tree, identical samples from known immediate relatives are deduped, when possible, in order to reduce unnecessary clutter and processing time.

This means two things. The actual number of testers is greater than 331,000. But more importantly, anyone who thinks that mitochondrial DNA isn’t interesting should take another look. More than half of the sequences used for tree-building are unique, which handily dispels the myth that mitochondrial DNA doesn’t mutate often enough to be useful for genealogy.

The Mitotree initiative has been both scientifically and genealogically successful beyond anything we could have imagined. The base tree includes approximately 180 branches that are older than 30,000 years, including the discovery of haplogroup L7 at 100,000 years old. These branches both expand and more firmly root the oldest portions of the tree.

Amazingly, haplogroup L7 has living descendants whose earliest known family members are found in Turkey, Saudi Arabia, Yemen, the UAE, Palestinian Territory, Ethiopia, Sudan, and South Africa.

Another fun discovery involved Otzi, the Iceman, a mummy found frozen in the Italian Alps who lived more than 5,000 years ago. He was thought to carry an extinct haplogroup, K1ö, named in his honor, but as it turns out, he’s actually a member of haplogroup K1f, a clade with living descendants in Algeria. Additionally, Otzi now matches four ancient burials too, so he does have cousins.

We couldn’t have made these discoveries without the right people testing, so please encourage everyone and dispel the discouraging myth that mitochondrial DNA isn’t useful or interesting. It absolutely IS, and the success stories keep rolling in!

Why Build a Phylogenetic Tree?

Simply put, the history of our ancestors, both recently and reaching back into ancient history, is revealed in the tree – and there’s absolutely no other avenue to reach this information. Ironically, it’s readily available to everyone because everyone has mitochondrial DNA and can easily take the test.

Mitochondrial DNA is different than Y-DNA, which has its own phylogenetic tree based on SNP mutations, and autosomal DNA, which has no tree.

The reason that both Y-DNA and mitochondrial DNA can have phylogenetic trees is that they are inherited from the appropriate parent with only occasional mutations, while autosomal DNA is roughly halved in each generation.

Y-DNA is inherited by males only from their fathers, with no admixture from their mother, while mitochondrial DNA is inherited by everyone from only their mothers, with no admixture from their father.

Autosomal DNA is inherited through random recombination, with half coming from each parent, except for the X chromosome which has its own inheritance pattern. X-DNA is often confused with mitochondrial DNA, but they are entirely different types of DNA. I wrote about that here.

No tree is possible for autosomal DNA, because it gets diced and riced in each generation.

The mutations that occur occasionally and randomly in both Y and mitochondrial DNA form a trail of breadcrumbs leading backward in time, or in our case, they form both the trunk and branches on the tree.

Those unique mutations, once they occur, are inherited by subsequent generations, forming a path back in time.

In current generations, those mutations provide testers with the ability to identify our closest cousins who inherited those same mutations and who have taken either a Big Y-700 test, in males, or a mitochondrial DNA full sequence test for everyone.

In this conceptual example, you can see that Ancestor 1 carries mutation A, as do the next two generations who inherited it from their parent. However, Ancestor 4 now has additional mutation B, so that person carries mutations A+B. This inheritance pattern continues through the apricol lineage as mutations C and D are added in subsequent generations, until “You” are born with A+B+C+D.

Your cousin’s ancestor, on the other hand, was also born to Ancestor 4 and carries both A+B, as seen in the green column. Three generations later, that line added mutation F. Your  ancestor 7 added mutation C, so now the apricot and green lineages can easily be genetically distinguished from each other.

When a living person tests, we immediately know, based on the combination of their mutations, if and where they fit in this lineage, because both the apricot and green branches have accumulated unique mutations that the original blue Ancestor 4 and earlier ancestors did not have.

Using our knowledge of the tree branches, when and where they occurred, provides valuable genealogical information, along with fascinating Ancient Connections, both since and prior to the adoption of surnames.

Both Y-DNA and mitochondrial DNA can reach much further back in time than autosomal DNA because they are not diluted with DNA from the other parent in each generation.

So mitochondrial DNA is both broad, meaning many leaves, and deep, meaning it helps us look straight back in time like a laser sight, all the way to the common ancestor of all humanity, Mitochondrial Eve, who lived about 140,000 years ago in Africa.

Mitochondrial DNA Presents Unique Challenges

Mitochondrial DNA presents challenges not found in Y-DNA tree building.

For example, mitochondrial DNA only has 16,569 locations available to utilize, while Y-DNA currently uses roughly 22 million “gold standard” locations on the Y chromosome.

Of those 16,569 mitochondrial locations, some are not reliable enough for tree-building.

Unreliable mutations include:

  • Insertions, where extra copies of a particular nucleotide (Thymine, Adenine, Cytosine and Guanine) have been inserted at a specific location. Those are indicated by designations such as 309.1C where 309 indicates the marker location, .1 indicates the number of insertions at that location, and C (for Cytosine in this example) indicates the nucleotide inserted.
  • Heteroplasmies occur when multiple nucleotides are detected at a specific location. They are reported by a different letter than T, A, C or G, depending on which of multiple nucleotides are found. Heteroplasmies tend to “come and go” based on detection and threshold levels, so they can’t be used the same way as more stable mutations for tree building – and are often, but not always, unreliable for genealogy. I wrote about this in the article, What is a Heteroplasmy and Why Do I Care?.

Those locations and types of mutations have been excluded from forming tree branches, or downweighted, because they are too prone to mutating back and forth. However, they *might* be useful for genealogical purposes. Less-than-reliable mutations are now used to create haplotype clusters, even though they aren’t used to create new branches on the Mitotree.

I wrote about how haplogroups and haplotype clusters are formed in these articles:

Weighting and Confidence Factors

Mitotree formation would have been a lot easier if delineations, meaning inclusions and exclusions, were clear, either yes or no, but they aren’t.

Some were obvious from the get-go, such as insertions at location 309 and elsewhere, but other situations were much less obvious.

For example, sometimes there’s a specific location that seems prone to reversion, mutating back and forth, meaning that it mutates, then returns to its original state, then repeats the process.

Reversions are a natural phenomenon that occurs frequently in mitochondrial DNA, but is rarely, if ever, found in Y-DNA.

Let’s look at an example.

Courtesy Dr. Paul Maier

How many reversions at the same location are too many, especially if they are close in the tree?

In the above example, the mutation from A to G occurs just below the first arrow, forming haplogroup L1, a branch of L. The red areas all carry that mutation, subsequently forming eight new branches.

However, one step downstream from that mutation, just above the second arrow, location 7055 back-mutates, or reverts to A from G, which is indicated by the “!”. That reverse mutation forms haplogroup L1c3.

If location 7055 continues to flip back and forth between A and G, at what point do we have less confidence in that location, and at what point should a location be excluded from the tree and prevented from creating or dividing a branch?

The answer is that “it depends,” sometimes on the branch, sometimes on the “group” of other mutations it’s found with, and other factors. Some locations are stable in some parts of the tree, but unstable in others. We certainly never expected to see that!

This means the team had to design and build a weighting methodology so that relevant mutations, such as reversions, are not summarily excluded from tree building but instead carry different confidence weighting levels, depending on the circumstances.

Some samples, such as ancient DNA, were down-weighted in general due to their propensity to contain artifacts resulting from deterioration. Ancient samples can still influence branching, just not as much as a high-quality modern sample.

Furthermore, especially when utilizing academic samples, results with a high number of heteroplasmies are excluded, along with those with ambiguous reads and missing upstream mutations, which were previously inferred with PhyloTree. Academic samples vary in quality and age, and we have no way of knowing which quality criteria were used by that lab at that time.

These types of variances made constructing and updating the Mitotree more challenging than the Y-DNA tree, which is not subject to weighting, resulting from phylogenetic tug-of-war between mutations.

In some situations, the addition of just one test can make the difference between a new branch, or no branch, in a subsequent run of the tree. Due to this type of scenario, and fine-tuning the algorithm, some people’s new haplogroups have reverted to an earlier haplogroup in subsequent Mitotree updates.

The paper and supplemental materials provide details about the exclusion process, types of exclusions, and a list of excluded marker locations.

You can view the confidence of any haplogroup in the Classic Mitotree view in Discover.

My haplogroup, J1c2f, is formed by the mutation G9055A, and you can see that the confidence rank is 7.5 out of 10.

Mousing over the little up-arrow tree icon beside the star explains changes in nearby branches, which can affect the haplogroup’s confidence ranking.

Branches are not renamed for convenience, and only when phylogenetically warranted. Existing haplogroup names used either on PhyloTree, in academic literature, or previously on the Y-Full tree are either maintained or avoided to eliminate potential confusion. No one wants two different haplogroup names depending on which tree is being viewed.

Previously obsoleted names remain permanently obsoleted and are not reused.

The paper explains further about technical corrections and tie-breaker situations. In some cases, potential branches with equal or near-equal weighting are flagged for team review.

Amazing Discoveries

I encourage everyone to read the section in the paper beginning with “Notable discoveries.” These aren’t people, as in Discover’s Notable Connections, but scientific accomplishments achieved with the new Mitotree.

Our knowledge of human migration within and out of Africa has been greatly refined, as well as the ancestral path into and across Eurasia, Asia, and into the Pacific Rim. If you have unusual mitochondrial haplogroups such as L, M, N, P, Q, R or S, you’ll absolutely want to read this.

Of course, in time these haplogroups branch and become Paleolithic haplogroups, then the Gravettian-Mesolithic followed by the Hunter-Gatherers found throughout Europe that we are familiar with. We’ve learned a great deal from rare ancient DNA samples that anchor more modern haplogroups in a place and time, and inform us of migration patterns as well as how now-extinct ghost populations gave rise to current ones.

The earliest humans, whom Mitotree has more firmly anchored, formed a trickle out of Africa that became a bifurcated stream, eventually flowing across the rest of the world. What recorded and even archaeological history cannot tell us can be and is revealed through the patterns held in our DNA today – and Mitotree is our map to read them. Common ancestors are found where our mutations as haplogroups converge, joining as we travel backward in time, piercing an otherwise impenetrable veil.

For those with Native American ancestry, Mitotree expands the two-wave theory, refining it into five or six probable migration surges, depending on how you count, based on a combination of haplogroup ages and distribution.

Summarizing from the paper:

The first wave of haplogroups A2, B2, C1b, C1c, C1d, D1, and D4h3a arrived from Asia, across Beringia or along the Pacific Corridor, about 17,000 to 18,500 years ago, and expanded along the Pacific coast. D4h3a is found almost exclusively in the Pacific region.

This was followed by haplogroup C4c about 15,800 years ago and X2a about 10,000 years ago, which expanded into the interior through the ice-free corridor east of the Rockies after the ice melted.

Next were the Paleo-Eskimo and Na-Dene speakers in haplogroups A2a, D2a, D2b, D2c/D3, and D4b1a2a1a2, who, between 3000 and 7000 years ago, made their way from Alaska, across the polar regions of Canada, into Greenland.

Na-Dene speakers, Apache and Navajo, in haplogroups A2a and B2a made their way southwest between 1300 and 1500 CE, or between 500 and 700 years ago.

Last, the present-day Inuit-Yupik expanded from Beringia to Greenland about 1000 CE.

For additional information, please see the Native American lineages section of the paper.

Mitotree has also clarified the ancestors of the Ainu/Jomon people from Hokkaido, Japan, and their ancient Paleolithic northwest Asian and Siberian relatives. The ancestors of this group and Native Americans share even earlier Asian ancestors.

The history of the Jewish people has been significantly refined as well, expanding on earlier works, and is found in the Counting the newest Jewish founders section of the paper.

  • 43% of Ashkenazi Jewish testers fell into 5 founding lineages where they had no subclades before, but they do now.
  • Two clades of haplogroup K have now been split 4000 to 5000 years ago in Romania.
  • There’s new information about the crypto-Jewish community in Portugal, Mountain Jews from Persia and the Caucasus, plus Jewish groups in India, Georgia, Azerbaijan, Israel and Libya.
  • Additionally, haplogroup M33c9b tells the story of Ashkenazi Silk Road merchants who traveled between China and Europe.

The paper reports the isolation of Sardinian-specific haplogroups and provides substantially greater structural definition for the Saami people, increasing from 22 subclades to more than 300.

The Notable discoveries section is chock full of information.

Genealogy Jump-Start

Today’s tree is ten times larger than the 2016 tree, and will continue to grow as more people take a full sequence mitochondrial DNA test, available at FamilyTreeDNA.

The greatly improved tree alone is not the only facilitator of genealogical success. A dozen reports, including Haplotype Clusters and the Match Time Tree are provided for all full-sequence testers in Discover. I wrote about how to effectively use your matches and Discover to break through genealogy brick walls, here.

There are a couple of things you need to do to increase your opportunities for success and to help Discover and Mitotree.

Genealogy is a team sport, and you can increase everyone’s success rate by completing (and updating) your Earliest Known Ancestor (EKA) and location information, found under “Account Settings” beneath your name in the upper right hand corner when signed on, then “Genealogy”, then “Earliest Known Ancestor”, and by providing a family tree or a link to WikiTree.

Identifying common ancestors is what testing is all about, and these are all important success factors. Everyone wants to identify previously unknown ancestors.

Mitotree is More Than Genealogy

Of course, as genealogists, we’re focused on how to use the new Mitotree information, paired with Discover, to identify brick-walled ancestors and learn more about them. I’ve written specifically about how to do that in these two articles:

Mitotree isn’t just an explosion for genealogy, though – it’s an incredible scientific achievement. Instead of genealogy benefiting from other specialties, now they can benefit from what genealogy has wrought.

Mitotree presents opportunities to rethink and potentially recalculate dating and information in other fields, such as archaeology, medical genetics, forensics, and history.

We know vastly more than ever before, but this is only the beginning.

With each new tester and every ancient genome added to the growing body of evidence, our understanding becomes more refined, revealing insights about our ancestors, and weaving our thread into the broader tapestry of human history.

_____________________________________________________________

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

Sixteen Unique Trees at FamilyTreeDNA: How and When to Use Each

I love all the various trees at FamilyTreeDNA – and I’m not referring just to traditional genealogy trees with people, names, and dates. I’m talking about phylogenetic or haplogroup trees – the ones you use to understand your Y-DNA and mitochondrial DNA haplogroups, origins – and more. These trees tell you ABOUT your ancestors, those people in the more traditional genealogy tree, and the combination of both is powerful.

This article introduces the various trees available at FamilyTreeDNA, when and where you’ll find them, and what they can do for you.

Haplogroup Trees

Phylogenetic, or haplogroup trees, provide a genetic path from you, or the tester, today, back in time to Y-Line Adam, or Mitochondrial Eve – the first two humans who lived AND have descendants today.

Let’s start by explaining about Y-DNA and mitochondrial DNA (mtDNA), their inheritance path, and what they mean to you.

Y-DNA

Only men have a Y-chromosome, so only biological males can test their Y-DNA.

Y-Line Adam, Y-DNA haplogroup A-PR2921, lived about 232,000 BCE, or 234,000 years ago.

Is it possible that one day someone will test whose results push that date back somewhat? Yes, of course, as we are always learning, and many testers split branches.

Today, all 711,000+ modern descendants who have tested carry the mutation named A-PR2921 as their oldest SNP (single nucleotide polymorphism), or haplogroup-defining mutation in their Y-DNA. That’s because we all descend from that one man.

If you’re a male, Y-DNA testing tells you about your direct paternal line by matching with other men who have also taken a Y-DNA test, and by revealing valuable information from before the adoption of surnames. There’s no other way to reach that far back in time.

If you’re a female, you can recruit males in your family to test.

The Big Y-700 test provides the deepest-reaching and most refined Y-DNA test available, which is essential for both genealogy and tree-building.

Mitochondrial DNA

All people have mitochondrial DNA, inherited from their mother directly through her matrilineal line – meaning her mother, her mother, her mother, and so forth – directly up your tree through all mothers.

Everyone inherits their mitochondrial DNA (mtDNA) from their mother, but only females pass it on. Both males and females in the current generation, meaning you, can (and should) test their mitochondrial DNA.

Mitochondrial Eve, mitochondrial DNA haplogroup L, lived about 141,000 BCE, or about 143,000 years ago. All 315,000 testers descend from this one woman.

Like with Y-Line Adam, one day the results of future testers may push this date further back in time. A full sequence mitochondrial DNA test, mtFull, is necessary to test all 16,569 mitochondrial locations.

Test Types

FamilyTreeDNA has been in business for more than 25 years. Technology has advanced dramatically during that time. While they continue to offer new tests and products, they strive to maintain value for their original testers.

Even though some early testers may have joined their ancestors, matching with their test results is still beneficial to us.

Present-day DNA testers can still derive value by matching the earlier, lower-level, lower-resolution tests. Not as much value as if the original tester had taken a higher-level test, but those tests may not have been available at that time.

Matches, surnames, genealogy, locations, and haplogroups provide us with valuable information. The more people who test, the larger the pool becomes, and the better our chances of discovering something that refines our understanding of our ancestors – and identifies who they are.

Before we look at the trees available, let’s take a look at where haplogroups come from. Different level tests assign different levels of haplogroups, based on how much is tested.

Let’s answer two common questions:

  1. Where can you find your haplogroup, and what does it mean?
  2. How can haplogroups be different for people who descend from the same ancestor?

Where Do Haplogroups Come From?

Since the beginning, FamilyTreeDNA has always provided their customers with haplogroup information. Haplogroups are very genealogically useful today, but initially, 25 years ago, they were only able to provide essentially continental-level origin information for your particular line. That too was useful, and helped to identify and eliminate common lineages – just not as useful as today.

Science and testing have both come a long way. Present-day testers still match with people who only tested at a lower level. You never know what you might find at that level – a match to someone who has not taken the current tests, but is still very relevant because they share your ancestor. In fact, they may be the only tester who does.

For Y-DNA testers, you’ll notice several match categories that reflect different testing levels – along with the number of matches at each level. At one time, you could purchase each one of these tests individually, then later upgrade to higher-level tests. Today, only the 37 and 111 marker tests, and the Big Y-700, which scans the entire gold-standard region of the Y chromosome, are available. Higher level tests include the lower-level tests.

Click any image to enlarge

Different types of tests provide either a predicted or a confirmed haplogroup which shows on your match list.

Without getting all sciency on you – the 12-111 marker tests test targeted STRs, or short tandem repeats, which can’t be used for haplogroup assignment and confirmation. They can and are used to compare to other testers for matching because the number of repeats, or stutters, are inherited on the Y chromosome. The Big Y test scans the Y chromosome for SNPs, single nucleotide polymorphisms, which are stable mutations that define haplogroups. I wrote about this in the article, STRs vs SNPs, Multiple DNA Personalities.

Some haplogroups are much further down the tree, or more current, than others. Your most current haplogroup, only available with the Big Y-700 test, is the best because it brings you the closest to current in time, often placing you within family branches. The Big Y-700 scans about 23 million locations on the Y chromosome, revealing both known and unknown mutations, not just a few markers, making it the most refined and relevant test genealogically.

Each higher-level test includes the lower-level tests. You can see what tests your matches have taken by looking beneath their names on your match list. In this case, these Estes men who match my cousin have taken the Family Finder (or uploaded an autosomal transfer), and taken the mtFull test. One match initially took the Big Y-500 but has since upgraded to the Big Y-700, and the other originally tested at the 111 marker level, and has since upgraded as well.

The Big Y-700 includes all lower-level tests, such as the Big Y-500 (now obsolete), the 111, 67, 37, 25, and 12 marker STR tests. You still match with people who only tested at those levels, plus everyone else who ordered a more refined test.

The haplogroup you receive is more or less refined, based on the test level you take.

Y-DNA Test Type Haplogroup Provided Relevance Upgradable
Y-DNA STR 12-111 marker tests (only 37 and 111 are available today – the rest are obsolete) Predicted based on STRs – very reliable at the level predicted Predicted (not confirmed) haplogroup that was generally formed a couple thousand years ago, or earlier Yes, if enough quality DNA remains. Only 37, 111, and the Big Y-700 tests are available today. Recommend the upgrade to Big Y-700.
Individual SNP test (now obsolete) Confirms a predicted haplogroup or tests a single SNP to confirm a closer haplogroup Relevant at the level tested – either positive or negative result was reported Individual SNP tests have now been replaced by Big Y-700, which covers all individual SNPs that were available to test, plus much more.
Big Y-500 test (now obsolete) Confirmed haplogroup within range of that test’s ability, replaced by much more granular Big Y-700 Big Y-700 is more refined and moves the tester towards more current haplogroups, so more genealogically significant Yes, upgrade to Big Y-700 if enough DNA remains, or tester can re-swab
Big Y-700 – scans the entire gold-standard region of the Y chromosome – approximately 23 million base pairs Top-of-the-line SNP-confirmed test, most granular and refined. Scans for known and previously unknown mutations. Extremely accurate. Generally advances the tester into a genealogical timeframe, and often divides testers into multiple lineages descended from a known common ancestor No more advanced test is available.
Family Finder autosomal test or transfer Confirmed to mid-range level if possible. Not all transfer files have Y-DNA or mtDNA SNPs so you get what you get. Useful in autosomal matching for locating people you may be related to you with that surname. Ask the match if they are willing to take a Y-DNA test, if relevant, or sponsor a testing scholarship for them.

Family Finder haplogroups are relatively new at FamilyTreeDNA. Each chip level that FamilyTreeDNA has used for testing over the years, and the chips that other vendors have used, contain different SNPs (or none at all on the Ancestry test) that can be measured for some level of haplogroup. Other vendors generally don’t quality-control for either Y-DNA or mtDNA SNPs because they don’t use them. This is a “you get what you get” freebie.

That said, most Family Finder haplogroups are closer in time, or “better” than the predicted R-M269, the most common haplogroup in Europe, often reported with STR testing.

Not everyone with a transfer kit receives a haplogroup. Due to quality and reliability issues, you cannot see haplogroups on your autosomal match list for those who only have a haplogroup through an autosomal transfer.

Using our male Estes testers as an example, we find the following haplogroup results at the various testing levels:

Haplogroup Haplogroup Formation Date Ancestor or Haplogroup Formation Location Haplogroup Source
R-M269 4450 BCE (6450 years ago) Between Ukraine and Kazakhstan, north of the Black and Caspian Seas Predicted from 12-111 STR marker tests
R-BY487 700 CE (1300 years ago) UK, Scotland/England Family Finder DNA SNP Confirmed
R-BY482 1550 CE Robert Eastye b 1555 Ringwould, Kent, England Big Y-700
R-BY490 1700 CE Silvester Eastye b 1596 Kent, England Big Y-700
R-ZS3700 1750 CE Moses Estes 1711 VA Big Y-700
R-BY154784 1850 CE Joseph Estes b c 1790 VA or TN Big Y-700

All of these are valid and accurate haplogroups – some are just closer in time and much more useful than others. All of these men have R-M269, because it is a parent haplogroup of all of those downstream haplogroups. The Big-Y tested men beginning with R-BY482 don’t share the haplogroups below them, because they don’t have those mutations that are downstream on the tree. However, the men at the bottom with R-BY154784 have all of the SNPs above them.

Note that all haplogroup formation dates are ranges. I’m showing the midpoint here.

When upgrading, if the original tester is deceased, select the highest-level test available, as there may not be enough DNA to run more than one test. When I offer scholarships now, I always just offer the Big Y-700 test to avoid future issues.

If the tester you need is no longer available, consider the possibility that other people, family members perhaps, might be available to test to represent this same line.

Next, let’s look at mitochondrial test levels and haplogroups.

Mitochondrial DNA Test Type Haplogroup Provided Relevance Upgradable
HVR1 & HVR2 tests (no longer available) Predicted based on around 1000 markers – very reliable at the level predicted Predicted haplogroup, not confirmed, generally formed a couple thousand years ago or earlier Yes, if enough quality DNA remains. Only the mtFull test is available today.
mtFull, full sequence test Tests all 16,569 SNP locations in the entire mitochondria. Most granular and refined. Extremely accurate. Often brings tester into genealogical timeframe, especially with the new Mitotree. Divides testers into multiple haplotype lineages, sometimes descended from known common ancestor. No upgrade needed to receive new Mitotree and mtDNA Discover benefits.
Family Finder autosomal test or transfer Coming soon. Will be the same criteria and caveats as Y-DNA SNPs. May be able to find a similar or upstream haplogroup that might point to a common ancestor. Ask autosomal match if they are willing to take a mtFull test, if relevant, or sponsor a scholarship for them.

Ok, now that we understand more about haplogroups, how they are determined, and where yours came from, let’s look at all of the trees at FamilyTreeDNA.

Trees Within Your Y-DNA and Mitochondrial DNA Account

Let’s start with trees found within your personal account, so sign in.

Each tree has a different purpose and unique benefits.

Tree #1 – Your Matches Genealogy Trees

Each of your matches may have provided links to genealogical trees. They may show trees in multiple places too; at MyHeritage, an archived tree at FamilyTreeDNA, and a WikiTree link. I makes notes about their trees in the comments field, and I also keep a spreadsheet to look for commonalities.

Tree #2 – Haplogroups and SNPs for Y-DNA Testers

Next, for Y-DNA testers, click on the Y-DNA Results and Tools.

You’ll see the Haplotree & SNPs tile on the dashboard.

The Haplotree and SNPs link takes you to a phylogenetic tree that defaults to your haplogroup, where you can view:

  • Variants – SNP mutations that define your haplogroup
  • Surnames with this haplogroup – so long as there are multiple public testers
  • Countries – self-reported for earliest known ancestors (EKA)
  • Recommended Projects – haplogroup projects only – others such as surname projects are found in Discover under Suggested Projects

Tree #3 – The Block Tree for Big Y Testers

People who have taken the Big Y-700 test have a separate section that includes tools for the Big-Y test that aren’t relevant for the 12-111 STR marker tests.

Big Y testers will see the Block Tree tile on their dashboard.

The block tree is an alternative way of displaying matches on a phylogenetic tree. While the Discover Time Tree is viewed left to right, this tree is displayed top to bottom, with each mutation being represented by one grey bar on the scale at left. Each mutation corresponds to approximately 100 years, which is a rough average for the frequency of Y-chromosomal mutations.

People with 30 mutations or fewer are shown as matches, with the goal of reaching back about 1500 years.

Each large block shows the mutation for which the haplogroup is named, such as R-BY482, at the top. The mutations, known as variants, shown below that haplogroup name, are found in the results of each person in that haplogroup, but in the future, people without those mutations, or with additional mutations, will form a new branching haplogroup.

The green “Private Variants” at the bottom of the branches display the average number of mutations of people within that group awaiting another tester to have the same mutations, so a new branch can be formed. I view Private Mutations as “haplogroups in waiting.”

Discover

In addition to the haplogroup trees shown in your account at FamilyTreeDNA, there are several additional trees in Discover for both Y-DNA and mitochondrial DNA. Discover, updated weekly, is a suite of tools for both Y-DNA and mitochondrial DNA that, cumulatively, provides a book about your haplogroup results.

Discover comes in two flavors:

  • The publicly available free version with limited functionality
  • Your private version with expanded functionality available from within your account

You can access Discover, here if you’d like to follow along.

Discover is a publicly available free tool introduced in the fall of 2023 that provides more than a dozen reports, enabling a deeper understanding of all haplogroups.

Just select Y-DNA or mtDNA and enter your haplogroup of choice.

Think of these menu choices, in the sidebar, as chapters in your personal book. Every chapter has something interesting to tell you. Please read them – don’t just scan.

In addition to the free version, if you have taken a Big-Y or mitochondrial DNA full sequence test at FamilyTreeDNA, you’ll have additional information available.

For mitochondrial DNA results, just click on the pink Discover tile.

For Y-DNA results, click on the blue Discover tile.

Within Discover, you’ll find three distinct trees.

Trees #4 and #5 – Y-DNA and Mitochondrial DNA Time Trees

The Time Tree shows your Y-DNA or mitochondrial DNA haplogroup displayed on a timeline, along with:

  • A self-reported ancestral country indicator for every person’s DNA in that haplogroup
  • Haplotype groupings indicating exact matches between everyone in that haplotype.

A haplotype is a grouping of people whose DNA matches exactly, including unstable or hypervariable locations too unreliable to use for haplogroup formation. However, those mutations may be relevant for genealogical matching.

I wrote about haplogroups and haplotypes here and here.

Tree #6 and #7 – Y-DNA and Mitochondrial DNA Class Tree View

The Classic Tree is available for both Y-DNA and mitochondrial DNA.

On the Classic Mitotree View, you can display and filter the tree, including haplotypes, in seven ways, as shown in the dropdown “Display Options.”

Tree #8 and #9 – Y-DNA and Mitochondrial DNA Tree Branch Comparison

Have you ever seen two haplogroups and wondered how closely they are related? Compare provides that answer.

Here, I’m comparing my haplogroup to that of a family member. Everyone is related, but how long ago are we related on our matrilineal lines?

Haplogroup J1c2f compared with haplogroup V216a shows that our common ancestor lived a VERY long time ago – about 55,000 years in the past, someplace in the fertile crescent.

For either Y-DNA or mitochondrial DNA, you can compare two haplogroups. This provides specific information about those two branches of the tree, and where they intersect. To view more about the common ancestor, just pop R+10398 into Discover and learn more about when and where that ancestor lived.

Trees #10 and #11 – Match Time Trees

Match Time Trees are one of the most useful Discover features.

In addition to the Time Trees and Classic Trees provided for everyone in Discover, test takers will also have a Match Time Tree that shows all of your matches, organized genetically.

For mtFull testers, your matches are organized by haplotype cluster. People in your haplotype cluster are your exact matches.

I have over 100 full sequence matches, so I’m only showing the first few in this screenshot. In addition to the match’s name, their EKA (earliest known ancestor) is shown, if provided.

On the Y-DNA Match Time Tree, links are provided to genealogical trees of the tester, which could be an archived FamilyTreeDNA tree, a MyHeritage tree, WikiTree, or some combination.

You can actually see your matches’ WikiTree tree on your Match Time Tree by enabling another feature.

Trees #12 and #13 – WikiTree Tree Integration

While you’re still on the Match Time Tree page for either Y-DNA or mitochondrial DNA, click on Display Options, above the Time Tree, and enable WikiTree Connections. Unfortunately, the default for this great feature is “off.”

I’ve enabled “Share Mode” at the top to obfuscate the names of the testers, and I’ve adjusted the vertical spacing so you can see more in my examples. You’ll notice the grey lines with dots inside circles. I think of these as beads or maybe knots on a rope, but they actually represent a line of ancestors.

Each tester with one of those grey dot bars has connected themselves to their ancestors at WikiTree, a public one-world tree. Living people are not shown, hence the dash marks to the immediate left of the tester’s name.

By mousing over any of the dots, aka ancestors, you can view information about this ancestor of this Estes tester at WikiTree. Ancestors appear in genealogical order in their relevant place on the Time Tree. How cool is that!!!

WikiTree, like any tree, public or private, can have errors. Always verify any tree using original source documents.

As far as I’m concerned, the Match Time Tree is one of the very best features of both Y-DNA and mitochondrial DNA testing and matching. There are so many options to select from, so take some time to look around.

Your Personal Version of Discover is Best

Y-DNA Discover and mtDNA Discover can both be useful for any level of haplogroup, but the best results are obtained when clicking through from the tester’s FamilyTreeDNA account. Big Y and full sequence mitochondrial DNA customers receive additional information, not available in the free, public version of Discover, including

  • The Match Time Tree
    • Including WikiTree integration
  • Globetrekker™ (Y-DNA, mtDNA coming eventually)
  • Up to 30 Ancient Connections, as compared to 3 in the free version
  • Up to 30 Notable Connections, as compared to 3 in the free version

 

Tree #14 – Group Time Trees

I absolutely love Group Time Trees. They are similar to Match Time Trees, but unlike Match Time Trees, are publicly viewable for Group Projects if the volunteer project administrators have enabled this feature for the project.

There are two ways to access Group Time Trees – through publicly accessible Discover or directly through any project.

In Discover, select Group Project in the dropdown.

Then type the name of the surname project you’re seeking. You’ll be presented with a menu if the surname you’ve entered is found in multiple projects, or administrators have listed it as “of interest” in their project.

I clicked on the Estes project.

Viewing the Estes DNA Project, under DNA Results, you can see the various options.

Selecting Y-DNA Results Overview displays the project results by administrator-defined group. The teal groups all descend through Abraham Estes through various sons.

However, by clicking the Group Time Tree instead, you can view all these testers and their results in a Match Time Tree format, arranged genetically.

Clicking on the Group Time Tree link takes you to the Group Time Tree for this project. A menu is displayed at left, based on how the administrator has grouped the project.

I’ve selected several groups that I know descend from the original Estes ancestor from Kent, England. Testers who have joined the Estes project and granted permission for their results to be displayed publicly are automatically grouped genetically, at right, with their surname and EKA (earliest known ancestor), assuming they have entered that information.

Earliest Known Ancestors (EKA)

You’ve probably noticed that earliest known ancestors, along with their locations, are used in many places.

Please enter both your direct paternal (father, father, to father’s line) and direct matrilineal (mother, mother, to mother’s line) earliest known ancestors, along with their locations. I wrote about how to do that in “Earliest Known Ancestors” at FamilyTreeDNA in 3 Easy Steps, here.

Trees #15 and #16 – Public Trees

In addition to trees within testers’ accounts, Discover trees, Group Time Trees, and WikiTree tree integration, FamilyTreeDNA provides two additional public trees.

FamilyTreeDNA made the Y-DNA and mitochondrial DNA haplogroup trees freely available years ago, at the bottom of their main company public page – without signing in.

These trees are still actively maintained today and are free for everyone to use.

To find these trees, scroll all the way to the very bottom of the page, in the footer, to the Community section. Yes, I know, it’s a bit like a scavenger hunt!

You can select to view either the Y-DNA or mtDNA tree. I love this tree, because it shows how many SNP-confirmed people have been tested. That number does not include the thousands of academic and public samples that may be utilized to help define haplogroups, and that you’ll sometimes see in your Ancient and Notable Connections.

So, if you receive a new haplogroup, but you don’t see a new match on your list or on the Block Tree, it’s probably because you match a high-quality academic sample.

The trees display from the root, meaning the oldest haplogroup is shown at the top. In the Y-DNA tree, above, haplogroup A-PR2921 is “Y-Adam”.

You can select any haplogroup on the bar across the top, search by country, or select a specific branch name to view.

The tree itself is viewable by country, as shown above, or by variant, meaning the haplogroup-defining mutations, shown below.

Additionally, for the Y-DNA tree, you can choose to display by surname, so long as there are two or more testers with that identically spelled surname who share this haplogroup and who have given permission for public display.

Please note that these people are all SNP-tested and confirmed at the level reported, but they are NOT all Big-Y testers.

This feature alone can be genealogy-changing because they may be surnames associated with your ancestors in records, or they may just be neighbors. Or maybe you thought they were “just neighbors,” but they are actually related.

At one time, customers could order an individual SNP test for R-M269 to confirm their predicted haplogroup. That test is no longer available, but anyone who took that test to confirm R-M269 and never tested or received results (like Family Finder) at a more granular level will be reported at R-M269. Note that 687 is the number of distinct surnames shown, not the total number of testers.

The three “hamburger dots” on the right side provide options for a user-reported Country Report based on the location of their earliest known ancestor, and a Surname Report. The surname report for R-M269 shows a total of 2448 testers who share those 687 surnames.

It’s a Whole Forest

Who knew there were 16 unique trees available at FamilyTreeDNA!

Each tree has a unique purpose and provides information not available elsewhere.

Take a look and see what kind of information is waiting for you – and don’t forget to check back often.

_____________________________________________________________

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 2026 – The Wind Beneath Our Wings

I started writing this article on Sunday evening, the day after RootsTech ended, and I’m basking in the afterglow. Also, my back and feet may never forgive me.

As a tongue-in-cheek comment, I think someone coined the word “exhausterwhelmulated” and defined it as being exhausted, overwhelmed, and overstimulated all at once. Yep, that’s me.

However, I need to add another couple of words to this – gratitude and joy.

Gratitude and Joy

I’m going to try to express this without sounding too sappy.

Do you recall the joy you used to feel when you spotted a relative you loved dearly but didn’t get to see often? Think of the unbridled joy as you piled out of your parents’ car and spotted your grandmother coming out of the door because she saw the car pull up. You ran as fast as your little legs could carry you directly into her arms, and got hugged so tightly it nearly squeezed the breath out of you.

I don’t know what the word for that would be, but it’s similar to how RootsTech feels.

Let me explain. Continue reading →

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

Y-DNA Results at 20 Years: Answers, Lessons, Methods, and Workarounds

Our goal as genealogists is always to learn what we don’t know and reveal anything we should know.

I’m going to share the evolution of four tests, purchased exactly twenty years ago. I haven’t cherry-picked these, so you’re getting the raw story. Successes, challenges and regrets, plus a few hacks to help you out when you’ve hit a roadblock.

I’m also sharing how I work around some issues – like tests that haven’t been (and can’t be) upgraded to Big Y tests.

DNA testing has come a long way from an infant science two decades ago, when we were tentatively establishing a new industry – one that today has evolved into a staple for serious genealogists.

On New Year’s Eve, 2005, exactly 20 years ago, I was doing the same thing I was doing at midnight in 2025 – genealogy.

That was long before the days of social media and chat groups, so some of us geeky types were discussing our genealogy research on the now-obsoleted RootsWeb e-mail list.

I Was Planning for 2006 Travel

I realized that I was going to be traveling during 2006 and would be asking several men to take a Y-DNA test, so I should purchase several kits while they were still on sale.

Then I got a bit giddy when I realized that I could actually celebrate the New Year by making those purchases right at midnight.

And I did too – I hit it right on the dot.

I mean, for a genealogist, what better way to celebrate? Right?

What I didn’t know is that, quite by accident, I managed to score kit 50,000. That seemed like such a milestone!

And now, I can’t believe it’s been 20 years. How is that even possible?

After I went to bed in the wee hours of January 1, 2026, I decided I needed to check in on the kits I purchased on that fateful New Year’s Eve, 2005, and see how they are doing. What were my goals, aspirations and expectations? Did we accomplish them then? Have we now?

What has happened in the past twenty years?

Let’s take a look, beginning with kit 50,000.

Kit 50,000 – Mr. Miller

Mr. Miller is my mother’s second cousin, so the perfect person to represent our Miller line.

Goals and Questions:

  • Do we descend from Johann Michael Miller born in 1692 in Germany? At that time, we did not know his birth location, and only knew that the line was German. Later research would add two additional generations and place his grandfather, Heinsman Mueller in Schwarzenmatt, Switzerland before 1655.
  • Does the Elder Jacob Miller (born about 1710 in Germany), a Brethren minister, match the Johann Michael Miller line? They were both Brethren, clearly knew each other, and were found in some of the same locations. The answer is conclusively no; the lineages are not the same based on both STR and Big Y-700 tests.

2005 – 12-marker test – $99

  • Initial 2006 haplogroup – R-M269 – about 6,500 years old
  • 2025 haplogroup – R-BY56132 – about 350 years old, obtained via DNA match to another Miller tester

That a HUGE difference!

2006 matches – no Y-DNA matches.

Remember, this was early, with less than 50,000 results in the database, compared to just under 700,000 SNP-confirmed testers today, not to mention probably double many more STR-only testers.

Haplogroups for STR testers are predicted based on marker values and are not SNP tested or confirmed. The Big Y tests, SNP tests and SNP packs which are no longer available, and haplogroups assigned through Family Finder are SNP confirmed.

2025 matches – 2 (yes two) 12-marker matches, both Millers. At 25 markers, he has 7 matches, all Millers.

I created the Miller-Brethren Project in September 2006 for any Miller line that was of the Brethren faith, hoping to differentiate between families with the same names in the same place.

2009 – upgraded to 67 markers – $148

In 2009, I upgraded Mr. Miller to 67 markers and recruited two other Miller males from our believed line. They all matched at 25 markers and above, confirming the lineage to our ancestor, Johann Michael Miller/Mueller. Whew! That one was close, because there was a great deal of consternation and confusion about these lineages.

2011 – added Family Finder – $289

Mr. Miller’s haplogroup today, confirmed by Family Finder, is still same as his predicted R-M269 from his STR results. Unfortunately, the kit has never been upgraded to the Big Y test, and I desperately want our personal lineage haplogroup. However, all is not lost because he matches several males from the same lineage who have been assigned to haplogroup R-BY56132 through the Big Y-700 test.

Every haplogroup is publicly viewable in Discover, but testers can see additional information and features when they click through to Discover from their own account – including the Match Time Tree, Globetrekker™, and more Ancient and Notable DNA Connections.

Discover provides an informative Haplogroup Story, an overview before viewing the dozen reports available in the left sidebar about that haplogroup’s history and lineage. You can take a look, here.

From Discover, we learn that the Miller haplogroup was born (or branches off from) its parent haplogroup about the year 1650 CE, so when the Millers were still living in either Switzerland or Germany. If we match males from either of those locations, they would probably match us upstream at R-BY115568. Their genealogy would certainly help our genealogy!

Ancient Connections, which are ancient DNA matches, extend beyond surnames, revealing connections to both the Yamnaya and Moros cultures and shared ancestry with Bronze Age Balkan burials.

Viewing the Ancient Connections tab, we learn that remains related to or upstream of our haplogroup were excavated in Albania, Germany, Hungary, Bulgaria, the North Banat and Mokrin in Serbia, and Macedonia. The closest genetic connections are shown first.

New Goal: Would love to test and match with Mueller men from Steindwenden, Germany, Schwarzenmatt, Switzerland, or anyplace near either location.

Kit 49,999 – Mr. Estes

Goals and Questions:

  • Do we connect with the Abraham Estes (c1647-1720) lineage?
  • Was there more than one early colonial Estes line?
  • If so, were they related?
  • Did our line come from Kent, England?

2005 – 25-marker test – $150

2006 matches –  54 12-marker matches

2025 matches – 326 12-marker matches

2006 matches – 4 25-marker matches – one to a known cousin, two more to other Estes males

2025 matches – 30 25-marker matches, including several Estes men

Crucial – this tester matched an Eastes male who lived in Kent and whose ancestors never left. This confirmed our oral history and early research suggesting that Abraham Estes’s origins were in Kent.

  • Original 2006 haplogroup – R-M269 – about 6.500 years old
  • Current Haplogroup – R-L151 – about 5,000 years old, SNP confirmed from the Family Finder test
  • Match Haplogroup – R-ZS3700 – about 250 years old obtained from STR match to multiple Big Y testers who shares same ancestor

In 2012, we added the Family Finder test for $199, which answered questions about whether multiple half-siblings were actually descended from a close relative of the tester. Family Finder also allowed people descended from this line, but who don’t carry the Estes Y-DNA to confirm their relationship to the Estes family.

This tester has not upgraded to the Big Y-700, but does match at the STR level with those who have taken that test.

Today, the Eastes male from Kent who subsequently upgraded to the Big Y-700 forms the base of the Estes family genetic tree, and others in the American lines form descendant branches based on the Big Y-700 test!

This includes some men whose genealogy we can’t yet connect vis the paper trail, such as kit 491887, shown in lavender below, but we know where he connects genetically. We were able to place him due to his Big Y-700 test results.

Thanks to the man from Kent whose results appear in the pink column, we know that both the Massachusetts and the Virginia immigrants descend from the Estes line in Kent, based on haplogroup R-BY490.

The Massachusetts line carries only R-BY482, so R-BY490 occurred in the generation between Robert b 1555 and Sylvester b 1600. Because the descendant of Sylvester’s brother Robert, born in 1603, does NOT carry the BY490 SNP, so we know exactly where and when it was introduced.

In Abraham’s lineage, two additional branches have been discovered. R-ZS3700, and within that haplogroup, R-BY154784.

All of this structure was built beginning with kit 9,993, followed by 49,999 (for my line), which is not shown in the chart above because there is no Big Y test, but whose STRs do match with kit 9,993, our very first Estes male to test.

Discover shows that R-ZS3700, the defining haplogroup of the Moses Estes lineage, kit 9,993, was born about 1750, which is within the genetic range of about 1600 to about 1820. Moses Estes, the man in whom this SNP originated, was actually born in 1711. The genetic tree closely matches the genealogy tree.

Ancient Connections reveals that we share distant ancestors from about 4400 years ago with Iron Age burials in Scotland, Cambridgeshire, Denmark, Dorset, Cornwall, Bedfordshire, Oxfordshire, Yorkshire, and Iceland. In other words, the Estes lineage has been in England for a very, very long time.

One of the upstream parent haplogroups, R-S252, dating from about 4500 years ago, was found in an Anglo-Saxon burial at Cliff’s End Farm, a mortuary and ritual Bronze Age site in Kent, England.

Cliffsend is only about 10 miles from Deal, where many Estes family records are found, and about 5 miles from Sandwich where Abraham Estes, the immigrant, was a weaver, next to the village of Worth, where he was married in 1672.

Kit 49,998 – Mr. Moore

Goals and Questions:

  • I was desperate to test a male from my Moore family in Halifax County, VA, and was very fortunate to locate Mr. Moore when I visited in person. I had to work on his genealogy, but once I was able to connect him, he was excited to test.
  • Could we connect our line with other Virginia lines, or eliminate them from consideration?

2005 -12 marker test – $99

2006 matches – 37 12-marker matches, two of whom were Moore men. One was a man I believed to be from my James Moore and William Moore line, and one we suspected, but really didn’t know. Many records from that time period are missing, and people were moving to the next frontier, with no connection to where they came from.

Mr. Moore’s matches, combined with his genealogy, confirmed what we thought we knew, but we still needed more.

  • Original 2006 haplogroup – J-M172 – about 28,000 years old
  • Current Haplogroup – J-M241 – about 8,600 years old, obtained from Family Finder
  • Match Haplogroup – J-Z631 – about 2,950 years old, obtained from matches to other Moore men who took the Family Finder test
  • Big Y Match Haplogroup – J-BY136349 – about 1,300 years old, obtained from a 111-marker Moore match to a non-Moore man who has taken a Big Y test

In 2012, we added Family Finder for $199, which provided invaluable matches to known Moore lineage family members, including Mr. Estes, kit 49,999. That makes perfect sense, since they are 4C1R.

2025 matches – 276 12-marker matches, of which five are Moore men, none of whom have taken the Big Y-DNA test.

One Moore match, who has not responded to emails, shows his paternal Moore ancestor as having been born in Scotland.

Three of Mr. Moore’s matches whose haplogroups were determined by Family Finder are J-Z631, which is closer to the present time than Mr. Moore’s haplogroup.

Why might that be?

Different autosomal DNA testing chips were used by different vendors at different times. Mr. Moore and the three other Moore men all took a Family Finder test at FamilyTreeDNA, but at different times when different chips were in use. That’s probably why the haplogroup assignment is different. The other reason could be that one of the SNP locations was missed in the autosomal DNA test. The haplogroup designation from the Family Finder test is a recent freebie, so was never actually intended to be a feature.

That’s all fine and dandy, but I STILL need a Moore Big Y tester to reveal more information about my line.

Workarounds for No Big Y Testers

Without a Big Y-700 Moore tester, is there something else we can try to obtain at least a somewhat more refined haplogroup?

Perhaps.

Without at least one Big Y-700 test, the next two things can do are:

  • Hope that someone has included at least some genealogy for you to follow.
  • One of the 111 marker matches will help by sharing if they have any Moore matches at that level. Remember, this kit, 49,998, only has 12 marker matches.

In this case, there is one match with a tree, but I hit the same genealogical brick wall that they did.

They, and now I am stuck with John Moore, born between 1851 and 1860, possibly in Sullivan County, TN. He was married to Mary, Polly, Mollie (take your pick based on the census and death certificates) Whitaker, who died between 1900 and 1910. John Moore died on September 25, 1936, in Sullivan County, TN, with several children and a brother named Bob Moore who lived in nearby Bristol listed in a brief obituary. I’m doing the “quick and dirty” tree thing, here, hoping to perhaps track his Moore back further than I have my own so we can connect – but so far – no cigar. I’m not finished yet, but this one is challenging. I’m always hopeful that I’ll find some hint about where James Moore (c1718-c1798) came from before Prince Edward and Amelia County, VA.

Eliminating Other Moore Lines

I certainly don’t have as much information as I want about my own Moore line, but I do have something. How can I use this to eliminate other potential Moore lines?

Checking the Moore Surname Project, I use the browser search and located the group of my James Moore testers.

These six men are candidates for Big Y upgrades.

I can also use the browser search to locate other groups of Moore men that have tested and I know we’re not related to.

For example, here’s another group of Moore men that we aren’t related but – but here’s the catch. This is the “other” James Moore that appears in Halifax County, and whose land is located right across the road from my James Moore. I kid you not. I could have SWORN these two Moore lines were the same, but they are not. This line track back to Thomas Moore born in 1720 and who married Mary Farrar. Using genealogy and projects, combined with what we do know, we can eliminate many possibilties.

Ok, let’s set genealogy aside for a minute.

Working With Alternative Haplogroups

What else can we do if we cannot upgrade either our tester or convince other Moore men to upgrade to the Big Y-700?

If a tester has higher level STR matches, meaning 67 or 111, and they match anyone with a Big Y-700 test, they will likely be in the same area of the genetic tree, but probably not the same branch, and possibly not within hundreds to the low thousands of years. This approach is an extremely poor substitute for the Big Y test and should never be used unless there is absolutely no other alternative. Think of it as sitting proxy at home, watching the Jumbotron on your TV, versus sitting behind home plate in the ballpark. It will do if you have no other choice.

That said, let’s see what we have. Our Moore Family Finder SNP is J-Z631, which is about 2,950 years old.

Our J-Z631 haplogroup story shows that the majority are found in Germany, followed by England, and the Ancient Connections are associated with the Roman era in the Balkans and Sicily. Burials from that era were found in Rome, Montenegro, Hungary, Poland, Serbia, Croatia, and Trapani, Italy.

Next, let’s look at one of the Moore men’s 111 matches, who has been assigned the Big Y-700 haplogroup of J-BY136349.

This is quite interesting, because this haplogroup has few testers, but the Ancient Connections are found in some of the same locations.

Next question – how are these two haplogroups related? Let’s see, using Discover’s Compare feature.

Wow, I didn’t expect to discover that J-BY136349 (111 marker match to a non-Moore man) is a descendant of J-Z631 (Moore haplogroup from Family Finder) and is about 2,200 years closer to the present time. Our Moore men, if we can ever find a Big Y-700 tester, will likely be someplace near J-BY136349.

Goals:

  • To upgrade at least one of Mr. Moore’s matches to the Big Y-700, and for some new Moore male to match so we can figure out which Virginia line, and which European line our Moore family descends from.
  • To break through the John Moore brick wall in Sullivan County, TN to see if we can track that lineage further back in time – informing us of our Moore line.

Kit 49,994 – Mr. Speaks

Goals and Questions:

  • To find and test any Speak/Speaks tester for our line.
  • Were the two Thomas Speaks in Maryland in the 1700s related?
  • Were various Speaks lines, by various spellings, throughout the country, related?
  • Where did we “come from?”

Twenty years ago, we had no Speaks males to test until Joyce, one of our long-time genealogy experts, located one man. She visited him and explained why his DNA was important. I provided a scholarship, and the rest, as they say, is history.

Not long after, another Speaks man tested, but did not match our original tester. Everyone was shocked. No one expected that result, and it only confused matters even more.

We needed tie-breakers, meaning other men from both of the known sons of immigrant, Thomas Speake (1633-1681).

At this point, we had far more questions than answers.

The Speaks Family Association had a whole list of questions, in part due to a lack of early records in Maryland, combined with burned southern states in later generations. That list was growing, not shrinking.

How many Speaks lines were there anyway? Had we stumbled across a descendants from the “other” Thomas Speaks in Maryland? I can’t answer that question now, and the answer is no, we had not accidentally found the other Thomas. That Thomas’s will and estate shows he had no sons other than a son Thomas who is not our Thomas, based on the fact that he died before his father. That also means there are no males from his line to test. You can read more, here, if you’re interested.

Did men with the surname Speak, Speaks and similar spellings all descend from the same Maryland line? Apparently not, or maybe not, based on those early results.

Could we determine through which men various testers descend?

At that time, we didn’t even dream that we’d be able to obtain Y-DNA from various men in the Lancashire villages where we thought our line might have originated. That was still years in the future. Our big breakthrough came after a Speaks man from New Zealand tested, and knew the name of the Lancashire village, Gisburn, where his grandfather was born. Working with local historical societies in England, we made that trip happen in 2014 and learned even more about differing Speaks lines.

In other words, in 2005, we were starting from scratch with pockets of men in various locations across the US who shared the same or similar surnames.

2005 – 25-marker – $150

  • Initial haplogroup – I-M170 – about 28,000 years old
  • Current 2025 haplogroup – I-FTA13986 – about 250 years old, obtained from a Big Y test

2014 – 111-marker upgrade – $184

2024 – Family Finder and the Big Y

2006 matches – Mr. Speaks had no 12 or 25-marker matches, which was discouraging. In fact, Mr. Speaks wouldn’t have any matches until the Family Association began actively recruiting testers a few years later. As it turns out, the Speaks family line has a rather unique DNA signature.

Today, Mr. Speak has 61 12-marker matches, and 54 25-marker matches, but it’s his Big Y results that confirm his placement in the tree as a descendant of John Speake the Innkeeper, son of Thomas Speake the immigrant.

Initially, we did the best we could, placing people in the tree based on STR results, but STRs did not provide the granularity we needed to define lines conclusively. STR mutations tend to back-mutate and aren’t always reliable.

Fast forward to January 2026.

The Speaks DNA project now has 48 Y-DNA testers, of which 32 fall into the Lancashire Speaks line we were seeking.

The Speak Family Association funded several Big Y-700 tests and upgrades for critical men in known lines.

Additionally, we’ve finally placed the elusive Aaron Lucky Speaks line, found in North Carolina, without any connecting documents back to Maryland. DNA connected him!

We’ve also eliminated several lines that were possibly connected to the Lancashire/Maryland line, thanks to DNA testing.

The Speak Family DNA Project Time Tree shows the Big Y testers with their self-identified earliest known ancestors (EKA) placed on branches of the genetic Time Tree.

Shifting to Discover, we see that Lancashire SNP, I-BY14004, which defines our Speak line, is associated with Medieval Britain, the early Slavs, and a historical Romanian culture.

Checking Ancient Connections, our ancestors are associated with burials from Yorkshire, Croatia, Romania, Denmark, Italy, the Czech Republic, France, Germany, and more, dating from about 4500 years ago.

Today, if a Speak/Speaks male takes a Big Y-700 test, we can assign his location in the tree very closely, and can tell him definitively which lines he does not descend from.

The Speaks project also welcomes all Speaks descendants, from any line, who have taken or uploaded autosomal DNA tests.

Regrets

Yes, I have regrets – learned in the school of hard knocks.

  1. My largest regret is that I didn’t test all of “my” kits at the highest level possible initially.
  2. My second regret is that I didn’t reach out to matches much earlier (when they still might answer) to inquire about genealogy and offer scholarships for upgrades. My testers need someone from that same line to match at the Big Y level. In some cases, I need that person to upgrade because my tester cannot. The longer you wait, the less likely you’ll receive a response.

Many tests, especially early tests, cannot be upgraded for various reasons:

  • Deceased tester
  • Lost the ability to contact the tester – obsolete or bounced email
  • Tester does not want to upgrade or does not reply to emails
  • Last vial available was already used and tester cannot provide another
  • Last vial was tested and failed

Solutions

  • Buy the most advanced test immediately. I literally have a kit available at all times.
  • Upgrade to the newest relevant tests as soon as they are introduced. In this case, that would be the Big Y-700 today and the Family Finder when it was introduced.
  • If the tester is deceased and you can contact the family, after offering condolences, ask for brothers, sons, or nephews who would be willing to retest.
  • Offer DNA testing scholarships either personally, through family associations, or through surname projects.
  • Request extra vials be sent to the tester so they can be returned and stored for future use.

There’s one more thing you need to do too.

Permissions

Testers can grant various forms of permission to other people, which allows their tests to be upgraded later. One man even sent me an affidavit stating I could do so after he died. Today, that’s not necessary because FamilyTreeDNA provides a Beneficiary service.

Permissions can be granted under the tester’s Account Settings.

  • Ask the tester to designate a Beneficiary which can be a Group Project Administrator. That means any person who is a group project administrator of a project the tester belongs to, after they are deceased.
  • Ask the tester to assign a Kit Manager who literally manages their kit on their behalf.

Under Project Preferences, project members can grant Advanced Access to individual project administrators by name. Advanced Access provides the ability for that specific administrator to act on behalf of the tester, including ordering upgrades and additional tests, so long as the administrator pays for them, which they often do with project funds.

Looking Back

I have absolutely no regrets about purchasing any of the tests I’ve bought over the years.

I look at it this way – if someone told me that a book about my ancestral line was in a library, and it held the undisputed truth about that one line – I’d spend far more than what I’ve spent on any one DNA test to obtain it. There’s simply no other way to conclusively unravel direct paternal vines, both within a genealogical timeframe, and before.

I want to know everything. Not just since the advent of surnames, but where my ancestors came from before that, and before that, and before that. I want to read about the culture and history of the land where my ancestors lived. What did they survive to travel to the next frontier? And where was that next frontier, and when?

Their own Y-DNA, passed down to their direct male descendants holds those secrets, just waiting to be revealed.

What’s Next?

  • Check your own and any Y-DNA tests that you sponsor or manage to see how they’re doing and what’s new.
  • Check surname projects at FamilyTreeDNA, here, to see if your ancestral surnames are represented any other information, similar to my Moore line.
  • Check your ancestor at WikiTree to see if anyone has entered a haplogroup for that ancestor, which tells you that someone has tested. The haplogroup may not be current, but it gives you a connection and someplace to start.
  • Check your autosomal matches at FamilyTreeDNA and any other vendor to see if you match surnames of interest. If the match is male, reach out and see if they descend from your line, and if they haven’t taken a Y-DNA test, would they be willing. If your match is female, reach out to see if it’s your line, and if so, if they know of males who have tested or would be willing.
  • If you’re a male and have not yet tested your Y-DNA, by all means, order that test now, by clicking here! Then make sure to join your surname project!

Is there something new and wonderful waiting for you?

_____________________________________________________________

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

2025 Genetic Genealogy Retrospective: Wow – What a Year!

2025 has been quite a year in genetic genealogy. Genetic genealogy, per se, really isn’t a separate “thing” anymore. DNA testing is now an integral part of genealogy, with the potential to answer questions that nothing else can!

The 76 articles I wrote in 2025 fall into multiple categories and focus on different topics based on what was happening in the industry.

From my perspective, here are the most notable announcements and trends in genetic genealogy, and genealogy more broadly.

#1 for 2025 – Mitochondrial DNA: The Million Mito Project Released the New Mitotree, Updates, and mtDNA Discover

The biggest genealogy news items this year, both industry-wide and genealogy-changing are definitely the release of the new Mitotree, plus two tree updates. But that’s not all.

In addition, full sequence mitochondrial DNA testers received new Mitotree haplogroups, if appropriate, and everyone received a haplotype – a new feature. Along with Mitotree, FamilyTreeDNA introduced mtDNA Discover which provides 13 individual reports based on your haplogroup and matches.

It’s no wonder that mitochondrial DNA articles led the pack with the most views based on the eleven articles about that topic. If you haven’t yet tested your mitochondrial DNA at FamilyTreeDNA, there’s no better time! You never know what you’re going to discover and the more testers, the more matches for everyone.

You don’t know what you don’t know, and you’ll never know if you don’t test. Remember, mitochondrial DNA is for both males and females and tests your mother’s direct matrilineal line (mother to mother to mother, etc.) – reaching beyond known surnames.  Click here to order or upgrade.

#2 – MyHeritage Low Pass Whole Genome Sequence Test Charges into the Future

Another big hitter is the new MyHeritage low-pass whole genome test (WGS) test. It’s new and innovative, but we haven’t seen comparative results yet.

My results from the new low-pass whole genome test just came back, and I haven’t had the opportunity to review them yet, as compared to the earlier tests. That said, I do have roughly the same number of matches, but I need to determine if they are the same matches, and how well they track. I’ll be working on that review soon.

The new whole genome test may be more about future proofing and preparedness than additional current benefit – but we will see. I definately wanted to take the whole genome test so I can receive and benefit from whatever new is coming down the pike.

MyHeritage allows you to maintain multiple DNA tests on your account, so the new whole genome won’t “replace” your older or uploaded test. That way, you can easily compare the results of the whole genome against any DNA test that you curently have at MyHeritage.

Click here to order the new test.

#3 – 23andMe Experiences Problems

On a less positive note, but still quite newsworthy is the bankruptcy of 23andMe and subsequent repurchase of 23andMe by the original founder after setting up a new nonprofit. I have real mixed feelings about this topic. However, 23andMe was really never about genealogy, and now, matching segment information is no longer available. Those searching for unknown parents or family may want to test there if they are unsuccessful elsewhere.

Best Genealogy Tool

The FamilySearch full text search continues to have a HUGE impact for genealogists. This tool is not one-and-done, but provides increasing amounts of rich information as more records are added to the “fully scanned” collection. If you haven’t tried it, please do. It’s a game-changer and continues to improve.

A Cautionary Word About AI – Artificial Intelligence

AI is such a hot topic right now that I feel it needs to be included.

The FamilySearch full text search uses a form of AI. However, you’ll quickly notice that it can’t read everything, gets words and names wrong, and if you actually need to fully depend on it for accuracy, you cannot. (That said, it’s still an amazing tool, and I’m not picking on FamilySearch.)

Aside from FamilySearch, AI in its current form is both wonderful and terrible. I’ll be writing about AI in the new year, but for now, don’t ever rely on AI for anything that you can’t verity. It’s your assistant, not an expert, no matter how insistent it is. Never trust and always verify.

This is ESPECIALLY TRUE WHEN RELATED TO GENETICS and genetic related topics. I can’t even begin to tell you how very wrong it has been, and how much people fall in love with inaccurate results. No, just no – at least for now.

You need to know your AI tool, your skill set, your understanding of AI broadly, the tool’s limitations, and yours, and that’s all before verifying the actual AI results. If you want to educate yourself, and everyone should, treat yourself to anything, anyplace by either Mark Thompson or Steve Little, the dynamic AI duo. They offer YouTube videos and classes in a wide variety of places – but keep in mind that AI tools and technology literally change every few weeks.

AI is, indeed, a specialty all unto itself, much like genetic genealogy. And right now, it’s not soup yet, but it is cooking.

Tried and True Genetic Genealogy Staples – DNAPrint and Genetic Affairs

I haven’t written about either one this year, but I use both DNAPainter and Genetic Affairs regularly.

I consistently paint segments from matches at both MyHeritage, FamilyTreeDNA, and GEDmatch that are newly identified to an ancestor or ancestral couple at DNAPainter.

Unfortunately, neither Ancestry nor 23andMe provide matching cM location information for your matches (chromosome browser), but you may find some people who have tested at those companies at both FamilyTreeDNA and GEDmatch if they have uploaded to either of those vendors. Both vendors provide segment information and a Chromosome Browser, enabling you to paint that information to DNAPainter when you can identify your common ancestor.

MyHeritage also provides a Chromosome Browser, but unfortunately, no longer accepts uploads from any other vendor. You can paint segments from MyHeritage, but no longer upload DNA files to MyHeritage.

Thanks to DNAPainter, I have 90% of my segments identified to specific ancestors – which is actually rather remarkable given that my mother’s grandfather was a Dutch immigrant, and her great-grandparents on her other side were German immigrants, meaning we don’t have many matches on either of those lines.

Genetic Affairs continues to develop new, advanced clustering tools, one of which I’ll be reviewing soon.

Major Vendor Releases

Aside from what’s listed above, most of the major vendors released new features.

MyHeritage released a VERY COOL new tool called Cousin Finder that finds your relatives in the MyHeritage database, whether they match you on a DNA test, or not. They may not have even taken a DNA test. Cousin Finder identifies your common ancestor and shows your relationships. It’s a wonderful way to initiate communications, discuss your common ancestors, and ask about DNA testing.

Of my 378 Cousin Finder matches, only 23 (about 6%) are on my DNA match list, so that leaves 355 people to message, several of whom represent Y-DNA and mtDNA lines I don’t have. You can bet I’ll be offering testing scholarships.

Additionally, MyHeritage released a new ethnicity version.

FamilyTreeDNA, in addition to the new Mitotree, Discover, and associated features, released a new match matrix so you can see if and how selected matches are related to each other in a grid format. In other words, you can create your own cluster.

A new built-in “Share” feature blurs private information to make sharing easier both on the website and in Discover.

Discover improvements include thousands of new Y-DNA and mtDNA tree branches, plus thousands of new Ancient DNA samples. Discover is evergreen, so once you’ve taken that Big Y-700 test or the mitochondrial DNA test, your learning never stops as more content is added.

Tree integration with WikiTree is super-easy and means you don’t have to choose between trees. You can choose to retain your archived tree at FamilyTreeDNA, or move your tree to MyHeritage, PLUS link yourself to your family at WikiTree.

Ancestry released match clustering and a new beta pedigree view of ThruLines, but that’s back in the shop for more work. I’d expect to see it rereleased in 2026.

Conferences

RootsTech is the granddaddy of genealogy conferences, and it’s always fun to attend and write about the experience. Many vendors release new tools or products during the conference.

The ECGGC (East Coast Genetic Genealogy Conference), held in the fall, is the only conference that focuses entirely on genetic genealogy, new tools, how to use existing tools, and more. The 2025 conference was virtual and provided a great deal of focused content. Attendees particularly appreciate the deep dive in a particular topic presented in DNA Academy.

I’ll be at RootsTech in 2026, will write about that soon, and hope to see you there.

Concepts, Techniques and Plain Old Genealogy

In the past, my Concepts series and genealogy “how to” articles have been very popular, so, in 2025, I penned a half-dozen articles focusing on frequently asked questions about relationships and DNA.

For example, how does one go about finding DNA testing candidates? The number of options may surprise you and includes both Cousin Finder and Relatives at RootsTech.

By testing ONE PERSON for either Y-DNA or mitochondrial DNA that represents an ancestor, you actually receive information about that entire lineage of ancestors. So, on my Estes line, by locating an Estes male from my line to test, I received relevant information for every Estes male in my line, back to and beyond the progenitor.

Eventually, we hit a brick wall in every line, and those tools are the perfect way to break through those brick walls.

Other articles discuss things like how to use Discover’s Ancient Connections, and the difference between half and full relationships, both in your tree and genetically. Plus, what does a cousin “once removed” mean anyway? And why do I care?

Another question I receive is how far back, based on the shared amount of DNA, should I look in my matches’ trees for our common ancestor? In other words, how many generations back should I click? That article was fun and produced some unexpected results.

Memorial Articles

Because we are part of a community, I write memorial articles when one of our friends passes on. This year, sadly, Schelly Talalay Dardashti, well-known Jewish genealogist, and another very close friend joined the ancestors, so I’ve recognized the best in both of their lives which constitutes their legacy.

Be the Storyteller

Last, but not least, I wrote about my ancestors in the “52 Ancestors” series, which launched several years ago with Amy Johnson Crow’s challenge to write about one ancestor per week. She hosts this every year, and you can join (free) now.

I’m now on ancestor #467, so yes, it’s addictive, but it’s also AMAZING how many wonderful cousins I’ve met who have information that I did not. Not only that, but after publishing about an ancestor, I’ve discovered that I’m related to people I’ve known for years. We were SOOOooo excited!

I’ve been writing about the lives of my ancestors for several years now, and the articles include attempts to identify Y-DNA and mtDNA testers for each ancestor, where appropriate. There’s so much to learn that can’t be revealed any other way.

Plus, people seem to like the “mystery” and “short story” aspect, and I salt each story with the history of the region and relevant historical events of the timeframe. You might find your ancestors here too, or other helpful information.

Find a way to share about your ancestors!

Do You Have Suggestions for 2026 Topics?

Do you have suggestions or requests for article topics in 2026? If so, please comment on this article and let me know.

Check Out the 2025 List

Here’s the list of the 2025 articles. Did you miss something fun? Enjoy!

  Title Category Date Link
1 Welcome to 2025 – Opportunities and New Genetic Genealogy Articles Welcome, general 1-2-2025 https://dna-explained.com/2025/01/02/welcome-to-2025-opportunities-and-new-genetic-genealogy-articles/
2 Anne Doucet (1713-1791), Oceans, Rivers, and Perseverance – 52 Ancestors #438 52 Ancestors 1-4-2025 https://dna-explained.com/2025/01/04/anne-doucet-1713-1791-oceans-rivers-and-perseverance-52-ancestors-438/
3 Register for RootsTech 2025 Now RootsTech 1-16-2025 https://dna-explained.com/2025/01/16/register-for-rootstech-2025-now/
4 What IS the McNeil Family History, by George Franklin McNeil – 52 Ancestors #439 52 Ancestors 1-19-2025 https://dna-explained.com/2025/01/20/what-is-the-mcneil-family-history-by-george-franklin-mcneil-52-ancestors-439/
5 Jean Garceau dit Tranchemontagne (c1785-1711), Soldier from Saint Marseault – 52 Ancestors #440 52 Ancestors 1-29-2025 https://dna-explained.com/2025/01/29/jean-garceau-dit-tranchemontagne-c1785-1711-soldier-from-saint-marseault-52-ancestors-440/
6 Memories Resurface When the Old Family Home Gets a Facelift Genealogy 2-3-2025 https://dna-explained.com/2025/02/03/memories-resurface-when-the-old-family-home-gets-a-facelift/
7 MyHeritage Introduces Ethnicity v2.5 MyHeritage 2-6-2025 https://dna-explained.com/2025/02/06/myheritage-introduces-ethnicity-v2-5/
8 Relatives at RootsTech Reveals Cousins and Provides DNA Candidates RootsTech, techniques 2-8-2025 https://dna-explained.com/2025/02/08/relatives-at-rootstech-reveals-cousins-and-provides-dna-candidates/
9 FamilyTreeDNA’s New Matrix Shows How Your Matches Are Related to Each Other FamilyTreeDNA 2-12-2025 https://dna-explained.com/2025/02/12/familytreednas-new-matrix-shows-how-your-matches-are-related-to-each-other/
10 René Doucet (c1680-c1731), Lifetime of Incessant Upheaval – 52 Ancestors #441 52 Ancestors 2-15-2024 https://dna-explained.com/2025/02/16/rene-doucet-c1680-c1731-lifetime-of-incessant-upheaval-52-ancestors-441/
11 Lineages Versus Ancestors – How to Find and Leverage Yours Techniques 2-23-2025 https://dna-explained.com/2025/02/23/lineages-versus-ancestors-how-to-find-and-leverage-yours/
12 Mitotree is Born Mitochondrial DNA 2-25-2025 https://dna-explained.com/2025/02/25/mitotree-is-born/
13 RootsTech 2025 – The Year of Discover and the New Mitotree RootsTech, Mitochondrial DNA 3-14-2025 https://dna-explained.com/2025/03/15/rootstech-2025-the-year-of-discover-and-the-new-mitotree/
14 Pierre Doucet (c1621-1713), Walking History Book Lived to Nearly 100 – 52 Ancestors #442 3-16-2025 https://dna-explained.com/2025/03/16/pierre-doucet-c1621-1713-walking-history-book-lived-to-nearly-!100-52-ancestors-442/
15 Welcome to the New FamilyTreeDNA mtDNA Group Mitochondrial DNA 3-17-2025 https://dna-explained.com/2025/03/17/welcome-to-the-new-familytreedna-mtdna-group/
16 23andMe Files for Bankruptcy – What You Need to Know! 23andMe 3-24-2025 https://dna-explained.com/2025/03/25/23andme-files-for-bankruptcy-what-you-need-to-know/
17 New “Share” Features at FamilyTreeDNA Blur Match Information and Make Sharing Easy FamilyTreeDNA 4-1-2025 https://dna-explained.com/2025/04/01/new-share-features-at-familytreedna-blur-match-information-and-make-sharing-easy/
18 The Chauvet Cave: Trip Back in Time with Prehistoric European Humans – Are We Related? History, DNA 4-6-2025 https://dna-explained.com/2025/04/06/the-chauvet-cave-trip-back-in-time-with-prehistoric-european-humans-are-we-related/
19 DNA for Native American Genealogy Webinar & Companion Book Native American 4-8-2025 https://dna-explained.com/2025/04/08/dna-for-native-american-genealogy-webinar-companion-book/
20 Marie Levron (c1686-1727), Tragedy from Cradle to Grave – 52 Ancestors #443 52 Ancestors 4-14-2025 https://dna-explained.com/2025/04/14/marie-levron-c1686-1727-tragedy-from-cradle-to-grave-52-ancestors-443/
21 Mitochondrial DNA: What is a Haplotype Cluster and How Do I Find and Use Mine Mitochondrial DNA 4-14-2025 https://dna-explained.com/2025/04/14/mitochondrial-dna-what-is-a-haplotype-cluster-and-how-do-i-find-and-use-mine/
22 New Mitotree Haplogroups and How to Utilize Them for Genealogy Mitochondrial DNA 4-23-2025 https://dna-explained.com/2025/04/23/new-mitotree-haplogroups-and-how-to-utilize-them-for-genealogy/
23 Sir Francois Levron dit Nantois(c1651-1714), and Acadia’s Pirate – 52 Ancestors #444 52 Ancestors 4-26-2025 https://dna-explained.com/2025/04/27/sir-francois-levron-dit-nantois-c1651-1714-and-acadias-pirate-52-ancestors-444/
24 Catherine Savoie (c1661-c1722/25), Whispered Threads Weave a Tapestry of Life – 52 Ancestors #445 52 Ancestors 5-4-2025 https://dna-explained.com/2025/05/04/catherine-savoie-c1661-c1722-5-whispered-threads-weave-a-tapestry-of-life-52-ancestors-445/
25 Discover’s Ancient Connections – How Are You Related? Discover, Ancient DNA 5-8-2025 https://dna-explained.com/2025/05/08/discovers-ancient-connections-how-are-you-related/
26 Mother’s Day and Legacies 52 Ancestors, Genealogy 5-10-2025 https://dna-explained.com/2025/05/11/mothers-day-and-legacies/
27 The Mystery of the Blue Fugates and Smiths: A Study in Blue Genes and Pedigree Collapse Genetics, Genealogy 5-18-1015 https://dna-explained.com/2025/05/19/the-mystery-of-the-blue-fugates-and-smiths-a-study-in-blue-genes-and-pedigree-collapse/
28 Regeneron Wins Bid for Bankrupt 23andMe – Wedding Planned 23andMe 5-19-2023 https://dna-explained.com/2025/05/19/regeneron-wins-bid-for-bankrupt-23andme-wedding-planned/
29 Francois Savoie’s Homestead Rediscovered – 52 Ancestors #446 52 Ancestors 5-24-2025 https://dna-explained.com/2025/05/24/francois-savoies-homestead-rediscovered-52-ancestors-446/
30 Memorial Day – Some Gave All Memorial 5-25-2025 https://dna-explained.com/2025/05/25/memorial-day-some-gave-all/
31 Mitotree Webinar – What It Is, How We Did It, and What Mitotree Means to You Mitochondrial DNA 6-4-2025 https://dna-explained.com/2025/06/04/mitotree-webinar-what-it-is-how-we-did-it-and-what-mitotree-means-to-you/
32 Catherine LeJeune (c1633-1671/1686), Meet Your Grandchildren – 52 Ancestors #447 52 Ancestors 6-7-2025 https://dna-explained.com/2025/06/07/catherine-lejeune-c1633-1671-1686-meet-your-grandchildren-52-ancestors-447/
33 Mitotree Q&A for Everyone Mitochondrial DNA 6-11-2025 https://dna-explained.com/2025/06/11/mitotree-qa-for-everyone/
34 Father’s Day: Bravery and Love 52 Ancestors, Genealogy 6-14-2025 https://dna-explained.com/2025/06/14/fathers-day-bravery-and-love/
35 Francoise Bourgeois (c1659-1693/1697), High Drama in Beaubassin and Terror at Port Royal – 52 Ancestors #448 52 Ancestors 6-16-2025 https://dna-explained.com/2025/06/16/francoise-bourgeois-c1659-1693-97-high-drama-in-beaubassin-and-terror-at-port-royal-52-ancestors-448/
36 Requesting Suggestions for RootsTech 2026 Topics RootsTech 6-18-2025 https://dna-explained.com/2025/06/18/requesting-suggestions-for-rootstech-2026-topics/
37 FamilyTreeDNA and WikiTree Collaboration – In Two Easy Steps!! FamilyTreeDNA, WikiTree 6-25-2025 https://dna-explained.com/2025/06/25/familytreedna-and-wikitree-collaboration-in-two-easy-steps/
38 Jacques Bourgeois (c1620-c1700), Surgeon of Port Royal – 52 Ancestors #449 52 Ancestors 7-1-2025 https://dna-explained.com/2025/07/01/jacques-bourgeois-c1620-c1700-surgeon-of-port-royal-52-ancestors-449/
39 TTAM, a Nonprofit Formed by 23andMe’s Founder Now Plans to Buy 23andMe 23andMe 7-1-2025 https://dna-explained.com/2025/07/01/ttam-a-nonprofit-formed-by-23andmes-founder-now-plans-to-buy-23andme/
40 Jacques Bourgeois: Complex Acadian, Founder of Beaubassin – 52 Ancestors #450 52 Ancestors 7-6-2025 https://dna-explained.com/2025/07/06/jacques-bourgeois-complex-acadian-founder-of-beaubassin-52-ancestors-450/
41 How to Use Ancestry’s New Match Clusters and What They Mean Ancestry 7-10-2025 https://dna-explained.com/2025/07/10/how-to-use-ancestrys-new-match-clusters-and-what-they-mean/
42 Walk with Your Ancestors: Peace, Light and Healing in an Abandoned Medieval Village History 7-21-2025 https://dna-explained.com/2025/07/21/walk-with-your-ancestors-peace-light-and-healing-in-an-abandoned-medieval-village/
43 Jeanne Trahan (c1629-c1699), Life in Chinon, La Heve, Port Royal, and Beaubassin – 52 Ancestors #451 52 Ancestors 8-2-2025 https://dna-explained.com/2025/07/28/jeanne-trahan-c1629-c1699-life-in-chinon-la-heve-port-royal-and-beaubassin-52-ancestors-451/
44 Wherefore Art Thou, Oh Ancestor – New Generation Tree Chart Suggests Where to Look in Your Matches’ Trees Techniques, Genetics, Genealogy 8-2-2025 https://dna-explained.com/2025/08/02/wherefore-art-thou-oh-ancestor-new-generation-tree-chart-suggests-where-to-look-in-your-matches-trees/
45 Guillaume Trahan (c1601-1625), More Than Meets the Eye – 52 Ancestors #452 52 Ancestors 8-13-2025 https://dna-explained.com/2025/08/13/guillaume-trahan-c1601-c1684-more-than-meets-the-eye-52-ancestor-452/ 
46 The East Coast Genetic Genealogy Conference – ECGGC – Register Now for the Best of the Best ECGGC Conference 8-14-2025 https://dna-explained.com/2025/08/14/the-east-coast-genetic-genealogy-conference-ecggc-register-now-for-the-best-of-the-best/
47 Schelly Talalay Dardashti – May Her Memory Be a Blessing Memorial 8-17-2025 https://dna-explained.com/2025/08/17/schelly-talalay-dardashti-may-her-memory-be-a-blessing/
48 Francoise Corbineau (c1609-c1665), Bride in Chinon, Founder of Acadia – 52 Ancestors #453 52 Ancestors 8-25-2025 https://dna-explained.com/2025/08/23/francoise-corbineau-c1609-c1665-bride-in-chinon-founder-of-acadia-52-ancestors-453/
49 Nicolas Trahan (c1570->1632), Life in the Heart of French Wine Country – 52 Ancestors #454 52 Ancestors 8-31-2015 https://dna-explained.com/2025/08/31/nicolas-trahan-c1570-1632-life-in-the-heart-of-french-wine-country-52-ancestors-454/
50 Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree, and mtDNA Discover Mitochondrial DNA, Discover, Genealogy, Techniques 10-2-2025 https://dna-explained.com/2025/09/02/mitochondrial-dna-a-z-a-step-by-step-guide-to-matches-mitotree-and-mtdna-discover/
51 Renée Desloges (c1570-1627/1632), Fragments of Life in Montreuil-Bellay – 52 Ancestors #454 (this is actually 455) 52 Ancestors 9-6-2025 https://dna-explained.com/2025/09/06/renee-desloges-c1570-1627-1632-fragments-of-life-in-montreuil-bellay-52-ancestors-454/
52 Best Mitochondrial DNA Presentation EVER – You’re Invited to DNA Academy!! Mitochondrial DNA 9-9-2025 https://dna-explained.com/2025/09/09/best-mitochondrial-dna-presentation-ever-youre-invited-to-dna-academy/
53 Unfillable Shoes Memorial – Douglas Rhodenbaugh 9-14-2025 https://dna-explained.com/2025/09/14/unfillable-shoes/
54 Concepts: What Does a Cousin “Once Removed” Mean? Concepts, Genealogy 9-24-2025 https://dna-explained.com/2025/09/24/concepts-what-does-a-cousin-once-removed-mean/
55 Daniel Vannoy (1752-after 1820), “Lived in the Boundary of the Cherokee Indians” – Say What??? 52 Ancestors 9-29-2025 https://dna-explained.com/2025/09/29/daniel-vannoy-1752-after-1820-lived-in-the-boundary-of-the-cherokee-indians-say-what/
56 Daniel Vannoy and the Strange Case of the Two Sarahs – 52 Ancestors #457 52 Ancestors 10-5-2025 https://dna-explained.com/2025/10/06/daniel-vannoy-and-the-strange-case-of-the-two-sarahs-52-ancestors-457/
57 Cousin Finder – MyHeritage’s Innovative New Tool Finds Your Relatives MyHeritage 10-9-2025 https://dna-explained.com/2025/10/09/cousin-finder-myheritages-innovative-new-tool-finds-your-relatives/
58 Sarah Hickerson Vannoy (c1761 – after 1826), Threw More than Shade – 52 Ancestors #458 52 Ancestors https://dna-explained.com/2025/10/13/sarah-hickerson-vannoy-c1761-after-1826-threw-more-than-shade-52-ancestors-458/
59 MyHeritage Introduces a Low-Pass Whole Genome Autosomal DNA Test & Why It Matters MyHeritage 10-14-2025 https://dna-explained.com/2025/10/14/myheritage-introduces-a-low-pass-whole-genome-autosomal-dna-test-why-it-matters/
60 Henriette Pelletret (c1640 – before 1694), Life Death in the Shadow of the Fort – 52 Ancestors #459 52 Ancestors 10-21-2025 https://dna-explained.com/2025/10/21/henriette-pelletret-c1640-before-1694-life-and-death-in-the-shadow-of-the-fort-52-ancestor-459/
61 Cheat Sheet: Mitochondrial Matches, Haplotype Clusters, and Haplogroups Mitochondrial DNA 10-22-2025 https://dna-explained.com/2025/10/22/cheat-sheet-mitochondrial-matches-haplotype-clusters-and-haplogroups/
62 Simon Pelletret (1610-1642/1645): A Walk Through Port Royal – 52 Ancestors #460 52 Ancestors 10-27-2025 https://dna-explained.com/2025/10/27/simon-pelletret-c1610-1642-1645-a-walk-through-port-royal-52-ancestors-460/
63 Perrine Bourg (c1626-1693/1698): Phoenix Rising from the Ashes – 52 Ancestors #461 52 Ancestors 11-2-2025 https://dna-explained.com/2025/11/02/perrine-bourg-c1626-1693-1698-phoenix-rising-from-the-ashes-52-ancestors-461/
64 Concepts: What is a Half Relationships, Life Half First Cousins, Anyway? Concepts, Genealogy 11-4-2025 https://dna-explained.com/2025/11/04/concepts-what-is-a-half-relationship-like-half-first-cousins-anyway/
65 Marie Broussard (1686-after 1752), Life Across the River from Port Royal – 52 Ancestors #462 52 Ancestors 11-10-2025 https://dna-explained.com/2025/11/10/marie-broussard-1686-after-1752-life-across-the-river-from-port-royal-52-ancestors-462/
66 Francois Broussard (1653-1716), Intractable Acadian – 52 Ancestors #463 52 Ancestors 11-22-2025 https://dna-explained.com/2025/11/22/francois-broussard-1653-1716-intractable-acadian-52-ancestors-463/
67 Mitotree Sprouts 12,773 New Branches and Includes Ancient DNA Mitochondrial DNA 11-24-2025 https://dna-explained.com/2025/11/24/mitotree-sprouts-12773-new-branches-and-includes-ancient-dna/
68 Catherine Richard (c1663 – after 1714), Mother of Beausoleil, Acadian Freedom Fighters – 52 Ancestors #464 52 Ancestors 11-29-2025 https://dna-explained.com/2025/11/29/catherine-richard-c1663-after-1714-mother-of-beausoleil-acadian-freedom-fighters-52-ancestors-464/
69 Ancestry’s ThruLines Has a New Pedigree View Ancestry 12-2-2025 https://dna-explained.com/2025/12/03/ancestrys-thrulines-has-a-new-pedigree-view/
70 Ancestry Reverts ThruLines to the Original View Ancestry 12-6-2025 https://dna-explained.com/2025/12/06/ancestry-reverts-thrulines-to-the-original-view/
71 Michel Richard (c1630-1686/1689), Carefree Acadian – 52 Ancestors #465 52 Ancestors 12-7-2025 https://dna-explained.com/2025/12/08/michel-richard-dit-sansoucy-c1630-1686-1689-carefree-acadian-52-ancestors-465/ 
72 Mitochondrial DNA: How Do I Know if I’m a Candidate to Receive a New Haplogroup? Mitochondrial DNA 12-9-2025 https://dna-explained.com/2025/12/09/mitochondrial-dna-how-do-i-know-if-im-a-candidate-to-receive-a-new-haplogroup/
73 Heavens Ablaze: the 1833 Leonid Meteor Storm and Your Ancestors History, Genealogy 12-15-2025 https://dna-explained.com/2025/12/15/heavens-ablaze-the-1833-leonid-meteor-storm-and-your-ancestors/
74 Madelaine Blanchard (c1643 – 1678/1683), Gone Too Soon – 52 Ancestors #466 52 Ancestors 12-20-2025 https://dna-explained.com/2025/12/20/madelaine-blanchard-c1643-1678-1683-gone-too-soon-52-ancestors-466/
75 Soar Inspiration 12-24-2025 https://dna-explained.com/2025/12/24/soar/

_____________________________________________________________

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