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

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

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

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

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

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

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

RootsTech 2024 – MyHeritage is ON FIRE with 13 Announcements

I’ve got to tell you, MyHeritage has outdone themselves.

I had a hard time just keeping track of their announcements, which totaled 13 – a baker’s dozen.

You can watch the MyHeritage RootsTech keynote by Aaron Godfrey, here.

However, there are a few things not in the video, so let’s take a look at a quick summary of what’s new.

DNA Uploads with Free Advanced Tools Forever Extended Until March 10th

MyHeritage just extended their DNA upload that includes ALL ADVANCED TOOLS FOR FREE, forever, to March 10th so click here now to upload every kit you manage. This is a great deal. Hint – new ethnicity results are coming soon and you’ll be saving $29 on each kit you upload.

20+ Billion Records

MyHeritage has just passed the 20 billion record mark and is continuing to add. That’s billion, with a B. These records are available to customers with a MyHeritage subscription. If you don’t have a subscription, you can try a MyHeritage Subscription with a Free Trial, here.,

Additionally, right now, subscriptions are 50% off, but I don’t know how long that price lasts.

I love my MyHeritage subscription, and if you try it and don’t like yours, you can cancel and be charged nothing during the 14-day trial period.

I particularly like that the local newspaper where my grandparents lived is available on MyHeritage, and no place else. In addition, MyHeritage has integrated with FamilySearch, which is digitizing and indexing records like wildfire. That collaboration has provided me with information from European sources, including archives.

MyHeritage Wiki

MyHeritage has been working on their new Wiki, a community encyclopedia for genealogy and DNA, for almost a year now, although it was only recently released.

Photo courtesy of MyHeritage

I’ve been honored to write several articles for the newly announced MyHeritage Wiki, including the definition of DNA itself:

Take a look at the new Wiki, here.

You can filter in a number of ways, and you can even sign up to be a contributor.

Check out their blog article, here.

AI Record Finder

The AI Record Finder is the world’s first AI chat-based search engine for historical records.

I should probably tell you that, at this point in time, I do use AI, such as ChatGPT, very cautiously, and I’m inherently suspicious because AI tools sometimes hallucinate. It’s a new technology with lots of glitches and unknowns, so let’s see how MyHeritage is using this tool. It should be much more reliable since it’s in a controlled environment. I need to be convinced. 😊

The AI Record Finder is under the Research Menu. Just type your question about your ancestor.

I’m cheating and giving MyHeritage a tough one. I typed, “Please tell me about Solomon Ferwerda, who died in 1768 in Groningen, the Netherlands.”

MyHeritage returned three possibilities in their database, including their affiliated databases. One is a MyHeritage tree and two are records from FamilySearch.

Don’t limit yourself at this point.

I happen to know “my” Solomon is the first person, but I played around a bit before selecting the “right” Solomon. Why? Because there’s a lot that I don’t know about his life. It’s possible that the second and third records are ALSO the right person, so be sure to review everything.

Clicking on the middle or right record for Solomon shows that, indeed, this record from FamilySearch comes from the Dutch Archival Indexes, so it’s not “just someone’s tree.”

We do know the Ferwerda family is from Leeuwarden, but we don’t know when Solomon was born, nor if he was married twice. I only have the name of his second wife and one child, Jan, who was born the year he died.

The two FamilySearch Dutch archive records are from Leeuwarden, so maybe, just maybe, I’ve discovered something new about Solomon. How exciting!

I need to click through and check this out further.

I didn’t expect to like this tool, but so far, I really do. But wait – there’s more.

AI Ancestor Bio

You can click to have MyHeritage generate an AI bio of an ancestor for you.

The bio takes a few minutes to generate and will be available for download in the chat and will also be emailed to you. You can easily share with others. Getting other people interested in genealogy often encourages them to take a DNA test. DNA tests are still on sale for $39, here.

Solomon Ferwerda’s AI bio was completed quickly and arrived in pdf format. We know so little about him, I knew it would be short. I must say, I really enjoyed the “Historical Context” section that discussed the surrounding events that would have affected his life. That’s incredibly important and would have or could have influenced the decisions he made. Maybe the warfare and political unrest caused him to move from Leeuwarden to Groningen for some reason, where he died the year his son was born.

Here’s Solomon’s bio.

Here’s a link to the RootsTech lecture about the MyHeritage AI tools by Ran Snir, the VP of Product.

MyHeritage blog links for AI Record finder are here and here.

You can watch Telling Your Family’s Story with MyHeritage’s AI Features by Janna Helshtein at Legacy Family Tree Webinars, here.

I can’t wait to play with the MyHeritage AI tools more.

Updated Ethnicity Coming Soon

This is going to make a lot of people happy!

MyHeritage is in the process of updating their ethnicity results, increasing their regions from 42 to 80, with significantly optimized granularity in Europe. I initially misunderstood and thought the new results were available now, but they won’t arrive until summer.

I understand from talking to a Jewish friend involved in MyHeritage’s R&D effort that their own results are substantially improved and that they have now been placed in Armenia where their ancestors are from. They are no longer generically “Jewish.”

New Profile Pages with Hints

Daniel Horowitz said that everyone calls Smart Matches and Record Matches hints, so now MyHeritage has updated profile pages and is adding them to the profile page and officially calling them Hints.

You can still find Smart Matches and Record Matches listed separately under Discoveries, but on everyone’s profile, they are called Hints.

On Solomon’s profile page, scroll down to view his journey based on the information you’ve entered or accepted into your tree.

I did not yet add Leeuwarden, because I’m yet positive those records in Leewarden are his, but if I had, Leeuwarden would also be shown on his journey map. I’ll be incorporating these into my 52 Ancestors stories. I love maps! Maybe I can find old maps to include too,

You can read more about the new profiles and hints, here.

Tree Collaboration with FamilyTreeDNA

Aaron Godfrey announced tree collaboration with FamilyTreeDNA who pre-announced this at their conference in November.

I don’t have specific details about how it works, as this won’t happen for a few months yet, but FamilyTreeDNA customers will port their trees to MyHeritage which allows them to take advantage of MyHeritage’s record collections and such. Existing MyHeritage customers will simply connect their FamilyTreeDNA test to their MyHeritage tree.

FamilyTreeDNA has never been a “tree” company, so this means that users will have one less tree to maintain independently, and they can augment their research with records from MyHeritage.

I talked to Katy Rowe-Schurwanz, the Product Manager at FamilyTreeDNA to confirm that this is NOT a DNA transfer. FamilyTreeDNA matches still occur in the FamilyTreeDNA database, just like always, and MyHeritage matches still occur in the MyHeritage database. If you want matching in both databases, you still have to upload to or test at both. Only the trees are integrated, meaning when you click on a tree at  FamilyTreeDNA, you’ll see the tree displayed on MyHeritage.

The great news is that FamilyTreeDNA features such as Family Matching (bucketing) where you link your DNA matches at FamilyTreeDNA to their profile cards so that maternal/paternal bucketing occurs will still work the same way. The only difference will be that your tree will actually reside at MyHeritage and not at FamilyTreeDNA.

You’ll be able to enjoy the best of both worlds.

We will know more in a few months, and I’ll provide more details when I have them.

Invite Another MyHeritage User to View Your DNA Results

Aaron Godfrey said in the keynote that 2FA (two-factor authentication) at MyHeritage will become mandatory later this month, and with it, MyHeritage is adding the feature of being able to invite another MyHeritage user to view your DNA results. This allows people to collaborate more easily, especially if a different person is managing someone else’s DNA test.

Reimagine Multi-Photo Scanner App

This photo-scanning innovation is for your phone and allows you to scan photos and entire photo album pages – automatically separating and improving the photos. Then, of course, you just tag them to the proper person in your tree like any other photo.

Oh, and did I mention that Reimagine is free? I expected to have to pay when I downloaded the app, but I didn’t, probably because I have a full subscription.

Based on this article, Reimagine is not meant for other types of images, like pages of text or albums of clipped newspaper articles. But guess what? I downloaded the app, and it works just fine for those items! Hallelujah. How I wish I had this last week at the FamilySearch Library when I was finding pages in books I wanted to associate with a specific ancestor.

If you have album pages of photos to scan, this is golden and integrates with the profiles of people into your MyHeritage tree.

I really, really like the idea of having the ability to scan in the palm of my hand. That way if someone has a photo, you don’t have to try to take a photo of it. Gone are the days of literally dragging a laptop and scanner around with me when I’m traveling – just in case. Yes, I actually did and now I don’t have to anymore.

I cringe to think how many opportunities were lost to me before the days of laptops – but not now.

Thank you – THANK YOU, MyHeritage. What a great gift!

You can find the QR code to download the app, here.

OldNews is New News

MyHeritage has introduced a new website for old newspapers called OldNews which you can find here.

This addition doubles the number of newspapers previously available on MyHeritage.

Users can also subscribe separately to Old News for about $99/year.

MyHeritage customers use their normal credentials to sign in to either site, but accessing newspapers not previously integrated into MyHeritage will require an OldNews subscription too.

I had to try it. I entered my mother’s name.

Look, my Mom had a tonsillectomy. I never knew that. It was just a couple of months after she graduated from high school.

I didn’t know Mom spent the summer in Philadelphia, either. She was 19 at that time, and I had heard rumblings that she studied with a “prima ballerina” at the School of American Ballet. Guess where that is? Yep, Philly.

My Mom was a professional tap and ballet dancer before she became my Mom.

Understanding that Mom spent the summer of 1942 on the east coast sheds new light on this and a few other photos in Mom’s photo album, which I can now scan.

Ok, I can’t help myself. I have to enhance this photo at MyHeritage.

Much better. Another tiny piece of Mom’s life brought into focus.

I wonder what else is in OldNews that I don’t know about. Hmmmm…

You can read about OldNews here.

New All-Inclusive Omni Subscription

MyHeritage is launching a new Omni all-inclusive subscription plan that includes most of the MyHeritage products and tools, except for Filae, unless I’m missing something. Omni reportedly costs less than half the price if you were to subscribe to all of these individually. I’ve asked for a comparison chart which I don’t have yet, but I’m told will be coming soon.

Here’s what’s included:

Additionally, I asked MyHeritage about whether or not the advanced DNA tools are included with Omni, and they are. So, add advanced DNA tools to that list.

The following information about the Omni Plan is a screenshot from the MyHeritage blog article, here.

I have not been able to determine the price of an Omni subscription. At RootsTech, you were interested in the Omni plan, you submitted a Google form and a day or so later, you received this email.

I suspect MyHeritage needs to talk to you because how much it costs initially depends on your existing subscriptions, and how much time is left on those.

I reached out to MyHeritage and asked when Omni will be available to purchase, and the answer is “soon.” You can’t sign up just yet.

I have never subscribed to Legacy Family Tree Webinars, even though I’m a webinar presenter and have several webinars available there. My gift to myself is going to be Omni when it’s available because I want Legacy Family Tree Webinars, and I’d love a subscription to OldNews. I already have a full subscription to MyHeritage, and I’d probably use Geni more than I do as a casual user if I had the Omni subscription.

Artifact Testing – Maybe

Unfortunately, I was not able to attend CEO Gilad Japhet’s RootsTech session because his session and mine were at exactly the same time.

However, I asked Aaron Godfrey after Gilad’s session what I had missed that was not in Aaron’s keynote, other than Gilad’s wonderful stories.

Aaron and others told me that Gilad stated that he was personally submitting personal artifacts, such as stamps, to a third-party lab once again, to test the waters to see if DNA can now be extracted from artifacts successfully.

MyHeritage tried this a few years ago, ultimately unsuccessfully. Perhaps this time will be different, but I would not hold my breath, truthfully. Degraded DNA has quality issues, not to mention that the DNA extracted might not be the DNA of the person expected.

I would personally love this, but I am also skeptical at this point. Kudos to Gilad for trying again with his own personal items.

MyHeritage Online RootsTech Booth

MyHeritage has provided several educational videos in their online RootsTech booth, at this link. Be sure to take advantage of this free resource.

Whew, I’m finally done! I told you that MyHeritage had been very, very busy, and I wasn’t kidding. I hope I didn’t miss anything.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Pedigree Collapse and DNA – Plus an Easy-Peasy Shortcut

Pedigree collapse can be responsible for you sharing more DNA than expected with another person.

What is pedigree collapse?

Pedigree collapse occurs when you descend from the same ancestor(s) through more than one path. In other words, you descend from those ancestors through two different children. Therefore, when matching with someone else who descends through those ancestors, you may share more DNA than would be expected from that level of relationship on the surface, meaning without pedigree collapse.

Endogamy is different and means that you descend from a community of ancestors who descend from the same group of ancestors. Often out-marriage is discouraged or otherwise impossible, so all of the group of people share common ancestors, which means they often match on segments without sharing close ancestors. Examples of descent from endogamous populations are Jewish, Amish, Brethren, Acadian, Native Hawaiian, Māori, and Native American people, among others.

I wrote about the difference between pedigree collapse and endogamy in the article, What’s the Difference Between Pedigree Collapse and Endogamy?

I’ve also written about endogamy in the following articles:

Degrees of Consanguinity

If you’re a genealogist, and especially if you’ve worked with Catholic church records, you’ve probably heard of “degrees of sanguinity,” which are prohibited blood relationships in marriage. For example, siblings are prohibited from marrying because they are too closely related, according to church doctrine.

By SVG remake by WClarke based on original by User:Sg647112c – Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=54804980

Today, we think of the genetic results of inbreeding, but originally, relationships (and consanguinity) also had to do with inheritance.

Essentially, marriages are prohibited by degree of sanguinity, and that degree is calculated based on this relationship chart. Prohibited degrees of consanguinity changed over time. Sometimes, a priest granted dispensation for a couple to wed who was of a prohibited degree of sanguinity. That’s a genealogy goldmine because it tells you where to look for common ancestors. It also tells you something else – that you may share more DNA with other descendants of that couple than one would otherwise expect.

More Than You Ever Expected

Recently, I’ve been working with an academic research team on a very interesting ancient DNA case that involves pedigree collapse. Doing the genealogy and genetic work on how much DNA was expected in a match without pedigree collapse, and how much was expected with pedigree collapse, was very interesting.

The team was working to confirm relationships between people in a cemetery. The burials shared more DNA than anticipated for who the people were believed to be. Enter pedigree collapse.

I can’t disclose the circumstances just yet – but I will as soon as possible. It’s an extremely interesting story.

We needed to ensure that readers, both academic and more generally understood pedigree collapse and our calculations. Why did burials share higher than expected DNA than indicated by the expected relationships? This puzzle becomes much more interesting when you add in pedigree collapse.

Academic researchers and scientists have access to models and mathematical algorithms that normal air-breathing humans don’t have easy access to.
So, what do you do if you and a match have a known pedigree collapse in your tree? How much DNA can you expect to share, and how do you calculate that?

These are all great questions, so let’s take a look.

I’m sharing the PowerPoint slides I prepared for our team on this topic. I’ve removed anything that would identify or even hint at the project and modified the slides slightly for easier consumption.

This presentation has never been given publicly, so you’re first! It seemed a waste to do this work and not share it!

Pedigree Collapse and DNA

Pedigree collapse occurs when you share an ancestor or ancestors through different pathways. In this case, the person at the bottom is the child of parents who were third cousins, but the father’s grandparents were also first cousins.

First cousin marriages were common in the not-too-distant past. Today, you could easily marry your third or fourth cousin and not even realize it unless someone in your family just happened to be a genealogist.

Genealogists use various tools to calculate the expected amount of shared DNA in relationships – first cousins, siblings, or half-siblings, for example. Both the Shared cM Project at DNAPainter and SegcM at DNA-Sci Tools provide tools.

Take a look at the article, DNA: In Search of…Full and Half-Siblings, for some great examples.

First cousins share common grandparents. Their child inherits DNA from two paths that lead back to the same ancestors. Some of that DNA will be the same, meaning the child will or can inherit the same ancestral segment from both parents, and some will be different segments from those ancestors that the parents do not share with each other.

Inheritance – How It Works

Let’s look at inheritance to see how this happens.

Let’s start with full and half-siblings.

Each child inherits half of their DNA from each parent, but not entirely the same half (unless they are identical twins.)

Therefore, full siblings will match on about 50% of their DNA, which is illustrated by the segments on the chromosome browser. However, and this will be important in a minute, about 25% of their DNA is exactly the same, when compared to each other, on the chromosome inherited from their father and mother at the same location.

On the chromosome browser, you can see that three siblings do match. One sibling (the grey background chromosomes) is the person both other full siblings are being compared to, in the example above.

What you can’t determine is whether they share the exact same DNA on both their mother and father’s Chromosome 1, where the matches overlap, for example. We know they both match their sibling, but the top person could match the sibling due to a match from their paternal chromosome in that location, and the bottom person could match due to their maternal chromosome. There’s no way to know, at least not from that view.

The areas where the siblings share exactly the same DNA on both their maternal and paternal chromosome, both, with each other are called Fully Identical REgions (FIR), as compared to Half Identical Regions (HIR) where the siblings match on either their maternal or paternal copy of the chromosome, but not both.

23andMe used to provide a tool that displayed both types of matches.

Since the data exposure incident at 23andMe, they no longer provide this lovely tool, and since that help page is now gone as well, I doubt this view will ever be returned. Fortunately, I grabbed a screenshot previously.

The dark purple segments are fully identical, meaning that these two full siblings match on both their maternal and paternal chromosomes in that location. The magenta are half identical, which means they match on EITHER the maternal or paternal chromosome in that location but not on both chromosomes. Of course, no color (light grey) means there is no match at that location.

Please note that because 23andMe counts fully identical regions (FIR) twice, their total matching cMs are elevated. The other companies do NOT count those regions twice.
GEDmatch also shows both full and half-identical regions as described more fully, here.

In this full-sibling example from GEDmatch, the green segments are fully identical regions across both the maternal and paternal chromosomes.

The definition of FIR is that two people match on both their mother’s and father’s DNA on the same chromosome. Therefore, in following generations, there technically should not be FIR matches, but in some instances we do find FIR matches outside of full siblings.

Moving down another generation, first cousins may share SOME fully identical DNA, especially if they are from an endogamous population or their mothers are related, but less, and it’s generally scattered.

Here’s my Mom’s GEDmatch comparison to her first cousin. The purple-legend segment shows a match, and the green within that match shows fully identical locations.

You can easily see that these are very scattered, probably representing “chance” or population-based fully identical matching locations within a segment. Comparatively, the green FIR segments for full siblings are dense and compact, indicating a segment that is fully identical.

Evaluating matches for dense FIR segments (known as runs of homozygosity – ROH) is a good indicator of parental relatedness.

Double Cousins

Of course, if these people were double first cousins, where the wives of the siblings were sisters to each other – the first cousins would have large patches of dense green FIR segments.

First cousins share grandparents.

Double first cousins occur when two people share both sets of grandparents, meaning that brothers marry sisters. Normal first cousins share about 12.5% of their DNA, but double first cousins share about 25% of their DNA.

In this case, Sharon and Donna descend from two brothers, James and Henry, who were sons of Joseph and Jane. In this scenario, James and Henry married unrelated women, so Sharon and Donna are first cousins to each other.

Double first cousins share both sets of grandparents so they would inherit FIR from both sets of siblings.

You need to be aware of this, but for now, let’s stick with non-double relationships. You’re welcome!

DNA Inheritance

Here’s a different example of DNA inheritance between two siblings.

  1. You can see that in the first 50 cM segment, both siblings inherited the same DNA from both parents, so they match on both their mother’s and father’s chromosomes. They match on both the 50 cM green and 50 cM pink segments. 23andMe would count that as 100 cMs, but other vendors only count a segment IF it matches, NOT if it matches twice. So, other vendors count this as a 50 cM match.
  2. In column two, these two people don’t match at all because they inherited different DNA from each parent. In this example, Person 1 inherited their maternal grandmother’s segment, and Person 2 inherited their maternal grandfather’s segment.
  3. In column three, our siblings match on their paternal grandmother’s segment.
  4. In column four, no match again.

How much can we expect to inherit at different levels – on average?

Different tools differ slightly, and all tools provide ranges. In our example, I’ve labeled the generations and how much shared DNA we would expect – WITHOUT pedigree collapse.

Ancestral couple Inherited cM Inherited %
Gen 1 – Their children 3500 cM 50
Gen 2 – Grandchildren 1750 cM 25
Gen 3 – Great-Grandchildren 875 cM 12.5
Gen 4 – GG-Grandchildren 437.5 6.25
Gen 5 – GGG-Grandchildren 218.75 3.125
Gen 6 – GGGG-Grandchildren 109.375 1.5625
Gen 7 – GGGG-Grandchildren 54.6875 .078125

Please note that this is inherited DNA, not shared (matching) DNA with another person.

Adding in pedigree collapse, you can see that we have three Gen 1 people involved, three Gen 2 descendants, and two Gen 3 and Gen 4 people.

Each of those people inherit and pass on segments from our original couple at the top.
We have three distinct inheritance paths leading from our original couple to Gen 5.
We have a first cousin marriage at Gen 2, at left, which means that their child, Gen 3, will have an elevated amount of the DNA of their common ancestors.

In Gen 4, two people marry who both descend from a common couple, meaning their child, Gen 5, descends from that couple in three different ways.

Did your eyes just glaze over? Well, mine did, too, which is why I had to draw all of this out on paper before putting it into PowerPoint.

The Gen 5 child inherits DNA from the ancestral couple via three pathways.
The next thing to keep in mind is that just because you inherit the DNA from an ancestor does not mean you match another descendant. Inheritance is not matching.

You must inherit before you can match, but just because you and someone else have inherited a DNA segment from a common ancestor does not guarantee a match. Those segments could be in different locations.

Categories of DNA

When dealing with inheritance and descent, we discuss four categories of DNA.

  • In the first generation, full siblings will, in about 25% of their locations, share the same DNA that has been inherited from both parents on the same chromosome. In other words, they match each other both maternally and paternally at that location. Those are FIR.
  • The DNA you inherit from an ancestor.
  • The DNA that both you and your cousin(s) inherit from a common ancestor and match on the same location. This is shared DNA.
  • The DNA that both you and your cousin(s) inherit from a common ancestor, but it’s not in the same location, so you do not match each other on that segment. Just because you inherit DNA from that ancestor does not necessarily mean that your cousin has the same DNA from that ancestor. This is inherited but not shared.

Inheritance is Not The Same as Matching

Inheritance is not the same thing as matching.

Inheriting our ancestor’s DNA isn’t enough. We need to match someone else who inherited that same segment in order to attribute the segment to that specific ancestor.

Depending on how close or distant the relationship, two people may share a lot of DNA (like full siblings), or one segment in more distant matches, or sometimes none at all. As we reach further back in time, we inherit less and less of our increasingly distant ancestors’ DNA, which means we match increasingly fewer of their descendants. I wrote about determining ancestral percentages in the article,  Ancestral Percentages – How Much of Them is in You?

Based on how much DNA we share with other known relatives, we can estimate relationships.

Pedigree collapse, where one descends from common ancestors more than once, increases the expected amount of inherited DNA, which in turn increases the probability of a shared match with other descendants.

Ancestral Couple Matching Between Shared DNA ~cM Shared DNA ~% Range (Shared cM Project) FIR – Identical DNA
Generation 1 Full Siblings 2600 50 1613-3488 25%
Generation 2 First Cousins 866 12.5 396-1397 0
Generation 3 Second Cousins 229 3.125 41-592 0
Generation 4 Third Cousins 73 0.78125 0-234 0

Here’s an example through third cousins, including expected FIR, fully identical regions where full siblings match each other on both their maternal and paternal chromosomes in the same location.

I provided a larger summary chart incorporating the information from public sources, here, minus FIR.

Of course, double cousins, where two pairs of siblings marry each other, represent another separate level of complexity. DNA-Sci’s Double Cousin Orogen explains this here and also provides a tool.

Double cousins, meaning when two pairs of siblings marry each other, are different from doubly related.

Doubly related means that two people descend from common ancestors through multiple paths, meaning multiple lines of descent. Doubly related is pedigree collapse. Double cousins is pedigree collapse on steroids.

Pedigree Collapse, aka Doubly Related

Calculating expected inherited DNA from multiple lines of descent is a bit more challenging.

A handy-dandy chart isn’t going to help with multiple relationships because the amount of expected shared DNA is based on the number of and distance of relationships.

Please note that this discussion excludes X-DNA matching which has its own inheritance path.

It’s time for math – but I promise I’ll make this relatively easy – pardon the pun.

What’s Behind the Math?

So, here’s the deal. I want you to understand why and how this works. You may not need this information today, but eventually, you probably will. This is one of those “refer back to it” articles for your personal library. Read this once as a conceptual overview, then read it again if you need to work through the relationships.

This is easy if you take it one step at a time.

First, we calculate each path separately.

In the first generation, full siblings inherit identical (FIR) DNA on both their mother’s and father’s chromosomes.

In the second generation, the male inherits the maternal segment, and the female inherits the paternal segment.

In the third generation, their child inherits those segments intact from both of their parents. The child inherits from the ancestral couple twice – once through each parent.

In generation 1, those two segments were FIR, fully identical regions. Both of those men married unrelated wives. When their children, Gen 2, were born, they had either the maternal or paternal segment from their father because they had an entirely different segment in that location from their mother.

However, the child in Gen 3 inherited the original green segment from their father and the original pink segment from their mother – reuniting those FIR segments in later generations.

First Cousin’s Child

Let’s calculate the inheritance for the child of those two first cousins who married.

Ancestral couple Inherited cM Inherited %
Gen 3 – Great-Grandchildren 875 cM 12.5
Gen 3 – Great-Grandchildren 875 cM 12.5
Total 1750 cM 25

Normally, a Gen 3 person inherits roughly 875 cM, or 12.5% of their great-grandparent’s DNA. However, since their grandparents were first cousins, they inherit about twice that amount, or 1750 cM.

While a Gen 3 person inherits as much as a grandchild (25%) normally would from the original couple, they won’t match on all of that DNA. When matching, we need to subtract some of that DNA out of the equation for two reasons:

  • In the first generation, between siblings, some of their DNA was fully identical and cannot be identified as such.
  • In the second generation, they will each have some parts of the ancestral couple’s DNA that will not match the other person. So, they inherit the same amounts from their common ancestors, but they can only be expected to match on about 25% of that amount two generations later.

However, the child of first cousins who marry inherits more DNA of the common ancestors than they would if their parents weren’t related. It’s just that some of that DNA is the same, potentially on the maternal and paternal chromosomes again, and some won’t match at all.

While matching DNA is the whole point of autosomal DNA testing, fully identical DNA matching regions (FIR) cannot be identified that way. For the most part, other than identifying full and half-siblings, sometimes pedigree collapse, and parent-relatedness, fully identical DNA isn’t terribly useful for genealogy. However, we still need to understand how this works.

It’s OK if you just want to say, “I know we’ll share more DNA due to pedigree collapse,” but if you want to know how much more to expect, keep reading. I’d really like for you to understand use cases and be able to track those segments.

Remember, we will learn a super-easy shortcut at the end, so for now, just read. It’s important to understand why the shortcut works.

Sibling Inheritance Versus Matching

In order to compare apples to apples, sometimes we need to remove some portion of DNA in our calculations.

Remember story problems where you had to “show your work”?

Calculating Expected DNA

Here’s the step-by-step logic.

Ancestral couple Inherited Non-Identical cM Inherited %
Gen 1 first son 3500 50
Gen 1 second son 3500 50
Less identical segments (FIR) -1750 (subtracted from one child for illustration) 25
Gen 2 son 1750 25
Gen 2 daughter married Gen 2 son 875 12.5
Gen 3 – Their child path through Gen 2 son 875 cM 12.5
Gen 3 – Their child path through Gen 2 mother 437.5 cM 6.25
Their child total without removing identical segments 1750 cM 25
Their child total after removing identical segments 1312.5 18.75

Category cMs Most Probable Degree Relationship
No Pedigree Collapse 875 98% Great grandparent or great-grandchild, great or half aunt/uncle, great or half niece/nephew, 1C 3
Pedigree Collapse without identical segment removal 1750 100% Grandparent, grandchild, aunt/uncle, half-sibling, niece/nephew 2
Pedigree Collapse after identical segment removal 1312.5 56% grandparent, grandchild, aunt/uncle, niece/nephew, half-sibling 2

Just because you HAVE this much shared (and/or identical) DNA doesn’t mean you’ll match on that DNA.

Next, let’s look at Gen 5 child who inherited three ways from the ancestors.

If you think, “This will never happen,” remember that it did, which is why I was working through this story problem. It’s not uncommon for families to live in the same area for generations. You married who you saw – generally, your family and neighbors, who were likely also family.

Let’s take a look at that 5th generation child.

The more distantly related, the less pedigree collapse affects matching DNA. That’s not to say we can ignore it.

Here’s our work product. See, this isn’t difficult when you take it step by step, one at a time.

Ancestral couple Inherited Non-Identical cM Inherited %
Gen 3 Child total after removing identical segments 1312.5 18.75
Gen 4 father – half of Gen 3 father 656.25 9.375
Gen 5 child – half of Gen 4 father 328.125 4.6875
Gen 5 child – mother’s side calculated from ancestral couple normally 218.75 3.125
Total for Gen 5 Child 546.875 7.8125

Inheritance Ranges

Lots of factors can affect how much DNA a person in any given generation inherits from an ancestor. The same is true with multiple paths from that same ancestor. How do we calculate multiple path inheritance ranges?

As with any relationship, we find a range, or combined set of ranges for Gen 5 Child based on the multiple pathways back to the common ancestors.

Gen 5 Child Inherited Non-Identical cM Inherited %
Without removing either paternal or maternal identical cMs 656.25 9.375
After removing paternal identical cMs only 546.875 7.8125

 

After removing maternal cMs only 546.875 7.8125

 

After removing both paternal and maternal identical cMs 362.50 6.25
Normal Gen 5 no pedigree collapse 218 3.125

What About Matching?

Inheritance and matching are different. Most of the time, two people are unlikely to share all of the DNA they inherited from a particular ancestor. Of course, inheriting through multiple paths increases the likelihood that at least some DNA from that ancestor is preserved and that it’s shared with other descendants.

Two people aren’t expected to match on all of the segments of DNA that they inherit from a particular ancestor. The closer in time the relationship, the more segments they will inherit from that ancestor, which increases the chances of matching on at least one or some segments.

Clearly, pedigree collapse affects matching. It’s most pronounced in closer relationships, but it may also be the only thing that has preserved that ONE matching segment in a more distant relationship.

So, how does pedigree collapse actually affect the likelihood of matching? What can we actually expect to see? Is there a name for this and a mathematical model to assist with calculations?

I’m so glad you asked! It’s called Coefficient of Relationship.

Coefficent of Relationship

My colleague, Diahan Southard, a scientist who writes at YourDNAGuide has authored two wonderful articles about calculating the statistical effects of pedigree collapse.

You can also read another article about the methodology of calculating coefficient of relationship, here, on WaybackMachine.

Diahan is a math whiz. I’m not, so I needed to devise something “quick and dirty” for my own personal use. I promised you a “cheat sheet,” so here’s the methodology.

Two Inheritance Paths – First and Third Cousins

Let’s look at an example where two people are both first cousins and third cousins because their grandparents were also first cousins.

Let’s calculate how these two people are related. They are first cousins and also third cousins.

When calculating the effects of pedigree collapse, we calculate the first relationship normally, then calculate the second relationship and add a portion of the result.

Here’s the math.

Using the Shared cM Project for the expected amount of shared DNA for both relationships, we’ve calculated the expected range for this pedigree collapse relationship.

Tying this back to degrees of relatedness.

Let’s look at ways to do Quick Calculations using the publicly available Shared cM charts and my composite tables, here.

Using Average Shared DNA

This first methodology uses average expected amount of shared, meaning matching, DNA. Please note, I’m not necessarily expecting you to DO this now, just read to follow.

Using Average Inherited DNA

Here’s a second method using average inherited DNA, meaning people wouldn’t be expected to match on all of the inherited DNA – just a portion.

You can’t always use the shared cM charts because all relationships aren’t represented, so you may need to use the amount of expected inherited DNA instead of shared DNA amounts.

Methodology Differences

Remember, none of these methodologies are foolproof because DNA inheritance is random. You may also have additional relationships that you’re aware of.

So, what’s the easiest method? Neither, actually. I’ve found an even easier method based on these proven methodologies.

Easy-Peasy Pedigree Collapse Shortcut Range Calculation in 4 Steps

Now that you understand the science and reasoning behind all of this, you can choose from multiple calculation methodologies after drawing a picture of the relevant tree.

You’re probably wondering, “What’s the easiest way to do this?”

  • These quick calculation methods are the easiest to work with for non-scientists and non-math whizzes. These are the calculations I use because, taking into account random recombination, you can’t do any better than get close.
  • Also, remember, if you’re dealing with double relationships, meaning double first cousins, you’ll need to take that into consideration, too.
  • If endogamy is involved, your matches will be higher yet, and you should use the highest calculations below because you need to be on the highest end of the range – and that may still not be high enough.

In these Easy-Peasy calculations, you calculate for the lowest, then the highest, and that’s your range. Please note that these are options, and truly, one size does not fit all.

  1. For the lowest end of the range, simply use the average of the highest relationship. In this case, that would be 1C, which is 866 cM. Remember that you may not share DNA with third cousins. 10% of third cousins don’t share any DNA, and 50% of fourth cousins don’t.
  2. For the highest end of the range, find the second relationship in the Shared cM chart, divide the average by half, and add to the value from the closest relationship. In this case, half of the 3C value of 76 is 38.
  3. Add 38 to 866 for the highest end of the range of 904.
  4. If there’s yet another path to ANY shared ancestor, add half that amount too to calculate the high end of the range – unless it’s 4C or more distant, then don’t add anything.

You can see that this easy-peasy range calculation for pedigree collapse compares very well to the more complex but still easy calculations.

  • Easy-peasy calculation: 866-904
  • Other calculation methods: 850-903
  • For this same relationship combination, Diahan’s statistical calculation was 850 cM.

Back to Genealogy

What’s the short story about how pedigree collapse affects genealogy?

Essentially, in close generations, meaning within a few generations of two first cousins marrying, descendants can expect to inherit and share significantly more DNA of the common ancestors, but not double the amount. As we move further away from those marriages in time, the effect becomes less pronounced and more difficult to detect. You can see that effect when calculating multiple paths where at the fourth cousin level, or more distant, those cousins have a 50% or greater possibility of not sharing DNA segments.

Of course, with multiple paths to the same ancestor, your chances of inheriting at least some segments from the common ancestor are increased because their DNA descends through multiple paths.

Today, close marriages are much less common and have been for several generations in many cultures, so we see fewer instances where pedigree collapse makes a significant difference.

Within a population or group of people, if pedigree collapse becomes common, meaning that there are multiple paths leading back to common ancestors, like our three-path example, DNA segments from the common ancestors are found among many people. Significant pedigree collapse becomes endogamy, especially if marriage outside of the group is difficult, impossible, or discouraged.

Normally, pedigree collapse is not recorded in actual records. It’s left to genealogists to discover those connections.

The exception, of course, is those wonderful Catholic parish records where the priest granted dispensations. Sometimes, that’s our only hint to earlier genealogy. In the case of the marriage of Marie-Josesphe LePrince to Jacques Forest, the priest wrote “dispense 3-3 consanguinity,” which tells us that they shared great-grandparents. It also tells us that their grandparents were siblings, that the bride and groom were second cousins, and that their children and descendants inherited an extra dose of DNA from their common great-grandparents.

How does that affect me today? Given that I’m their seventh-generation descendant – probably not at all. Of course, they are Acadian, and the Acadians are highly endogamous, which means I match many Acadians because all Acadians share the DNA of just a few founders, making it almost impossible to track segments to any particular ancestor. If it weren’t for endogamy, I would probably match few, if any, of their descendants.

Now, when you see those Catholic church dispensations or otherwise discover pedigree collapse, you can be really excited, because you understand the effects of pedigree collapse and how to calculate resulting matches! You might, just might, have retained a DNA segment from those ancestors because you inherited segments through multiple paths – increasing the probability that one survived.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Bennett Greenspan: Meet My Extended Family & Discover Extraordinary Deep Heritage

“My ancestors are in my soul. I can’t get them out of my mind.”

Bennett Greenspan

“And yes, I brake for cemeteries.”

Bennett Greenspan gave an incredibly interesting presentation at the 15th International Genetic Genealogy Conference held by FamilyTreeDNA in November 2023. Since his retirement in January 2021, he has been able to focus on his genealogy. Once a genealogist, always a genealogist.

Bennett said some things I hadn’t thought about, and now I’m viewing Y-DNA matches with a different perspective – based on how he’s using his results.

Ever since I met him, Bennett’s focus has been to use genetics to unravel his complex Jewish heritage.

The questions that drive Bennett are the same ones that motivate most genealogists:

  1. Who are we?
  2. Where did we come from?
  3. Where were we before we were there?
  4. How did my ancestors get there?

Bennett “lost his family lines” before the mid-1800s due to his Jewish heritage, exacerbated in the 1930s by the devastation wrought by the Holocaust. Families were either killed or scattered to survive. It has been through Y-DNA in particular that he has been able to establish unquestionable and confirmed connections with other Greenspan men, sometimes by similar but different surnames, like Green, and sometimes with other surnames entirely.

When Bennett first started down this path, he tested more than 62 men before actually finding one a decade later that matched his Y-DNA. Bennet commented that it was “a little frustrating.”

Persistence is the key, and sometimes, genealogy is a waiting game, but that’s small comfort to genealogists during that unproductive waiting period.

Eventually, Bennett reassembled his family, at least somewhat, but it was a long journey. Here’s Bennett’s incredible story, including surprises, as he tells it.

Bennett discovered genealogy at age 12 and, like many genealogists, created a pedigree chart by talking to his family.

I love the mark-outs. How many of us still have our first chart with its edits?

This is the young Bennett Greenspan, whose interest in genealogy would one day unlock secrets for all of us!

It was a long way from a decade with no matches to finding his genetic kin in Ukraine.

The Big Y-700 Time Tree shows Bennett’s lineage in Ukraine, but stepping back in time, some descendants of his ancestors are found in adjacent locations.

Bennett was passionately discussing his matches on the time tree and in the Greenspan project, so I visited the Greenspan DNA Project, where the earliest known ancestors of Bennett’s Big Y matches are shown on the Group Time Tree.

Bennett’s closest matches are shown as descendants of haplogroup J-ZS1718. He has additional matches who are not in the Greenspan project. Since this is the Group Time Tree, it only displays the people in that project, along with their earliest known ancestors, Isaac and Usher Greenspan.

12-Marker Matches

Bennett never fails to amaze me. He said something very important and profound about 12-marker matches that I really hadn’t thought about – at least not this way.

As a community, we are often guilty of discounting 12-marker matches, those that don’t match us at 25-markers or above, or with different surnames, as “too far back in time” or otherwise irrelevant. I always look at the names and earliest known ancestors of 12-marker matches, because that person may have tested back in the day when fewer markers were available. But if I don’t recognize something, I move on.

However, Bennett said that, ”Y-12 matches reach back to a common ancestor. 12-marker matches are not a quirk. They are related to you, just further back in time. You share a common ancestor with them, someplace. They may be more distant, but they are still your close matches.”

I’ve been in too much of a hurry for a quick win, and ignoring the (apparently not so) obvious.

Determining when and where their ancestors lived also paves the way to discover yours. Your Y-DNA and theirs were in the same place at the same time.

Of Bennett’s 171 12-marker matches, 107 have upgraded to the Big Y, probably mostly due to his encouragement. This benefits both them and Bennett by fleshing out the history of that entire group of men, including how they got to where they are found in the first available records. The Time Tree shows when Big Y testers shared a common ancestor, and based on Earliest Known Ancestor (EKA) locations, where. This provides further information about the lives of ancestors before contemporary records – in other words – people that we can never identify by name. It’s a window into ancestors before surnames.

Bennett notes that testers need to know their ancestral village or location to be most useful within the project, and of course, they need to enter their EKA information. Location information is how the Migration Map, Matches Map, and Discover tools, including the Time Tree, are built.

What Happened in Spain?

Bennett’s ancestors and those of his 12-marker matches are found in Spain, and as Bennett says, “One son stayed and one left about the year 296.”

While we have no idea of their names, based on the Time Tree combined with the cluster of earliest known ancestors, we know that they were in Spain, and when.

Their family story is revealed in the bifurcation of the tree found beneath haplogroup J-L823, formed about 296 CE. One line stayed in Spain, and Bennett’s line migrated to eastern Europe where that man’s descendants, including Bennett’s family, are found in the Russian Federation, Belarus, Poland, Lithuania, Sweden, Slovakia, Ukraine, Germany, Romania, the Czech Republic, and other eastern European locations. The closer to you in the tree and in time, the more relevant to your more recent ancestral story.

However, Bennett’s deeper ancestry, the migration of his ancestors to Spain, was only revealed by testing those more distantly related men. Those same men could well have been ignored entirely because they only matched at 12 markers.

According to Bennett, “Y-12 markers are important because these are the men most closely related to you in a database of 1 million men.”

How incredibly profound. How much have I been cavalierly overlooking?

How does this actually apply to Bennett’s results?

Bennett’s Spanish Matches

Bennett has the following STR panel matches who indicate that their EKA are from Spain. You can see that they match Bennett on a variety of panels.

  • X = yes, match
  • No = no match
  • Blank = not tested at that level.

In the Big Y GD column, the genetic distance (GD) is displayed as 15/660 where 15 is the number of mismatches, or the cumulative genetic distance ABOVE the 111 panel, and 660 is the number of STR markers above 111 with results.

The Big Y-500 test guaranteed a minimum of 500 total STR markers, and the Big Y-700 guarantees a minimum of 700 total STR markers, plus multiple scans of the balance of the Y chromosome for SNP mutations that define haplogroups. Testers don’t receive the same number of markers because the scan technology sometimes doesn’t read a specific location.

Tester 12 25 37 67 111 Big Y Test Big Y GD Big Y Match Haplogroup
AA X X X No No Yes 15/660 No J-FTD8826
DT X X No No X Yes 17/664 No J-FTE50318
JG X X No No
AR No No X X No No
ELR X X X No No
EL X X Yes 17/666 No J-FTE50318
GC X X X X No No
JC X No No
JLG X X No No No Yes 14/662 No J-FTE23540
MF X X No X No Yes 15/665 No J-FTD91126
MT X X X X No No
BE X X X X X Yes 20/664 No J-BY1795
DR X X X X X Yes 16/660 No J-FTC87344
EC X X X X X Yes 15/665 No J-FTC87344
GM X X No No No Yes 16/650 No J-FTD28153
GM X X X X No Yes 17/664 No J-FTD11019
LS X X No No No Yes 18/666 No J-FTD28153
NE X X X X X Yes 23/597 No J-BY1795
NC X No No
RR X X X No X Yes 22/659 No J-BY1795
TT X X X X X Yes 16/647 No J-FTC87344
XG X X X No No Yes 17/523 No J-BY167283
JA X X No No No Yes 15/646 No J-FTD11019

Of those 23 Spanish matches, sixteen have upgraded to Big Y tests, 14 of which are Big Y-700s, resulting in nine different haplogroups, all of which are descendants of Haplogroup J-L823. How cool is that?

The “Nos” in the Big Y Match Column aren’t mistakes. That’s right – none of these men match Bennett on the Big Y test, meaning they had more than a 30 mutation difference between them and Bennett on the Big Y test.

At first glance, you’d think that Bennett would have been disappointed, but that’s not the case at all! In fact, it was the information provided by these distant Spanish matches that provided Bennett with the information that his line had split sometime around the year 296 CE, with one branch remaining in Spain and his branch migrating to Eastern Europe, where he has lots of matches.

DNA Plus History

What was happening in Spain or the Iberian peninsula that involved the Jewish people about that time? Historical records exist of Jews living in that region before the fall of the Second Temple in about 70 CE, including records of Jews being expelled from Rome in 139 for their “corrupting influence.”

Furthermore, the Ancient DNA Connections for haplogroup J-L823, the most recent common ancestor (MRCA) for all of those branches, includes connections to multiple burials from:

  • Lebanon
  • Iran
  • Rome (from 1-400 CE)
  • Turkey
  • Jordan

Clearly, Bennett’s ancestor was in the Iberian peninsula around or before 296 CE. One branch stayed, winding up in Spain, and one headed for Europe.

Without these matches, some who didn’t match above the 12 or 25 marker level, how would Bennett have EVER known that his Jewish ancestors left the Middle East for Spain in the early years? How would he have known they migrated from Spain to Eastern Europe, and how would he have known that his line did not migrate directly from the Levant to Eastern Europe in the 9th century?

Big Y matches are typically within about 1500 years, but non-matches are still INCREDIBLY valuable. Without them, you can’t completely assemble your family story.

I noticed on the Time Tree that in Bennett’s Eastern European line, one of his ancestor’s brother lineages includes the Katzenellenbogen Rabbinic Lineage derived from ancient DNA samples.

Bennett’s successes have resulted from contacting his matches and encouraging upgrades. So how did he do it? What’s the magic sauce?

Contacting Matches

How to contact matches successfully is a question I see often. In fact, FamilyTreeDNA recently wrote about that in an article, here.

Bennett’s methodology for contacting his matches to encourage an upgrade is that he sends an email explaining why he’s encouraging them to upgrade, followed by a 2nd email three days later.

Bennett tells the recipient that we are at an inflection point in time. “It’s winter, the wind is blowing hard, and many of the leaves are gone.”

In other words, we need to cast the net wider and capture what we can, while we can. Unfortunately, many early testers have died, and with them, chapters of history are perishing.

Collaboration is key. In addition to encouraging upgrades, Bennett also offers Zoom calls to these groups of men to explain the results if they are interested.

What a GREAT idea! I need to begin offering that as well.

Upgrade Request

Bennett reaches out to his matches at various levels, but he expects his closer STR matches, meaning at the 67 and 111 marker level with the fewest mismatches, to match him on a Big Y-700 test and connect someplace between 300-600 years ago, which helps everyone flesh out their tree.

Bennett’s email:

Hello <name>,

Since you have already made a sizable investment in your Y-DNA, you now know that we come from the dominant male Middle Eastern group (Haplogroup J) of men who <subject here>.

What’s really neat is that our Y-DNA has recently been found in an archaeological site in Northwestern Jordan dated to about 4200 years ago. I know this because I upgraded to the Big Y, which tests SNPs, looking at several million locations on the Y chromosome of each man.

One academic customer recently compared this new technology as the difference between looking into space with binoculars versus the Hubble Telescope.

I don’t know if you are familiar with your list of matches at the highest level you’ve tested for, either Y-67 or Y-111. If you are, you should recognize my name and the names of others who have taken the Big Y test.

You’ll see what you’ll gain by letting me upgrade your test for you and determining whether you are related to my line – probably between about 200 years and 500 years.

This might be the second time that I have written to you on this matter; can I presume if I don’t hear from you that you’re not really interested in the Y-DNA subject anymore?

Can I run the test so that I can see how closely we are related – at my expense? (Of course, you get to see how closely related we are, too).

Please reply to me and say “yes.” You don’t even have to put a 🙂 if you don’t want to.

I started this company and this industry over 20 years ago. I predict that you will be happy with the history of YOU that this upgrade will uncover.

Best,

Bennett Greenspan

As you can see, this email can easily be personalized further and adapted to matches at the 37, 25, and 12 marker levels – or even Family Finder matches, now that intermediate-range haplogroups are being reported.

What’s Next?

I’m going back to every one of the kits I sponsored or that represent descendants of one of my ancestors to review their matches again – focusing not just on the closest matches with common surnames, but also on locations – and specifically at lower matching levels. I’ll also be checking their Family Finder matches for male surname matches, or similar surnames.

As is evident from Bennett’s tests, an entire mine of diamonds is out there, just waiting to be unearthed by a Big Y test.

And to think that some people have been advising people to ignore 12-marker matches out-of-hand because they are “entirely irrelevant.” They aren’t – for two reasons.

  1. First, some early testers only tested to that level
  2. Second, because of the deeper history that Big Y tests from those matches will uncover

You can view your Y-DNA matches, upgrade your own Y-DNA test, or order a Big Y-700 test if you haven’t yet tested by clicking here. What’s your next step?

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

FamilyTreeDNA 2023 Update – Past, Present and Future

At the FamilyTreeDNA International Conference on Genetic Genealogy, held November 3-5 in Houston for group project administrators, product and feature updates were scattered across both days in various presentations.

I’ve combined the updates from FamilyTreeDNA into one article.

I’ve already written two articles that pertain to the conference.

FamilyTreeDNA has already begun rolling the new Y DNA haplogroups from Family Finder autosomal tests, which I wrote about here:

I still have at least two more articles to publish from this conference that was chocked full of wonderful information from a wide range of talented speakers.

Past, Present, and Future with Katy Rowe-Schurwanz

Katy Rowe-Schurwanz, FamilyTreeDNA’s Product Manager, provided an update on what has been accomplished in the four and a half years since the last conference, what’s underway now, and her wish list for 2024.

Please note the word “wish list.” Wish list items are NOT commitments.

Recent Milestones

A lot has been happening at FamilyTreeDNA since the last conference.

Acquisition and Wellness Bundles

As everyone is aware, at the end of 2020, myDNA acquired Gene by Gene, the parent company of FamilyTreeDNA, which included the lab. As a result, the FamilyTreeDNA product menu has expanded, and wellness bundles are now available for FamilyTreeDNA customers.

If you’re interested, you can order the Wellness product in a bundle with a Family Finder test, here.

You can add the Wellness product for $39 if you’ve already tested.

New TIP (Time Prediction) STR Report

Did you notice that the old TIP report for Y DNA STR markers was replaced with an updated version several months ago?

To view the new report, sign on and select your Y DNA matches. At the far right of each match you’ll see these three icons representing a pedigree chart, notes, and the TIP (Time Predictor) report.

The updated TIP report includes wonderful new graphs and age estimates for each match category, which you can read about, here. Each category, such as 67-marker matches, has time estimates in which a common ancestor might have lived at each possible genetic distance.

Math is our friend, and thankfully, someone else has done it for us!

Please note that the Big Y SNP dates are MUCH more accurate for a variety of reasons, not limited to the instability and rapid mutation rate of STR mutations.

MyOrigins3

MyOrigins3, FamilyTreeDNA’s ethnicity offering, added over 60 new reference populations for a total of 90, plus chromosome painting. You can read about MyOrigins features here, and the white paper, here.

This is one of my favorite improvements because it allows me to identify the segment location of my population ancestries, which in turn allows me to identify people who share my minority segments such as Native American and African.

Due to a lack of records, these relationships are often exceedingly difficult to identify, and MyOrigins3 helps immensely.

Additional Releases

Additional products and features released since the last conference include:

Discover

Released in July 2022, Discover is the amazing new free product that details your ancestor’s Y DNA “story” and his walk through time and across the globe.

In the past 18 months, all of the Discover features are new, so I’m only making a brief list here. The great thing is that everyone can use Discover if you know or can discover (pardon the pun) the haplogroup of your ancestral lines. Surname projects are often beneficial for finding your lineages.

  • Haplogroup Story includes haplogroup location, ages derived from the earliest known ancestor (EKA) of your matches, and ancient DNA samples. Please be sure you’ve entered or updated your EKA, and that the information is current. You can find instructions for how to update or add your EKA here.
  • A recent addition to the haplogroup story includes Haplogroup Badges.
  • Country Frequency showing where this haplogroup is found with either a table view or an interactive map
  • Famous and infamous Notable Connections, including Mayflower passengers, Patriots from the American Revolution, US presidents, royal houses, artists, musicians, authors, pirates, sports figures, scientists, and more.

If you know of a proven connection to a notable figure, contact customer support and let them know! Notable connections are added every week.

One famous Discover connection is Ludwig von Beethoven which resulted from a joint academic study between FamilyTreeDNA and academic researchers. It’s quite a story and includes both a mystery and misattributed parentage. You can see if you match on Discover and read about the study, here.

  • Updated Migration Map, including locations of select ancient DNA sites
  • The Time Tree, probably the most popular Discover report, shows the most current version of the Y DNA phylotree, updated weekly, plus scientifically calculated ages for each branch. Tree node locations are determined by your matches and their EKA countries of origin. I wrote about the Time Tree, here.
  • Anticipated in early 2024, the EKA and block tree matches will also be shown on the Time Tree in Discover for individual Big Y testers, meaning they will need to sign in through their kits.
  • The Group Time Tree, visible through group projects, takes the Time Tree a step further by including the names of the EKA of each person on the Time Tree within a specific project. Information is only displayed for project members who have given permission to include their data. You can select specific project groupings to view, or the entire project. I wrote about the Group Time Tree here and here.
  • Globetrekker is an exclusive Big Y mapping feature discussed here, here, here, and here.
  • Ancient Connections includes more than 6,100 ancient Y DNA results from across the globe, which have been individually analyzed and added for matching in Discover. Ancient Connections serve to anchor haplogroups and provide important clues about matches, migration paths and culture. New connections are added weekly or as academic papers with adequate Y DNA coverage are released.
  • Your Ancestral Path, which lists the haplogroups through every step from the tester back to Y Adam and beyond. Additional information for each haplogroup in your path includes “Time Passed” between haplogroups, and “Immediate Descendants,” meaning haplogroups that descend from each subclade. New columns recently added include “Tested Modern Descendants” and “Ancient Connections.”
  • Suggested Projects include surname, haplogroup, and geographic projects. Katy said that people joining projects are more likely to collaborate and upgrade their tests. You can also see which projects other men with this haplogroup have joined, which may well be projects you want to join too.
  • Scientific Details provides additional information, such as each branch’s confidence intervals and equivalent variables (SNPs). You can read more here.
  • Compare Haplogroups is the most recent new feature, added just last month, which allows you to enter any two haplogroups and compare them to determine their most recent common ancestral haplogroup. You can read about Compare Haplogroups, here.

Please note that the Studies feature is coming soon, providing information about studies whose data has been included in Discover.

You can read about Discover here, here, here, and here.

If you’re interested, FamilyTreeDNA has released a one-minute introduction to Y DNA and Discover that would interest new testers, here.

Earliest Known Ancestor (EKA) Improvement

Another improvement is that the earliest known ancestor is MUCH easier to enter now, and the process has been simplified. The EKAs are critical for Discover, so PLEASE be sure you’ve entered and updated your EKA.

Under the dropdown beside your name in the upper right-hand corner of your personal page, select Account Settings, then Genealogy and Earliest Known Ancestors. Complete the information, then click on “Update Location” to find or enter the location on a map to record the coordinates.

It’s easy. Just type or drop a pin and “Save.”

Saving will take you back to the original EKA page. Save that page, too.

Recommended Projects on Haplogroups & SNPs Page

You’re probably aware that Discover suggests projects for Y DNA testers to join, but recommended haplogroup projects are available on each tester’s pages, under the Y DNA Haplotree & SNPs page, in the Y DNA STR results section.

If there isn’t a project for your immediate haplogroup, just scroll up to find the closest upstream project. You can also view this page by Variants, Surnames and Countries.

This is a super easy tool to use to view which surnames are clustered with and upstream of your haplogroup. With Family Finder haplogroups being assigned now, I check my upstream haplogroups almost daily to see what has been added.

For example, my Big Y Estes results are ten branches below R-DF49, but several men, including Estes testers, have been assigned at this level, thanks to Y DNA haplogroups from Family Finder testing. I can now look for these haplogroups in the STR and Family Finder matches lists and see if those men are receptive to Big Y testing.

Abandoned Projects

Sometimes group project administrators can no longer function in that capacity, resulting in the project becoming abandoned. FamilyTreeDNA has implemented a feature to help remedy that situation.

If you discover an abandoned project, you can adopt the project, spruce things up, and select the new project settings. Furthermore, administrators can choose to display this message to recruit co-administrators. I need to do this for several projects where I have no co-admin.

If you are looking for help with your project, you can choose to display the button
through the Project Profile page in GAP. For non-project administrators, if you’d like to help, please email the current project administrators.

New Kit Manager Feature

FamilyTreeDNA has added a “Kit Manager” feature so that an individual can designate another person as the manager of their kit.

This new setting provides an avenue for you to designate someone else as the manager of your DNA test. This alerts FamilyTreeDNA that they can share information with both of you – essentially treating your designated kit manager the same as you.

If you’re the kit manager for someone else, you NEED to be sure this is completed. If that person is unavailable for some reason, and support needs to verify that you have legitimate access to this kit, this form and the Beneficiary form are the ONLY ways they can do that.

If your family member has simply given you their kit number and password, and for some reason, a password reset is required, and their email address is the primary contact – you may be shut out of this kit if you don’t complete this form.

Beneficiary Page

Additionally, everyone needs to be sure to complete the Beneficiary page so that in the event of your demise, FamilyTreeDNA knows who you’ve designated to access and manage your DNA account in perpetuity. If you’ve inherited a kit, you need to add a beneficiary to take over in the event of your death as well.

What is FamilyTreeDNA working on now?

Currently in the Works

Katy moved on to what’s currently underway.

Privacy and Security

Clearly, the unauthorized customer data exposure breach at 23andMe has reverberated through the entire online community, not just genetic genealogy. You can read about the incident here, here, here, and here.

FamilyTreeDNA has already taken several steps, and others are in development and will be released shortly.

Clearly, in this fast-moving situation, everything is subject to change.

Here’s what has happened and is currently planned as of today:

  • Group Project Administrators will be required to reset their password soon.

Why is this necessary?

Unauthorized access was gained to 23andMe accounts by people using the same password for multiple accounts, combined with their email as their user ID. Many people use the same password for every account so that they can remember it. That means that all a hacker needs to do is breach one account, and they can use that same information to “legitimately” sign in to other accounts. There is no way for the vendor to recognize this as unauthorized since they have both your user ID and password.

That’s exactly what happened at 23andMe. In other breaches, this information was exposed, and hackers simply tried the same username and password combination at 23andMe, exposing the entire account of the person whose account they signed in “as.” This includes all of their matches, genetic tree, shared matches, matches of matches, ethnicity, and segments. They could also have downloaded both the match list and the raw DNA file of the compromised account.

At FamilyTreeDNA, project administrators can select their own username, which could be their email, so they will be required to reset their password.

Additional precautions have been put in place on an interim basis:

  • A pause in the ability to download match and segment information.
  • A pause in accepting 23andMe uploads.

Administrators will also be required to use two-factor authentication (2FA.) To date, two of the four major vendors are requiring 2FA. I would not be surprised to see it more broadly. Facebook recently required me to implement 2FA there, too, due to the “reach” of my postings, but 2FA is not required of everyone on Facebook.

Please note that if you received an email or message that is supposedly from any vendor requiring 2FA, GO DIRECTLY TO THAT VENDOR SITE AND SIGN IN.  Never click on a link in an email you weren’t expecting. Bad actors exploit everything.

Customers who are not signing in as administrators are not required to implement 2FA, nor will they be required to reset their password.

Personally, I will implement 2FA as soon as it’s available.

While 2FA is an extra step, it’s easy to get used to, and it has already literally saved one of my friends from an authorized hack on their primary and backup email accounts this week. Another friend just lost their entire account on Facebook because someone signed in as them. Their account was gone within 15 minutes.

2FA is one of those things you don’t appreciate (at all) until it saves you, and then, suddenly, you’re incredibly grateful.

At this point in time, FamilyTreeDNA users will NOT be required to do a password reset or implement 2FA. This is because customers use a kit number for sign-in and not a username or email address. I would strongly recommend changing your password to something “not easy.” Never reuse passwords between accounts.

I really, really want you to visit this link at TechRepublic and scroll down to Figure A, which shows how long it takes a hacker to crack your password. I guarantee you, it’s MUCH quicker than you’d ever expect.

Kim Komando wrote about this topic two years ago, so compare the two charts to see how much easier this has become in just two years.

Again, if you receive an email about resetting your password, don’t click on a link. Sign in independently to the vendor’s system, but DO reset your password.

FamilyTreeDNA also engages in additional security efforts, such as ongoing penetration testing.

New Permissions

Additionally, at FamilyTreeDNA, changes were already in the works to separate out at least two permissions that testers can opt-in to without granting project administrators Advanced rights.

  • Download data
  • Purchase tests

The ability to purchase tests can be very important because it allows administrators to order and pay for tests or upgrades on behalf of this tester anytime in the future.

Family Finder Haplogroups

FamilyTreeDNA has already begun releasing mid-level Y DNA haplogroups for autosomal testers in a staggered rollout of several thousand a day.

I wrote about this in the article, FamilyTreeDNA Provides Y DNA Haplogroups from Family Finder Autosomal Tests, so I’m not repeating all of that information here – just highlights.

  • The Family Finder haplogroup rollout is being staggered and began with customers on the most recent version of the testing chip, which was implemented in March of 2019.
  • Last will be transfers/uploads from third parties.
  • Haplogroups resulting from tests performed in the FTDNA labs will be visible to matches and within projects. They will also be used in both Discover and the haplotree statistics. This includes Family Finder plus MyHeritage and Vitagene uploads.
  • Both MyHeritage and Vitagene are uploaded or “transferred” via an intracompany secure link, meaning FamilyTreeDNA knows that their information is credible and has not been manipulated.
  • Haplogroups derived from tests performed elsewhere will only be visible to the user or a group administrator viewing a kit within a project. They will not be visible to matches or used in trees or for statistics.
  • Any man who has taken a Y DNA STR test will receive a SNP-confirmed, updated haplogroup from their Family Finder test that replaces their predicted haplogroup from the STR test.

Please read this article for more information.

New Discover Tools and Updates

Discover content continues to be updated, and new features are added regularly, creating an increasingly robust user experience.

Soon, group administrators will be able to view all Discover features (like Globetrekker) when viewing kits of project members who have granted an appropriate level of access.

Ancient and Notable connects are added weekly, and a new feature, Study Connections, will be added shortly.

Study Connections is a feature requested by customers that will show you which study your academic matches came from. Today, those results are used in the Y DNA tree, but the source is not detailed.

Anticipated in early 2024, the EKA and block tree matches will also be shown on the Time Tree in Discover for individual Big Y testers (not publicly).

Big Y FaceBook Group

FamilyTreeDNA has ramped up its social media presence. They launched the Big Y Facebook group in July 2023, here, which currently has just under 9000 members. Several project administrators have volunteered their time to help manage the group.

FamilyTreeDNA Blog

In addition, FamilyTreeDNA is publishing at least one blog article each week, and sometimes more. You can view or subscribe here. Some articles are written by FamilyTreeDNA staff, but project administrators and customers author other content.

Multi-Language Support

Translation of the main FamilyTreeDNA website and results pages to Spanish has begun, with more languages planned soon.

Paypal, Payments, and Gift Cards

Paypal has been added as a payment selection, along with a PayPal option that provides the ability to make payments.

Additionally, a gift card can be purchased from the main page.

Million Mito Project & Mitotree

Work on the Million Mito Project is ongoing.

The Million Mito Project was launched in 2020 as a collaborative effort between FamilyTreeDNA’s Research & Development Team and the scientific portion of the Genographic Project. I’m a team member and wrote about the Million Mito Project, here.

We’re picking up from where the Phylotree left off in 2016, analyzing 20 times more mtDNA full sequences and reimagining the mtDNA Haplotree. By examining more mtDNA data and applying the processes that allowed FamilyTreeDNA to build the world’s largest Y DNA Haplotree, we can also create the world’s largest Mitotree.

In 2022, the first update was released, authored by the Million Mito team, with the discovery of haplogroup L7. You can read about this amazing discovery rooted deep in the tree here, here, and here. (Full disclosure: I’m a co-author.)

Not only that, but “Nature Scientific Reports” selected this article as one of five named Editor’s Choice in the Mitogenomics category, here. In the science world, that’s a HUGE deal – like the genetic Emmy.

Here’s one example of the type of improvements that can be expected. Currently, the formation of haplogroup U5a2b2a reaches back to about 5000 years ago, but after reanalysis, current branches originated between 500 and 2,500 years ago, and testers are clustered more closely together.

This is SOOO exciting!!!

Just as Discover for Y DNA results was built one feature at a time, the same will be true for MitoDiscover. That’s my name, not theirs.

As the new Mitotree is rolled out, the user interface will also be updated, and matching will function somewhat differently. Specifically, it’s expected that many more haplogroups will be named, so today’s matching that requires an exact haplogroup match to be a full sequence match will no longer work. That and other matching adjustments will need to be made.

I can hardly wait. I have so many results I need to be able to view in a tree format and to place in a timeframe.

You can be included in this exciting project, learn more about your matrilineal (mother’s) line, and hopefully break down some of those brick walls by taking the full sequence mitochondrial DNA test, here.

After the new Mitotree is rolled out and the Y DNA Family Finder haplogroups are completed, Family Finder customers, where possible, will also receive at least a basic-level mitochondrial haplogroup. Not all upload files from other vendors include mtDNA SNPs in their autosomal files. The mitochondrial Family Finder haplogroup feature isn’t expected until sometime in 2025, after the new tree and MitoDiscover are complete.

The Future

What’s coming later in 2024, or is ongoing?

Privacy Laws

Most people aren’t aware of the new privacy laws in various states, each of which has to be evaluated and complied with.

The effects of these changes will be felt in various areas as they are implemented.

New Kits Opted Out of IGG

Since late August, all new FTDNA kits are automatically opted OUT of Investigative Genetic Genealogy (IGG) by default.

Regular matching consent and IGG matching consent have been separated during onboarding.

Biobanking Separate Consent

Another consent change is to have your sample biobanked. FamilyTreeDNA has always maintained your sample for “roughly 25 years.” You could always ask to have your sample destroyed, but going forward, you will be asked initially if you want your sample to be retained (biobanked.) It’s still free.

Remember, if someone declines the biobanking option, their DNA will be disposed of after testing. They can’t order upgrades without submitting a new sample. Neither can their family after they’re gone. I ordered my mother’s Family Finder test many years after she had gone on to meet our ancestors – and I’m incredibly grateful every single day.

MyHeritage Tree Integration

An exciting change coming next year is tree integration with MyHeritage.

And no, before any rumors get started, FAMILYTREEDNA IS NOT MERGING WITH MYHERITAGE. It’s a beneficial marriage of convenience for both parties.

In essence, one of the primary focuses of MyHeritage is trees, and they do that very well. FamilyTreeDNA is focused on DNA testing and their existing trees have had issues for years. MyHeritage trees are excellent, support pedigree collapse, provide search capabilities that are NOT case sensitive, SmartMatching, and much more.

If you don’t have a MyHeritage account, creating one is free, and you will be able to either port your existing FamilyTreeDNA tree, or begin one there. If you’re already a MyHeritage member, FamilyTreeDNA and MyHeritage are planning together for a smooth integration for you. More detailed information will be forthcoming as the integration progressed and is released to customers.

You’ll be able to connect multiple kits to your tree at MyHeritage, just like you can at FamilyTreeDNA today, which enables family matching, aka bucketing.

You can also have an unlimited number of different trees at MyHeritage on the same account. You’re not limited to one.

After you link your initial FamilyTreeDNA kit to the proper person in your MyHeritage tree, you’ll be able to relink any currently linked kits.

MyHeritage will NOT receive any DNA information or match information from FamilyTreeDNA, and yes, you’ll be able to use the same tree independently at MyHeritage for their DNA matching.

You’ll still be able to view your matches’ trees, except it will actually be the MyHeritage tree that will be opened at FamilyTreeDNA in a new tab.

To the best of my knowledge, this is a win-win-win, and customers of both companies aren’t losing anything.

One concern is that some FamilyTreeDNA testers have passed away and cannot transition their tree, so a view-only copy of their tree will remain at FamilyTreeDNA so that their matches can still see their tree.

Big Y Infrastructure

Katy mentioned that internal discussions are taking place to see what changes could be made to improve things like matching and test processing times.

No changes are planned for SNP or STR coverage, but discussions are taking place about a potential update to the Telomere to Telomere (T2T) reference. No promises about if or when this might occur. The last part of the human genome to be fully sequenced, the T2T reference model includes the notoriously messy and unreliable region of the Y chromosome with many repeats, duplications, gaps, and deletions. Some data from this region is probably salvageable but has previously been omitted due to the inherent problems.

I’m not sure this shouldn’t be in the next section, the Wishlist.

Wishlist

There are lots of good things on the Wishlist – all of which I’d love.

I’d have difficulty prioritizing, but I’d really appreciate some Family Finder features in addition to the items already discussed. I’d also like to see some GAP (administrator) tool updates.

Which items do you want to see most?

Katy said that FamilyTreeDNA is NOT planning to offer a Whole Genome Sequencing (WGS) test anytime soon. So, if you’re holding your breath, please don’t. Based on what Katy did say, WGS is very clearly not a consideration in 2024 and I don’t expect to see it in 2025 either unless something changes drastically in terms of technology AND pricing.

While WGS prices have come down, those consumer tests are NOT scanned at the depth and quality required for advanced tests like the Big Y or even Family Finder. Normally consumer-grade WGS tests are scanned between 2 and 10 times, where the FamilyTreeDNA lab scans up to 30 times in order to obtain a quality read. 30X scans are in the same category as medical or clinical grade whole genome scans. Significantly higher quality scans mean significantly higher prices, too, so WGS isn’t ready for genealogy prime time yet.

Additionally, commercially available WGS tests are returned to the customer “as is,” and you’re left to extract the relevant SNPs and arrange them into files, or find someone else to do that. Not to mention, in order to preserve the integrity of their database, FamilyTreeDNA does not accept Y or mitochondrial DNA uploads.

Recently, I saw two WGS files with a 20-25% no-call rate for the autosomal SNPs required for the Family Finder test. Needless to say, that’s completely unacceptable. Some tools attempt to “fix” that mess by filling in the blanks in the format of either a 23andMe or Ancestry file so you can upload to vendors, but that means you’re receiving VERY unreliable matches.

The reason none of the major four vendors offer WGS testing for genealogists is because it’s not financially feasible nor technologically beneficial. The raw data file alone won’t fit on most home computers. WGS is just not soup yet, and it won’t be for the general consuming public, including relevant tools, for at least a few years.

I’ve had my whole genome sequenced, and trust me, I wish it were feasible now, but it just isn’t.

Suggestions Welcomed

Katy said that if you have suggestions for items NOT on the wishlist today to contact her through support.

I would add that if you wish to emphasize any specific feature or need above others, please send that feedback, politely, to support as well.

Katy ended by thanking the various teams and individuals whose joint efforts together produce the products we use and enjoy today.

Lab Update

Normally, DNA testing companies don’t provide lab updates, but this conference is focused on group project administrators, who are often the most dedicated to DNA testing.

A lab update has become a tradition over the years.

Linda Jones, Lab Manager, provided a lab update.

You may or may not know that the FamilyTreeDNA lab shifted gears and stepped up to handle Covid testing.

Supply-chain shortages interfered, but the lab ran 24×7 between 2020 and 2022.

Today, the lab continues to make improvements to processes with the goal of delivering the highest quality results in a timely manner.

On Monday, after the conference, attendees could sign up for a lab tour. You might say we are a rather geeky bunch and really enjoy the science behind the scenes.

Q&A and Thank You

At the end of the conference, the FamilyTreeDNA management team answered questions from attendees.

Left to right, Daniel Au, CTO; Linda Jones, Lab Manager; Katy Rowe-Schurwanz, Product Manager; Clayton Conder, VP Marketing; Goran Runfeldt, Head of R&D; and Andrew Gefre, Development Manager. Not pictured, Jeremy Balkin, Support Manager; Kelly Jenkins, VP of Operations; and Janine Cloud, Group Projects Manager. Janine is also responsible for conferences and events, without whom there would have been no 2023 FamilyTreeDNA conference. Janine, I can’t thank you enough!

A huge thanks to all of these people and many others, including the presenters, CSRs,  IT, and other FamilyTreeDNA team members for their support during the conference, enabling us to enjoy the conference and replenish the well of knowledge.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Holiday DNA Sales Are Here!!!

I apologize for the brevity of this posting, but I came home from the FamilyTreeDNA Conference this past weekend with “conference crud.”

I’ll catch you up on that great conference later, but sales won’t wait, and the holiday sales have already begun. This is a great time to order. These prices are the lowest ever.

MyHeritage

The MyHeritage autosomal test is only $36, and shipping is free if you order two or more DNA tests. That’s a GREAT deal. Click here to order.

If you’ve already tested elsewhere, you can upload your raw DNA file from that vendor to MyHeritage, here. I’ve provided step-by-step instructions, here. After you’ve uploaded, be sure to purchase the $29 unlock for advanced autosomal features, including the MyHeritage chromosome browser and Theories of Family Relativity, which shows you how you connect with DNA matches who share the same ancestor in MyHeritage’s collection of 52 million trees.

If you’re new to MyHeritage, you can also purchase a data or records subscription here, including a free trial.

I use this combination of DNA, trees, and tools almost daily and love that MyHeritage sends me regular record matches from their billions of genealogy records.

FamilyTreeDNA

Every test is on sale at FamilyTreeDNA.

As you know, FamilyTreeDNA provides Y-DNA, mitochondrial, and autosomal testing through their Family Finder test. They also accept autosomal DNA file uploads from Ancestry and MyHeritage. You’ll find easy download and upload instructions for each vendor, here. The advanced feature unlock is on sale now for just $9!

You can order each test individually or bundle tests for a better price.

Note that the introductory Y-DNA 37-marker test is available for $99, and can later be upgraded to the Big-Y test. However, the Big Y-700 is on sale for $399 which is a great price. Y-DNA testing unlocks your paternal ancestor’s history revealed in FamilyTreeDNA‘s world-class Discover tools.

If you’ve already tested at FamilyTreeDNA and would like to add another test for yourself or upgrade, say to the Big-Y test, just click here, sign on, and click on the Add Ons and Upgrade button in the upper right-hand corner.

I hope I’m not spilling the beans, but all sale prices, including upgrades and autosomal transfer unlocks, are shown below:

Genealogy Goals

The holidays are coming! Take a look at what you need for your genealogy.

I decided a long time ago it’s absolutely fine to “gift myself” with purchases and upgrades for my cousins. Especially the Big Y-700 at FamilyTreeDNA and the mitochondrial DNA test, which is vastly underutilized. This helps my genealogy immensely, as well as theirs. Most people are happy to swab, especially if you’re doing the genealogy work.

My goal is to:

  • Have the autosomal DNA of each of my family members and cousins in both databases that provide chromosome browsers so that I can confirm ancestors at FamilyTreeDNA and MyHeritage.
  • Find male cousins to test for the Y-DNA, the surname lineage of each of my ancestral lines. Males who descend paternally from each male ancestor can usually be tracked by their surname.
  • Mitochondrial DNA for each of my ancestors. For mitochondrial DNA testing, we need testers descended through all females from each female ancestor, although males in the current generation can test. Everyone has their mother’s direct matrilineal line mitochondrial DNA.

To find testing candidates for your lineages, check projects at FamilyTreeDNA, autosomal matches at all vendors, your ancestors at WikiTree, ThruLines at Ancestry, even though ThruLines is still having issues, and Theories of Family Relativity at MyHeritage.

With DNAtests on sale right now, this is a great time to purchase tests at MyHeritage and FamilyTreeDNA.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Y-DNA Haplogroup O – When and How Did It Get to the Americas?

Y-DNA Haplogroup O has been found in male testers descended from a Native American ancestor, or in Native American tribes in the Americas – but sometimes things are more complex than they seem. The story of when and how haplogroup O arrived in the Americas is fascinating – and not at all what you might think.

Introduction

The concept of Native American heritage and indigenous people can be confusing. For example, European Y-DNA haplogroup R is found among some Native American men. Those men may be tribal members based on their mother’s line, or their haplogroup R European Y-DNA may have been introduced either through adoption practices or traders after the arrival of Europeans.

There is unquestionable genetic evidence that the origin of Haplogroup R in the Americas was through colonization, with no evidence of pre-contact indigenous origins.

Y-DNA testing and matching, specifically the Big Y-700 test, with its ability to date the formation of haplogroups very granularly, has successfully identified the genesis of Y-DNA haplogroups and their movement through time.

We’ve spent years trying to unravel several instances of Native American Y-DNA Haplogroup O and their origins. Native American, in this context, means that men with haplogroup O are confirmed to be Native American at some point in documented records. This could include early records, such as court or probate records, or present-day members of tribes. There is no question that these men are recognized as Native American in post-contact records or are tribal members, or their descendants.

What has not been clear is how and when haplogroup O entered the Native American population of these various lineages, groups, or tribes. In other words, are they indigenous? Were they here from the earliest times, before the arrival of colonists, similar to Y-DNA haplogroups C and Q?

This topic has been of great interest for several years, and we have been waiting for additional information to elucidate the matter, which could manifest in several ways:

  1. Ancient pre-contact DNA samples of haplogroup O in the Americas, but none have been found.
  2. Current haplogroup O testers in Native American peoples across the North and South American continents, forming a connecting trail genetically, geographically, and linearly through time. This has not occurred.
  3. Big-Y DNA matches within the Americas between Haplogroup O Native American lines unrelated in a genealogical timeframe whose haplogroup formation pre-dates European contact. This has not occurred.
  4. Big-Y DNA matches between Haplogroup O men whose haplogroups were formed in the Americas after the Beringian migration and expansion that scientists agree occurred at least 12-16K years ago, and possibly began earlier. Earlier human lineages, if they existed, may not have survived. A later Inuit and Na-Dené speaker circumpolar migration occurred 4-7K years ago. This has not occurred.
  5. Big-Y DNA matches with men whose most recent common ancestor haplogroup formation dates connect them with continental populations in other locations, outside of North and South America. This would preclude their presence in the Americas after the migrations that populated the Americas. This has occurred.

The Beringian migration took place across a now-submerged land bridge connecting the Chutkin Peninsula in Russia across the Bering Strait with the Seward Peninsula in Alaska.

By Erika Tamm et al – Tamm E, Kivisild T, Reidla M, Metspalu M, Smith DG, et al. (2007) Beringian Standstill and Spread of Native American Founders. PLoS ONE 2(9): e829. doi:10.1371/journal.pone.0000829. Also available from PubMed Central., CC BY 2.5, https://commons.wikimedia.org/w/index.php?curid=16975303

Haplogroup O is clearly Native American in some instances, meaning that it occurs in men who are members of or descend from specific Native American tribes or peoples. One man, James Revels, is confirmed in court records as early as 1656. However, ancestors of James Revels fall into category #5, as their upstream parental haplogroup is found in the Pacific islands outside the Americas after the migration period.

Based on available evidence, the introduction of haplogroup O appears to be post-contact. Therefore, haplogroup O is not indigenous to the Americans in the same sense as haplogroups Q and C that are found widespread throughout the Americas in current testers who are tribal members, descendants of tribal members, and pre-contact ancient DNA as mapped in the book, DNA for Native American Genealogy.

Ancient DNA

Haplogroup C is found in both North and South America today, as are these ancient DNA locations.

Haplogroup Q is more prevalent than Haplogroup C, and ancient DNA remains are found throughout North and South America before colonization.

No ancient DNA for Haplogroup O has been discovered in the Americas. We do find contemporary haplogroup O testers in regional clusters, which we will analyze individually.

Let’s take a look at what we have learned recently.

Wesley Revels’ Lineage

Wesley Revels was the initial Y-DNA tester whose results identified Haplogroup O as Native American, proven by a court record. That documentation was critical, and we are very grateful to Wesley for sharing both his information and results.

Wesley’s ancestor, James Revels, was Native American, born about 1656 and bound to European planter, Edward Revell. James was proven in court to be an Accomack “Indian boy” from “Matomkin,” age 11 in 1667. James was bound, not enslaved, until age 24, at which time he was to be freed and receive corn and clothes.

James had died by 1681 when he was named several times in the Accomack County records as both “James, an Indian” and “James Revell, Indian,” in reference to his estate. James lived near Edward Revell, his greatest creditor and, therefore, administrator of his estate, and interacted with other Indian people near Great Matompkin Neck. Marie Rundquist did an excellent job of documenting that here. Additional information about the Revels family and Matomkin region can be found here.

The location where Edward Revell lived, Manokin Hundred, was on the water directly adjacent the Great Matomkin (now Folly Creek) and Little Matomkin Creeks, inside the Metomkin Inlet. The very early date tells us that James Revels’s paternal ancestor was in the colonies by 1656 and probably born about 1636, or perhaps earlier.

Lewis and Revels men are later associated with the Lumbee Tribe, now found in Robeson and neighboring counties in North Carolina. The Lewis line descends from the Revels lineage, as documented by Marie and Wesley. Other men from this line have tested and match on lower-level STR markers, but have not taken the much more granular and informative Big-Y test.

Until recently, the men who matched Wesley Revels closely on the Big-Y test were connected with the Revels line and/or the Lumbee.

Wesley has a 37-marker STR match to a man with a different surname who had not tested beyond that level, in addition to several 12-marker STR matches to men from various locations. Men who provided known ancestral or current locations include one from Bahrain, two from the Philippines, and three from China. Those men have not taken the Big-Y, and their haplogroups are all predicted from STR results to O-M175 which was formed in Asia about 31,000 years ago.

12-marker matches can reach thousands of years back in time. Unless the matches share ancestors and match at higher levels, 12-marker matches are only useful for geographic history, if that. The Big Y-700 test refines haplogroup results and ages from 10s of thousands of years to (generally) within a genealogically relevant timeframe, often within a couple hundred years.

One of Wesley’s STR matches, Mr. Luo, has taken a Big Y-700 test. Mr. Luo descends directly from Indonesia in the current generation and is haplogroup O-CTS716, originating about 244 BCE, or 2244-ish years ago. Mr. Luo does not match Wesley on the Big-Y test, meaning that Wesley and Mr. Luo have 30 or more SNP differences in their Big-Y results, which equates to about 1,500 years. The common ancestor of Wesley Revels and Mr. Luo existed more than 1,500 years ago in Indonesia. It’s evident that Mr. Luo is not Native American, but his location is relevant in a broader analysis.

There is no question that Wesley’s ancestor, James Revels, was Native American based on the court evidence. There is also no question that the Revels’ paternal lineage was not in the Americas with the Native American migration group 12-16K years ago.

The remaining question is how and when James Revels’ haplogroup O ancestor came to be found on the Atlantic seaboard in the early/mid 1600s, only a few years after the founding of Jamestown.

The results of other Haplogroup O men may help answer this question.

Mr. Lynn

Another haplogroup O man, Mr. Lynn, matches Wesley on STR markers, but not on the Big-Y test.

Mr. Lynn identified his Y-DNA line as Native American, although he did not post detailed genealogy. More specifically, we don’t know if Mr. Lynn identified that he was Native on his paternal line because he matches Wesley, or if the Native history information was passed down within his family, or from genealogical research. Mr. Lynn could also have meant generally that he was Native, or that he was Native “on Dad’s side,” not specifically his direct patrilineal Y-line.

Based on Mr. Lynn’s stated Earliest Known Ancestor (EKA) and additional genealogical research performed, his ancestor was John Wesley Lynn (born approximately 1861, died 1945), whose father was Victor Lynn. John’s death certificate, census, and his family photos on Ancestry indicate that he was African American. According to his death certificate, his father, Victor Lynn, was born in Chatham Co., NC, just west of Durham.

Family members are found in Baldwin Township, shown above.

I did not locate the family in either the 1860 or 1870 census. In 1860, the only Lynn/Linn family in Chatham County was 50-year-old Mary Linn and 17-year-old Jane, living with her, presumably a daughter. Both are listed as “mulatto” (historical term) with the occupation of “domestic.” They may or may not be related to John Wesley Lynn.

In 1870, the only Linn/Lynn in Chatham County is John, black, age 12 or 13 (so born in 1857 or 1858), farm labor, living with a white family. This is probably not John Wesley Lynn given that he is found with his mother in 1880 and the ages don’t match.

In 1880. I find Mary Lynn in Chatham County, age 48, single, black, with daughter Eliza Anne, 20, mulatto, sons John Wesley, 14 so born about 1866, and Charles 12, both black. Additionally, she is living with her nieces and nephews, Cephus, black, 12, Lizzie, 7, mulatto, Malcom, 4, mulatto, William H, 3, mulatto (I think, written over,) and John age 4, mulatto. The children aged 12 and above are farm labor.

In 1880, I also find Jack Lynn, age 28, black, married with 3 children, living beside William Lynn, 25, also married, but with no children.

Trying to find the family in 1870 by using first name searches only, I find no black Mary in 1870 or a mulatto Mary with a child named Jack or any person named Cephus by any surname. I don’t find Jack or any Lynn/Linn family in Chatham County.

The 1890 census does not exist.

In the 1900 census, I find Wesley Lynn in Chatham County, born in January of 1863, age 37, single, a boarder working on the farm of John Harris who lives beside Jack Lynn, age 43, born in April of 1857. Both Lynn men are black. I would assume some connection, given their ages, possibly or probably brothers.

In 1940, John Wesley Lynn, age 74, negro (historical term), is living beside Victor Lynn, age 37, most likely his son.

I could not find Victor Lynn, John Wesley Lynn’s father in any census, so he was likely deceased before 1880 but after 1867, given that Mary’s son Charles Lynn was born in 1868, assuming Mary’s children had the same father. The fact that Mary was listed as single, not married nor widowed suggests enslavement, given that enslaved people were prohibited from legally marrying.

About the only other assumption we can make about Victor Sr. is that he was probably born about 1832 or earlier, probably in Chatham County, NC based on John Wesley’s death certificate, and he was likely enslaved.

Subclades of Haplogroup O

Both the Revels and Lynn men are subclades of haplogroup O and both claim Native heritage – Wesley based on the Revels genealogy and court documents, and Mr. Lynn based on the Native category he selected to represent his earliest known paternal ancestor at FamilyTreeDNA.

Both men have joined various projects, including the American Indian Project, which provides Marie and me, along with our other project co-administrators, the ability to work with and view both of their results at the level they have selected.

How Closely Related Are These Haplogroup O Men?

How closely related are these two men?

By Viajes_de_colon.svg: Phirosiberiaderivative work: Phirosiberia (talk) – Viajes_de_colon.svg, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=8849049

  • Do the haplogroups of the Revels men and Mr. Lynn converge in a common ancestor in a timeframe BEFORE colonialization, meaning before Columbus “discovered” the Caribbean islands when colonization and the slave trade both began?
  • Do the haplogroups converge on North or South American soil or elsewhere?
  • Is there anything in the haplogroup and Time Tree information that precludes haplogroup O from being Native prior to the era of colonization?
  • Is there anything that confirms that a haplogroup O male or males were among the groups of indigenous people that settled the Americas sometime between 12 and 26 thousand years ago? Or even a later panArctic or circumpolar migration wave?

Haplogroup O is well known in East Asia, Indonesia, and the South Pacific.

Another potential source of haplogroup O is via Madagascar and the slave trade.

The Malagasy Roots Project has several haplogroup O individuals, including the Lynn and Revels men, who may have joined to see if they have matches. We don’t know why the various haplogroup O men in the project joined. Other haplogroup O men in the project may or may not have proven Malagasay heritage.

Information provided by the project administrators is as follows:

The people of Madagascar have a fascinating history embedded in their DNA. 17 known slave ships came from Madagascar to North America during the Transatlantic Slave Trade. As a result, we find Malagasy DNA in the African American descendants of enslaved people, often of Southeast Asian origin. One of the goals of this project is to discover the Malagasy roots of African Americans and connect them with their cousins from Madagascar. Please join us in this fascinating endeavor. mtDNA Haplogroups of interest include: B4a1a1b – the “Malagasy Motif”, M23, M7c3c, F3b1, R9 and others Y-DNA Haplogroups include: O1a2 – M50, O2a1 – M95/M88, O3a2c – P164 and others

Resources:

http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2987306/  http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1199379/  http://mbe.oxfordjournals.org/cgi/pmidlookup?view=long&pmid=19535740  http://www.biomedcentral.com/1471-2156/15/77  http://www.biomedcentral.com/1471-2164/10/605

The Malagasy group only has one other man who is haplogroup O and took the Big-Y test, producing haplogroup O-FTC77008. Of course, we don’t know if he has confirmed Madagascar ancestry, and his haplogroup is quite distant from both Revels and Lynn in terms of when his haplogroup was formed.

Viewing the Malagasy Project’s Group Time Tree, above, the common ancestor between those three men lived about 28K BCE, or 30,000 years ago.

Haplogroup O Project Group Time Tree

The Haplogroup O Project Time Tree provides a better representation of haplogroup O in general given that it has a much wider range of samples.

On this tree, I’ve labeled the haplogroup formation dates, along with the Revels/Lewis line which descends from O-FT45548. This haplogroup includes one additional group member whose surname is locked, as he hasn’t given publication permission. The haplogroup formation date of 1766 occurs approximately 85 years after James Revel’s birth, so is attributable to some, but not all of his descendants. At least one descendant falls into the older Haplogroup O-BY60500.

The common ancestor of all three, meaning Revels, Lewis, and the man whose name is locked and does not know his genealogy, is haplogroup O-BY60500, born about 1741.

Their ancestral haplogroup before that, O-FT11768, is much older.

Two Filipino results are shown on and descending from the parent branch of O-FT11768, formed about 3183 BCE, or about 5183 years ago. This tells us that the ancestors of all these men were in the same place, most likely the Philippines, at that time.

3183 BCE (5180 years ago) is well after the Native American migration into the Americas.

Discover Time Tree

Obviously, not every tester joins a project, so now I’m switching to the Discover Time Tree which includes all Y-DNA haplogroup branches. Their common haplogroup, O-FT11768, has many branches, not all of which are shown below. I’m summarized unseen branch locations at bottom left.

Expanding the Time Tree further to view all of the descendant haplogroups of O-FT11768, we see that this was a major branch with many South Pacific results, including the branch of O-FT22410, bracketed in red, which has three members.

One is Mr. Lynn whose feather indicates Native American as his EKA country selection, one is a man whose ancestor is from Singapore, and one is an unknown individual who did not enter his ancestor’s country of origin.

Geography

Wesley’s STR match list, which can reflect matches further back in time than the Big-Y test, includes islands near Singapore. This geography aligns with what is known about haplogroup O.

The distance between this Asian region and continental America, 9000+ miles distant by air, is remarkable and clearly only navigable at that time by ship, meaning ships with experienced crew, able to navigate long distances with supplies and water.

We know that in 760 CE, about 1240 years ago, Mr. Lynn’s haplogroup O-F24410 was formed someplace in the South Pacific – probably in Malaysia or a nearby island. This region, including the Philippines, is home to many haplogroup O men. The majority of haplogroup O is found in Asia, the South Pacific, and Diaspora regions.

We know that Hawaii was populated by Polynesian people about 1600 years ago, prior to the age of colonization. Hawaii is almost 7000 miles from Singapore.

Here’s the challenge. How did these haplogroup O men get from the South Pacific to Virginia? Mr. Lynn and the Singapore tester share a common ancestor about 1240 years ago, or 760 CE.

There is no known or theorized Native American settlement wave across Beringia as late as 760 CE. We know that the parent haplogroup was someplace near Singapore in approximately 760 CE.

Two Filipino men and the Revels’ ancestors were in the same location in the Pacific Islands 5180 years ago. How did they arrive on the Eastern Shore in Virginia, found in the Native population, either in or before 1656 when James Revels was born?

What happened in the 3500 years between those dates that might explain how James Revel’s ancestor made that journey?

Academic Papers

In recent years, there has been discussion of possible shoreline migration routes along the Russian coast, Island hopping along Alaska, Canada, and what is now the US, known as the Kelp Highway or Coastal Migration Route – but that has yet to be proven.

Even if that is the case, and it’s certainly a possibility, how did this particular group of men get from the Pacific across the continent to the Atlantic shore in such a short time, leaving no telltale signs along the way? The Coastal Migration Theory hypothesis states that this migration occurred from 12-16 thousand years ago, and then expanded inland over the next 3-5K years. They could not have expanded eastward until the glaciers receded. Regardless, the parent haplogroup and associated ancestors are still found in the Philippines and South Pacific 5000 years ago – after that migration and expansion had already occurred.

The conclusion of the paper is that there is no strong evidence for a Pacific shoreline migration. Regardless, that’s still thousands of years before the time range we’re observing.

We know that the Lynn ancestor was with men from Indonesia in 760 CE, and the Revels ancestor was with men from the Pacific Islands, probably the Philippines, 5180 years ago. They couldn’t have been in two places at the same time, so the ancestors of Revels and Lynn were not in the Americas then.

A 2020 paper shows that remains from Easter Island (Rapa Nui) show Native American DNA, and suggests that initial contact occurred between the two cultures about 1200 CE, or about 800 years ago, but there is not yet any pre-contact or post-contact ancient Y-DNA found in the Americas that shows Polynesian DNA. Furthermore, the hypothesis is that the DNA found on Easter Island came from the Americas, not vice versa. The jury is still out, but this does show that trans-Pacific contact between the two cultures was taking place 800 years ago, at least two hundred years pre-European contact.

Australasian migration to South America is also suggested by one set of remains found in Brazil dating from more than 9000 years ago, but there have been no other remains found indicating this heritage, either in Brazil, or elsewhere in the Americas.

Based on the Time Tree dates of the Haplogroup O testers in our samples, we know they were in the Islands of Southeast Asia after this time period. Additionally, there are no Australia/New Zealand matches.

The Spanish

The Spanish established an early trade route between Manila and Acapulco beginning in 1565. Consequently, east Asian men left their genetic signature in Mexico, as described in this paper.

Historians estimate that 40-129K immigrants arrived from Manilla to colonial Mexico between 1565 and 1815, with most being enslaved upon arrival. Approximately one-third of the population in Manilla was already enslaved. Unfortunately, this paper focused only on autosomal genome-wide results and did not include either Y-DNA, nor mitochondrial. However, the paper quantifies the high degree of trade, and indicates that the Philippines and other Asian population haplotypes are still prevalent in the Mexican population.

In 2016, Dr. Miguel Vilar, the lead scientist with the National Geographic Genographic project lectured in Guam about the surprising Native American DNA found in the Guam population and nearby islands. He kindly provided this link to an article about the event.

Guam was colonized by Spain. In the image from the Boxer Codex, above, the local Chamorro people greet the Manila Galleon in the Ladrones Islands, as the Marianas were called by the Spanish, about 1590.

Native Hawaiians descend from Polynesian ancestors who arrived in the islands about 400 CE, or about 1600 years ago. Captain Cook, began the age of European contact in Hawaii in 1778.

Five Possibilities

There are five possible origins of haplogroup O in the Americas.

  • Traditional migration across Beringia with the known migrations, estimated to have occurred about 12-16K years ago.
  • A Kelp Highway Coastal Migration which may have occurred about 12-16K years ago and dispersed over the next 3-5K years.
  • Circumpolar migration – specifically Inuit and Na-Dene speakers, about 4-6K years ago.
  • Post-contact incorporation from the Pacific Islands resulting from shipping trade on colonial era ships sometime after 1565.
  • Post-contact incorporation from Madagascar resulting from the importation of humans who may or may not have been enslaved upon arrival.

Do we have any additional evidence?

Other Haplogroup O DNA

From my book, DNA for Native American Genealogy:

Testers in haplogroup O-BY60500 and subclade O-FT45548 have proven Native American heritage.

We have multiple confirmed men from a common ancestor who is proven to be an enslaved Accomack “Indian boy,” James Revell, born in 1656, “belonging to the Motomkin” village, according to the Accomack County, Virginia court records. These men tested as members of haplogroup O-F3288 initially, after taking the Big Y-500 test. However, upgrading to the Big Y-700 produced more granular results and branches reflecting mutations that occurred since their progenitor was born in 1656.

Unfortunately, other than known descendants, these men have few close Y-DNA or Big Y-700 matches.

Without additional men testing from different unrelated lines, or ancient haplogroup O being discovered, we cannot confirm that this haplogroup O male’s ancestor was not introduced into the Matomkin Tribe in some way post-contact. Today, one descendant from this line is a member of the Lumbee Tribe.

However, that isn’t the end of the haplogroup O story.

The Genographic Project data shows one Haplogroup O Tlingit tribal member from Taku, Alaska, along with several testers from Mexico that indicate their paternal line is indigenous. Some people from Texas identify their paternal line as Hispanic.

Another individual indicates they were born on the Fountain Indian Reserve, in British Columbia and speaks the St’at’imcets language, an interior branch of Coastal Salish.

Haplogroup O has been identified as Native American in other locations as well.

Much of the information about Haplogroup O testers was courtesy of the Genographic Project, meaning we can’t contact those people to request upgraded tests, and we can’t obtain additional information in addition to what they provided when they tested. As an affiliate researcher, I’m very grateful to the National Geographic Society’s Genographic project for providing collaborative data.

When the book was published, the Discover Time Tree had not yet been released. We have additional information available today, including the dates of haplogroup formation.

FamilyTreeDNA Haplotree and Discover

The FamilyTreeDNA Haplotree (not to be confused with the Discover Time Tree) shows 10 people at the O-M175 level in Mexico, 10 people in the US report Native American heritage, 2 in Jamaica, and one each in Peru, Panama, and Cuba. There’s also one tester from Madagascar.

Altogether, this gives us about 35 haplogroup O males in the Americas, several with Native heritage.

Please note that I’ve omitted Hawaii in this analysis and included only North and South America. The one individual selecting Native Hawaiian (Kanaka Maoli) is in haplogroup O-M133.

Let’s look at our three distinct clusters.

Cluster 1 – Pacific Northwest – Alaska and Canada

We have a cluster of three individuals along the Pacific Coast in Alaska and Canada who have self-identified as Native, provided a tribal affiliation, and, in some cases, the spoken language.

How might haplogroup O have arrived in or near Vancouver, Washington? We know that James Cook “discovered” Hawaii in 1778, naming it the Sandwich Islands. By 1787, a female Hawaiian died en route to the Pacific Northwest, and the following year, a male arrived. Hawaii had become a provisioning stop, and the Spanish took Hawaiians onto ships as replacement workers.

Hawaiian seamen, whalers, and laborers began intermarrying with the Native people along the West Coast as early as 1811. Their presence expanded from Oregon to Alaska. Migration and intermarriage along the Pacific coast began slowly, but turned into a steady stream 30 years later when we have confirmed recruitment and migration of Hawaiian people

In 1839, John Sutter recruited a small group of 10 Hawaiians to travel with him to the then-Mexican colony of Alta, California.

By the mid-1800s, hundreds of Hawaiians lived in Canada and California. In 1847, it was reported that 10% of San Francisco’s residents were Hawaiian. Some of those people integrated with the Native American people, particularly the Miwok and Maidu. The village of Verona, California was tri-lingual: Hawaiian, a Native language, and English, and is today the Sacramento-Verona Tribe.

This article provides a history of the British Company who administered Fort Vancouver, near Vancouver, Washington, that included French-Canadians, Native Americans and Hawaiians. In 1845, 119 Hawaiians were employed at the fort. One of the 119, Opunuia, had signed on as an “engagé,” meaning some type of hired hand or employee, with the Hudson Bay Company for three years, after which he would be free to return home to Honolulu or establish himself in the Oregon Country. He married a woman from the Cascade Tribe.

The descendants of the Hawaiian men and Native women were considered tribal members. In most tribes, children took the tribal status and affiliation of the mother.

The Taku and Sitka, Alaska men on the map are Tlingit, and the man from British Columbia is from the Fountain Indian Reserve.

Hawaiian recruitment is the most likely scenario by which haplogroup O arrived in the tribes of the Pacific Northwest. In that sense, haplogroup O is indeed Native American but not indigenous to that region. The origins of haplogorup O in the Pacific Northwest are likely found in Hawaii, where it is indigenous, and before that, Polynesia – not due to a Beringian crossing.

Cluster 2 – Mexico

We find a particularly interesting small cluster of 4 haplogroup O individuals in interior Mexico.

In the 1500s, Spain established a trade route between Mexico and Manilla in the Philippines.

In 1564, four ships left Mexico to cross the Pacific to claim Guam and the Philippines for King Philip II of Spain. The spice trade, back and forth between Mexico and the Philippines began the following year and continued for the next 250.

Landings occurred along the California coast and the western Mexican coastline. The majority of the galleon crews were Malaysian and Filipino who were paid less than the Spanish sailors. Slaves, including people from the Marianas were part of the lucrative cargo.

One individual in Texas reports haplogroup O and indicates their paternal ancestors were Hispanic/Native from Mexico. A haplogroup O cluster claiming Native heritage is found near Zacatecas, Fresnillo and San Luis Potosi in central Mexico. Additionally, mitochondrial haplogroup F, also Asian, is found there as well. Acapulco is the lime green pin.

An additional haplogroup O tester with Native heritage is found in Lima, Peru.

Haplogroup O men are found in Panama, Jamaica and Cuba, but do not indicate the heritage of their paternal ancestral line. None of these men have taken Big-Y tests, and some may well have arrived on the slave ships from Madagascar, especially in the Caribbean. This source attributes some enslaved people in Jamaica to Hawaiian voyages.

I strongly suspect that the Mexican/Peru grouping in close proximity to the Pacific coastline is the result of the Manilla-Mexico 250-year trade route. The Spanish also plied those waters regularly. Big Y testing of those men would help flesh-out their stories – when and how haplogroup O arrived in the local population.

Cluster 3 – East Coast

At first glance, the East Coast grouping of men with a genetic affinity to the people of the Philippines and Indonesia seems more difficult to explain, but perhaps not.

On the East Coast, we have confirmed reports of whalers near Nantucket as early as 1765 utilizing crewmen from Hawaii, known then as the Sandwich Islands, Tahiti, and the Cape Verde Islands off of Africa. A thorough review of early literature might well reveal additional information about early connections with the Sandwich Islands, and in particular, sailors, crew, or enslaved people.

The Spanish and French were the first to colonize the Philippines by the late 1500s. They had discovered the Solomon Islands, Melanesia, and other Polynesian Islands, and by the early 1600s, the Dutch were involved as well.

The Encyclopedia Britanica further reports that Vasco Balboa first sailed into the Pacific in 1513 and seven years later, Ferdinand Magellan rounded the tip of South America. The Spanish followed, establishing a galley trade between Manila, in the Philippines and Acapulco in western Mexico.

While I found nothing specific stating that the earliest voyages brought men from the Philippines and Oceania back to their European home ports with them, we know that early European captains on exploratory voyages took Native people from the east coast of the Americas on their return journey, so there’s nothing to preclude them from doing the same from the Pacific. The early explorers stayed for months among the Oceanic Native peoples. If they were short on sailors for their return voyage, Polynesian men filled the void.

We know that the Spanish took slaves as part of their trade. We know that the ships in the Pacific took sailors from the islands. If the men themselves didn’t stay in the locations they visited, it’s certainly within the realm of possibility that they fathered children with local, Native women. Furthermore, given that the slave trade was lucrative, it’s also possible that some Pacific Island slaves were taken not as crew but with the intention of being sold into bondage. Other men may have escaped the ships and hidden among the Native Tribes along the eastern seaboard.

Fishing in Newfoundland and exploration in what would become the US was occurring by 1500, so it’s certainly possible that some of the indigenous people from Indonesia and the Philippines were either stranded, sold to enslavers, escaped, or chose to join the Native people along the coastline in North America. Ships had to stop to resupply rations and take on fresh water.

We know that by the mid-1600s, James Revels, whose father carried haplogroup O, had been born on the Atlantic coast of Virginia or Maryland, probably on the Delmarva Peninsula, short for Delaware, Maryland, Virginia, where the Accomac people lived.

There are other instances of haplogroup O found along the east coast.

On the eastern portion of the haplogroup O map from the book, DNA for Native American Genealogy, we find the following locations:

  • Hillburn, NY – man identified as “Native American Black.”
  • Chichester County, PA – Genographic tester identified the location of his earliest known ancestor – included here because O is not typically found in the states.
  • Accomack County, VA – Delmarva peninsula – James Revels lineage
  • Robeson County, NC – Lewis and Revels surname associated with the Lumbee
  • Chatham County, NC – Lynn ancestor’s earliest known location
  • Greene County, NC – enslaved Blount ancestor’s EKA in 1849

The genesis of Mr. Blount’s enslaved ancestor is unclear. Fortunately, he took a Big Y-700 test.

Mr. Blount’s only Big-Y match is to a man from the United Arab Emirates (UAE), but the haplogroup history includes Thailand, which is the likely source of both his and his UAE matches’ ancestors at some point in time. Their common ancestor was in Thailand in 336 CE, almost 1700 years ago.

All surrounding branches of haplogroup O on the Time Tree have Asian testers, except for the one UAE gentleman.

The Blount Haplogroup O-FTC77008 does not connect with the common ancestral haplogroup of Lynn and Revels, so these lineages are only related someplace in Oceana prior to O-F265, or more about  30,000 years ago. Their only commonality other than their Asian origins is that they arrived on the East Coast of the Americas.

We know that the Spanish were exploring the Atlantic coastline in the 1500s and were attempting to establish colonies. In 1566, a Spanish expedition reached the Delmarva Peninsula. This spit of land was contested and changed hands several times, belonging variously to the Spanish, Dutch, and British by 1664.

Furthermore, we also know that the ships were utilizing slave labor. One of the Spanish ships wrecked in the waters off North Carolina near Hatteras or Roanoke Island before the Lost Colony was abandoned on Roanoke Island in 1587. The Croatan Indians reported that in memorable history, several men, some of whom were reported to be slaves, had survived the wreck and “disappeared” into the hinterlands – clearly running for their lives.

These men, if they survived, would have been incorporated into the Native population as there were no other settlements at the time. Variations of this scenario may have played out many times.

James Revels’ ancestor could have arrived on any ship, beginning with exploration and colonization in the early 1500s through the mid-1650s.

By the time the chief bound the Indian boy who was given the English name James to Edward Revell, James’s Oceanic paternal ancestor could have been 4, 5 or 6 generations in the past – or could have been his father.

The Accomack was a small tribe, loosely affiliated with the Powhatan Confederacy along the Eastern Shore. By 1700, their population had declined by approximately 90% due to disease. A subgroup, the Gingaskins, intermarried with African Americans living nearby. After Nat Turner’s slave rebellion of 1831, they were expelled from their homelands.

The swamps near Lumberton in Robeson County, NC, became a safe haven for many mixed-race Native, African, and European people. The swamps protected them, and they existed, more or less undisturbed, for decades. Revels and Lewis descendants are both found there.

Many Native Americans were permanently enslaved alongside African people – and within a generation or so, their descendants knew they were Native and African, but lost track of which ancestors descended from which groups. Life was extremely difficult back then. Generations were short, and enslaved people were moved from place to place and sold indiscriminately, severing their family ties entirely, including heritage stories.

Returning to the Discover Time Tree Maps

Wesley Revels has STR matches with several men from Indonesia, China, and the Philippines. It would be very helpful if those men would upgrade to the Big Y-700 so that we can more fully complete the haplogroup O branches of the Time Tree.

The common Revels/Lewis ancestor, accompanied by two descendant men on different genetic branches from the Philippines, was born about 5180 years ago. There is no evidence to suggest Haplogroup O-FT11768 was born anyplace other than in the Philippines.

How did the descendant haplogroups of O-FT45548 (Revels, Lewis, and an unnamed man) and O-F22410 (Lynn) arrive in Virginia or anyplace along the Atlantic seaboard?

Hawaii wasn’t settled until about 1600 years ago. We know Hawaiians integrated with the Pacific Coast Native tribes in the 1800s, but James Revels was in Virginia in 1656..

We know that the Spanish established a mid-1500s trade route between Manila and Acapulco, leaving their genetic signature in western Mexico.

None of these events fit the narrative for the Revels or the Lynn paternal ancestor.

Furthermore, the Revels and Lynn lines do not connect on North American soil, as both descend from the same parent haplogroup, O-FT11768, 5180 years ago in the Philippines. This location and history suggest a connection with the Spanish galleon trade era. The haplogroup formation clearly predates that trade, which means those men were still in the Philippines, not already living on the American continents. Therefore, the descendants of the haplogroup O-FT11768 arrived in Virginia and North Carolina sometime after that haplogroup formation 5100 years ago.

The Lynn ancestor connects with a man from Singapore in 760 CE, or just 1240 years ago. A descendant of haplogroup O-F22410 arrived in North Carolina sometime later.

It does not appear, at least not on the surface, that there is a connection through Madagascar, although we can’t rule that out without additional testers. If the connection is through Madagascar, then their ancestors were likely transported from Indonesia to Madagascar, then as enslaved people from Madagascar to the Atlantic colonies to be sold. However, James Revels was not enslaved. He was clearly Native and bound to a European plantation owner, who did, in fact, free him as agreed and subsequently loaned him money.

Based on the dates involved, and when we know they were in Oceania, an arrival along the west coast, followed by a quick migration across the country to a peninsula of land in the Atlantic, is probably the least likely scenario. There is also no historical or ancient haplogroup O DNA found anyplace between the west and east coasts, nor in the Inuit or Na-Dene speakers. The Navajo, who speak the Na-Dené language, migrated to the Southwest US around 1400 CE, but haplogroup O has not been found among Na-Dené speakers.

It’s a long way from Singapore and the Philippines to Madagascar, so while the coastal migration scenario is not impossible, it’s also not probable, especially given what we know about the Spanish Pacific trade that existed profitably for 250 years.

However, one haplogroup O subgroup arrived in the UAE by some methodology after 336 CE.

It’s entirely possible, indeed probable, that haplogroup O arrived in the Americas for various reasons, on different paths, in different timeframes.

Haplogroup O was found in people in the Americas after colonization had begun. There has been no ancient Haplogroup O DNA discovered, and there’s evidence indicating that these instances of haplogroup O could not have arrived in any of the known Beringia migrations nor the theorized Coastal or Kelp migration. We know the East Coast Cluster is not a result of the West Coast 19th-century migration because James Revels was in court one hundred and fifty years before the Hawaiians were living among the Native people along the Pacific coastline.

There’s nothing to indicate that the Mexican group that likely arrived beginning in the mid-1500s for the next 250 years as a result of the Indonesian trade route migrated to the east coast, or vice versa. That’s also highly unlikely.

The most likely scenario is that Mr. Lynn’s, Mr. Blount’s, and James Revels’ ancestors were brought on trade ships, either as sailors or enslaved men. They may not have stayed, simply visited. They may each have arrived in a completely different scenario, meaning Mr. Blount’s ancestors could have been enslaved arrivals from Madagascar, Mr. Lynn’s from Indonesia, and Mr. Revel’s as a crew member on a Spanish ship. We simply don’t know.

James Revels’ descendants were Native through his mother’s tribe, as confirmed in the 1667 court records. However, the Revels and Lynn lineages weren’t Native as a result of their paternal haplogroup O ancestors crossing Beringia into the Americas with Native American haplogroups Q and C. Instead, the Lynn and Revels migration story is quite different. Their ancestors arrived by ship. The journey was long, perilous, and far more unique than we could have imagined, taking them halfway around the world by water.

Timeline

There’s a lot of information to digest, so I’ve compiled a timeline incorporating both genetic and historical information for easy reference.

  • 30,000 years ago (28,000 BCE) – haplogroup O-F265, common Asian ancestor  of Mr. Blount, the Revels/Lewis group, Mr. Lynn, and an unknown Big-Y tester in the Malagasy group project
  • 12,000-16,000 years ago – Indigenous Americans arrived across now-submerged Beringia
  • 12,000-16,000 years ago – possible Coastal Migration route may have facilitated a secondary source of indigenous arrival along the Pacific coastline of the Americas
  • 4000-7000 years ago – circumpolar migration arrival of Inuit and Na-Dené speakers found in the Arctic polar region and the Navajo in the Southwest who migrated from Alaska/Canada about 1400 CE
  • 5180 years ago (3180 BCE) – haplogroup O-FT11768, the common ancestor of Mr. Lynn and the Revels/Lewis group with many subgroups in the Philippines, Hawaii, Singapore, Brunei, China, Sumatra, and Thailand
  • 2244 years ago (244 BCE) – haplogroup O-CTS716, the common ancestor of Wesley Revels and Mr. Luo from Indonesia
  • The year 336 CE, 1684 years ago – haplogroup O-FTC77008, the common ancestor of Mr. Blount, UAE tester and a man from Thailand
  • 400 CE, 1600 years ago  –  Hawaii populated by Polynesian people
  • 760 CE, 1240 years ago – haplogroup O-F22410, common ancestor of Mr. Lynn with a Singapore man
  • 1492 CE, 528 years ago – Columbus begins his voyages to the “New World,” arriving in the Caribbean
  • By 1504 CE – European fishing began off of Newfoundland
  • 1565 – Spain claimed Guam and the Philippines
  • 1565 – Spanish trade between Manilla and Acapulco begins and continues for 250 years, until 1815, using crews of men from Guam, the Philippines, and enslaved people from the Marianas.
  • 1565 – St. Augustine (Florida) was founded by the Spanish as a base for trade and conquest along the eastern seaboard
  • 1566 – A Spanish expedition reached the Delmarva peninsula intending to establish a colony, but bad weather thwarted that attempt.
  • 1585-1587 – voyages of discovery by the English and the Lost Colony on Roanoke Island, North Carolina
  • 1603 – English first explored the Delmarva Peninsula, home to the Accomac people, now Accomack County, VA, where James Revels’s court record was found in 1667
  • 1607 – Jamestown, Virginia, founded by the English
  • 1608 – Colonists first arrived on the Delmarva Peninsula and allied with Debedeavon, whom they called the “laughing King” of the Accomac people. At that time, the Accomac had 80 warriors. Debedeavon was a close friend to the colonists and saved them from a massacre in 1622. He died in 1657.
  • 1620 – The Mayflower arrived near present-day Provincetown, Massachusetts
  • 1631-1638 – Dutch West India Company established a colony on the Delmarva Peninsula, but after conflicts, it was destroyed by Native Americans in 1638. The Swede’s colony followed, and the region was under Dutch and Swedish control until it shifted to British control in 1664
  • 1656 – Birth of James Revels, confirmed in a 1667 court record stating that he was an Accomack “Indian boy” from “Matomkin,” judged to be age 11, bound to Edward Revell. This location is on the Delmarva Peninsula.
  • 1741 CE –  Haplogroup O-BY60500 formation date that includes all of the Revels and Lewis testers who descend from James Revels born in 1656
  • 1765 – Whalers near Nantucket using crewmen from Hawaii (Sandwich Islands), Tahiti, and the Cape Verde Islands off of Africa
  • 1766 CE – Formation date for haplogroup O-FT45548, child haplogroup of O-BY60500, for some of the Lewis and Revels men who all descend from James Revels born in 1656
  • 1778 – Captain Cook makes contact with Hawaiian people
  • 1787 – The first male arrived in the Pacific Northwest from Hawaii
  • 1811 – Hawaiian seamen begin intermarrying with Native American females along the Pacific shore, eventually expanding their presence from Oregon to Alaska
  • 1839 – John Suter recruits Hawaiian men to travel with him to California
  • 1845 – Hawaiians employed by Fort Vancouver, with some marrying Native American women

Conclusions

It’s without question that James Revels was Native American very early in the settlement of the Delmarva Peninsula, now Accomack County, Virginia, but his common ancestor with Filipino men 5100 years ago precludes his direct paternal ancestor’s presence in the Americas at that time. In other words, his Revel male ancestor did not arrive in the Beringian indigenous migration 12,000-16,000 years ago. His ancestor likely arrived post-contact, based on a combination of both historical and genetic evidence.

Haplogroup O is not found in the Arctic Inuit nor the Na-Dene speakers, precluding a connection with either group, and has never been found in ancient DNA in the Americas.

Haplogroup O in the Revels lineage is most likely connected with the Spanish galleon trade with the Philippines and the early Spanish attempts to colonize the Americas.

The source of Haplogroup O in the Pacific Northwest group is likely found in the recruitment of Hawaiian men in the early/mid-1800s.

The Mexican Haplogroup O group likely originated with the Manilla/Mexico Spanish galleon trade.

The source of the Blount Haplogroup O remains uncertain, other than to say it originated in Thailand thousands of years ago and is also found in the UAE. The common Blount, UAE, and Thailand ancestor’s haplogroup dates to 336 CE, so they were all likely in or near Thailand at that date, about 1687 years ago.

What’s Next?

Science continuously evolves, revealing new details as we learn more, often clarifying or shifting our knowledge. Before the Discover tool provided haplogroup ages based on tests from men around the world, we didn’t have the necessary haplogroup origin and age data to understand the genesis of haplogroup O in the Americas. Now, we do, but there is invariably more to learn.

New evidence is always welcome and builds our knowledge base. Haplogroup O ancient DNA findings would be especially relevant and could further refine what we know, depending on the location, dates of the remains, who they match, and historical context.

Additional Big Y-700 tests of haplogroup O men, especially those with known genealogy or ancestor location, including Madagascar, would be very beneficial and allow the haplogroup formation dates to be further refined.

If you are a male with haplogroup O, please consider upgrading to the Big Y-700 test, here.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

East Coast Genetic Genealogy Conference – In Person and Virtual – October 6-8, 2023

There’s a conference focused solely on genetic genealogy, and you’re invited!! Now that’s talking my language!!!

The second annual East Coast Genetic Genealogy Conference (ECGGC) will take place on October 6-8, 2023, at the Maritime Conference Center in Linthicum Heights, Maryland, just outside Baltimore.

This year’s conference is a hybrid affair, with both in-person and virtual speaker sessions and vendor booths.

The in-person conference includes lunch and costs $225, while the virtual conference is $175.

As the name suggests, this conference caters to genetic genealogists. The lineup includes wonderful speakers who I’m sure you’ll recognize, here. I can hardly wait to attend some of these sessions. The great news is that you really don’t have to pick and choose from the more than 40 sessions, because you can view recorded sessions after the conference.

Please note that while my session on Sunday at 11, Wringing Every Drop Out of Mitochondrial DNA, is listed as In-Person, it is not. Due to a change in plans, it’s virtual.

Be sure to check out the DNA Academy on Saturday evening from 6 to 8:30 PM. This event was quite popular last year.

Is there a presentation or a few that you’re particularly looking forward to?

Recorded sessions will be available until December 31st, so even if you can’t join us that weekend, or you’re on the other side of the world and the timing just doesn’t work, you don’t have to miss out. Often, in-person sessions aren’t recorded and available later, but at ECGGC, both in-person and virtual sessions will be recorded so you can watch any session through year-end. Thanks to the fine folks on the ECGGC conference committee for providing this benefit.

You can purchase a ticket, here.

This is a wonderful opportunity, and I hope to see you there.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Which DNA Test Should I Buy? And Why?

Which DNA test should I buy, and why?

I receive questions like this often. As a reminder, I don’t take private clients anymore, which means I don’t provide this type of individual consulting or advice. However, I’m doing the next best thing! In this article, I’m sharing the step-by-step process that I utilize to evaluate these questions so you can use the process too.

It’s important to know what questions to ask and how to evaluate each situation to arrive at the best answer for each person.

Here’s the question I received from someone I’ll call John. I’ve modified the wording slightly and changed the names for privacy.

I’m a male, and my mother was born in Charleston, SC. My maternal grandmother’s maiden name was Jones and a paternal surname was Davis. The family was supposed to have been Black, Dutch, Pennsylvania Dutch, and Scots-Irish…only once was I told I was 3/16 Indian, with Davis being 3/4 and Jones being full Indian.

Do I have enough reasonable information to buy a test, and which one?

Please note that it’s common for questions to arrive without all the information you need to provide a sound answer – so it’s up to you to ask those questions and obtain clarification.

Multiple Questions

There are actually multiple questions here, so let me parse this a bit.

  1. John never mentioned what his testing goal was.
  2. He also never exactly said how the paternal line of Davis was connected, so I’ve made an assumption. For educational purposes, it doesn’t matter because we’re going to walk through the evaluation process, which is the same regardless.
  3. John did not include a tree or a link to a tree, so I created a rudimentary tree to sort through this. I need the visuals and normally just sketch it out on paper quickly.
  4. Does John have enough information to purchase a test?
  5. If so, which test?

There is no “one size fits all” answer, so let’s discuss these one by one.

Easy Answers First

The answer to #4 is easy.

Anyone with any amount of information can purchase a DNA test. Adoptees do it all the time, and they have no prior information.

So, yes, John can purchase a test.

The more difficult question is which test, because that answer depends on John’s goals and whether he’s just looking for some quick information or really wants to delve into genealogy and learn. Neither approach is wrong.

Many people think they want a quick answer –  and then quickly figure out that they really want to know much more about their ancestors.

I wrote an article titled DNA Results – First Glances at Ethnicity and Matching for new testers, here.

Goals

Based on what John said, I’m going to presume his goals are probably:

  • To prove or disprove the family oral history of Black, Dutch, Pennsylvania Dutch (which is actually German,) Scots-Irish, and potentially Native American.
  • John didn’t mention actual genealogy, which would include DNA matches and trees, so we will count that as something John is interested in secondarily. However, he may need genealogy records to reach his primary goal.

If you’re thinking, “The process of answering this seemingly easy question is more complex than I thought,” you’d be right.

Ethnicity in General

It sounds like John is interested in ethnicity testing. Lots of people think that “the answer” will be found there – and sometimes they are right. Often not so much. It depends.

The great news is that John really doesn’t need any information at all to take an autosomal DNA test, and it doesn’t matter if the test-taker is male or female.

To calculate each tester’s ethnicity, every testing company compiles their own reference populations, and John will receive different results at each of the major companies. Each company updates their ethnicity results from time to time as well, and they will change.

Additionally, each company provides different tools for their customers.

The ethnicity results at different companies generally won’t match each other exactly, and sometimes the populations look quite different.

Normally, DNA from a specific ancestor can be found for at least 5 or 6 generations. Of course, that means their DNA, along with the DNA from all of your other ancestors is essentially combined in a communal genetic “pot” of your chromosomes, and the DNA testing company needs to sort it out and analyze your DNA for ethnicity.

DNA descended from ancestors, and their populations, further back in people’s trees may not be discerned at all using autosomal DNA tests.

A much more specific “ethnicity” can be obtained for both the Y-DNA line, which is a direct patrilineal line for men (blue arrow,) and the mitochondrial DNA line (pink arrows,) which is a direct matrilineal line for everyone, using those specific tests.

We will discuss both of those tests after we talk about the autosomal tests available from the four major genealogy DNA testing companies. All of these tools can and should be used together.

Let’s Start with Native American

Let’s evaluate the information that John provided.

John was told that he “was 3/16 Indian, with Davis being 3/4 and Jones being full Indian.”

We need to evaluate this part of his question slightly differently.

I discussed this in the article, Ancestral DNA Percentages – How Much of Them is in You?

First, we need to convert generations to 16ths.

You have two ancestors in your parent’s generation, four in your grandparents, and so forth. You have 16 great-great-grandparents. So, if John was 3/16th Native, then three of his great-great-grandparents would have been fully Native, or an equivalent percentage. In other words, six ancestors in that generation could have been half-Native. Based on what John said, they would have come from his mother’s side of the tree. John is fortunate to have that much information to work with.

He told us enough about his tree that we can evaluate the statement that he might be 3/16ths Native.

Here’s the tree I quickly assembled in a spreadsheet based on John’s information.

His father, at left, is not part of the equation based on the information John provided.

On his mother’s side, John said that Grandfather Davis is supposed to be three-quarters Native, which translates to 12/16ths. Please note that it would be extremely beneficial to find a Y-DNA tester from his Davis line, like one of his mother’s brothers, for example.

John said that his Grandmother Jones is supposed to be 100% Native, so 16/16ths.

Added together, those sum to 28/32, which reduces down to 14/16th or 7/8th for John’s mother.

John would have received half of his autosomal DNA from his mother and half from his non-Native father. That means that if John’s father is 100% non-Native, John would be half of 14/16ths or 7/16ths, so just shy of half Native.

Of course, we know that we don’t always receive exactly 50% of each of our ancestors’ DNA (except for our parents,) but we would expect to see something in the ballpark of 40-45% Native for John if his grandmother was 100% Native and his grandfather was 75%.

Using simple logic here, for John’s grandmother to be 100% Native, she would almost assuredly have been a registered tribal member, and the same if his grandfather was 75% Native. I would think that information would be readily available and well-known to the family – so I doubt that this percentage is accurate. It would be easy to check, though, on various census records during their lifetimes where they would likely have been recorded as “Indian.” They might have been in the special “Indian Census” taken and might be living on a reservation.

It should also be relatively easy to find their parents since all family members were listed every ten years in the US beginning with the 1850 census.

The simple answer is that if John’s grandparents had as much Native as reported, he would be more than 3/16th – so both of these factoids cannot simultaneously be accurate. But that does NOT mean neither is accurate.

John could be 7/8th or 40ish%, 3/16th or 18ish%, or some other percentage. Sometimes, where there is smoke, there is fire. And that seems to be the quandary John is seeking to resolve.

Would  Ethnicity/Population Tests Show This Much Native?

Any of the four major testing companies would show Native for someone whose percentage would be in the 40% or 18% ballpark.

The easiest ethnicities to tell apart from one another are continental-level populations. John also stated that he thinks he may also have Black ancestry, plus Dutch, Pennsylvania Dutch (German), and Scots-Irish. It’s certainly possible to verify that using genealogy, but what can DNA testing alone tell us?

How far back can we expect to find ethnicities descending from particular ancestors?

In this table, you can see at each generation how many ancestors you have in that generation, plus the percentage of DNA, on average, you would inherit from each ancestor.

All of the major DNA testing companies can potentially pick up small trace percentages, but they don’t always. Sometimes one company does, and another doesn’t. So, if John has one sixth-generation Native American ancestor, he would carry about 1.56% Native DNA, if any.

  • Sometimes a specific ethnicity is not found because, thanks to random recombination, you didn’t inherit any of that DNA from those ancestors. This is why testing your parents, grandparents, aunts, uncles, and siblings can be very important. They share your same ancestors and may have inherited DNA that you didn’t that’s very relevant to your search.
  • Sometimes it’s not found because the reference populations and algorithms at that testing company aren’t able to detect that population or identify it accurately, especially at trace levels. Every DNA testing company establishes their own reference populations and writes internal, proprietary ethnicity analysis algorithms.
  • Sometimes it’s not found because your ancestor wasn’t Native or from that specific population.
  • Sometimes it’s there, but your population is called something you don’t expect.

For example, you may find Scandinavian when your ancestor was from England or Ireland. The Vikings raided the British Isles, so while some small amount of Scandinavian is not what you expect, that doesn’t mean it‘s wrong. However, if all of your family is from England, it’s not reasonable to have entirely Scandinavian ethnicity results.

It’s also less likely as each generation passes by that the information about their origins gets handed down accurately to following generations. Most non-genealogists don’t know the names of their great-grandparents, let alone where their ancestors were from.

Using a 25-year average generation length, by the 4th generation, shown in the chart above, you have 16 ancestors who lived approximately 100 years before your parents were born, so someplace in the mid-1800s. It’s unlikely for oral history from that time to survive intact. It’s even less likely from a century years earlier, where in the 7th generation, you have 128 total ancestors.

The best way to validate the accuracy of your ethnicity estimates is by researching your genealogy. Of course, you need to take an ethnicity test, or two, in order to have results to validate.

Ethnicity has a lot more to offer than just percentages.

Best Autosomal Tests for Native Ethnicity

Based on my experience with people who have confirmed Native ancestry, the two best tests to detect Native American ethnicity, especially in smaller percentages, are both FamilyTreeDNA and 23andMe.

Click images to enlarge

In addition to percentages, both 23andMe and FamilyTreeDNA provide chromosome painting for ethnicity, along with segment information in download files. In other words, they literally paint your ethnicity results on your chromosomes.

They then provide you with a file with the “addresses” of those ethnicities on your chromosomes, which means you can figure out which ancestors contributed those ethnicity segments.

The person in the example above, a tester at FamilyTreeDNA, is highly admixed with ancestors from European regions, African regions and Native people from South America.

Trace amounts of Native American with a majority of European heritage would appear more like this.

You can use this information to paint your chromosome segments at DNAPainter, along with your matching segments to other testers where you can identify your common ancestors. This is why providing trees is critically important – DNA plus ancestor identification with our matches is how we confirm our ancestry.

This combination allows you to identify which Native (or another ethnicity) segments descended from which ancestors. I was able to determine which ancestor provided that pink Native American segment on chromosome 1 on my mother’s side.

I’ve provided instructions for painting ethnicity segments to identify their origins in specific ancestors, here.

Autosomal and Genealogy

You may have noticed that we’ve now drifted into the genealogy realm of autosomal DNA testing. Ethnicity is nice, but if you want to know who those segments came from, you’ll need:

  • Autosomal test matching to other people
  • To identify your common ancestor with as many matches as you can
  • To match at a company who provides you with segment information for each match
  • To work with DNAPainter, which is very easy

The great news is that you can do all of that using the autosomal tests you took for ethnicity, except at Ancestry who does not provide segment information.

Best Autosomal Test for Matching Other Testers

The best autosomal test for matching may be different for everyone. Let’s look at some of the differentiators and considerations.

If you’re basing a testing recommendation solely on database size, which will probably correlate to more matches, then the DNA testing vendors fall into this order:

If you’re basing that recommendation on the BEST, generally meaning the closest matches for you, there’s no way of knowing ahead of time. At each of the four DNA testing companies, I have very good matches who have not tested elsewhere. If I weren’t in all four databases, I would have missed many valuable matches.

If you’re basing that recommendation on which vendor began testing earliest, meaning they have many tests from people who are now deceased, so you won’t find their autosomal tests in other databases that don’t accept uploads, the recommended testing company order would be:

If you’re basing that recommendation on matches to people who live in other countries, the order would be:

Ancestry and 23andMe are very distant third/fourth because they did not sell widely outside the US initially and still don’t sell in as many countries as the others, meaning their testers’ geography is more limited. However, Ancestry is also prevalent in the UK.

If you’re basing that recommendation on segment information and advanced tools that allow you to triangulate and confirm your genetic link to specific ancestors, the order would be:

Ancestry does NOT provide any segment information.

If you’re basing that recommendation on unique tools provided by each vendor, every vendor has something very beneficial that the others don’t.

In other words, there’s really no clear-cut answer for which single autosomal DNA test to order. The real answer is to be sure you’re fishing in all the ponds. The fish are not the same. Unique people test at each of those companies daily who will never be found in the other databases.

Test at or upload your DNA to all four DNA testing companies, plus GEDmatch. Step-by-step instructions for downloading your raw data file and uploading it to the DNA testing companies who accept uploads can be found, here.

Test or Upload

Not all testing companies accept uploads of raw autosomal DNA data files from other companies. The good news is that some do, and it’s free to upload and receive matches.

Two major DNA testing companies DO NOT accept uploads from other companies. In other words, you have to test at that company:

Two testing companies DO accept uploads from the other three companies. Uploads and matching are free, and advanced features can be unlocked very cost effectively.

  • FamilyTreeDNA – free matching and $19 unlock for advanced features
  • MyHeritage – free matching and $29 unlock.for advanced features

I recommend testing at both 23andMe and Ancestry and uploading one of those files to both FamilyTreeDNA and MyHeritage, then purchasing the respective unlocks.

GEDmatch

GEDmatch is a third-party matching site, not a DNA testing company. Consider uploading to GEDmatch because you may find matches from Ancestry who have uploaded to GEDmatch, giving you access to matching segment information.

Other Types of DNA

John provided additional information that may prove to be VERY useful. Both Y-DNA and mitochondrial DNA can be tested as well and may prove to be more useful than autosomal to positively identify the origins of those two specific lines.

Let’s assume that John takes an autosomal test and discovers that indeed, the 3/16th Native estimate was close. 3/16th equates to about 18% Native which would mean that three of his 16 great-great-grandparents were Native.

John told us that his Grandmother Jones was supposed to be 100% Native.

At the great-great-grandparent level, John has 16 ancestors, so eight on his mother’s side, four from maternal grandmother Jones and four from his maternal grandfather Davis.

John carries the mitochondrial DNA of his mother (red boxes and arrows,) and her mother, through a direct line of females back in time. John also carries the Y-DNA of his father (dark blue box, at left above, and blue arrows below.)

Unlike autosomal DNA which is admixed in every generation, mitochondrial DNA (red arrows) is inherited from that direct matrilineal line ONLY and never combines with the DNA of the father. Mothers give their mitochondrial DNA to both sexes of their children, but men never contribute their mitochondrial DNA to offspring. Everyone has their mother’s mitochondrial DNA.

Because it never recombines with DNA from the father, so is never “watered down,” we can “see” much further back in time, even though we can’t yet identify those ancestors.

However, more importantly, in this situation, John can test his own mitochondrial DNA that he inherited from his mother, who inherited it from her mother, to view her direct matrilineal line.

John’s mitochondrial DNA haplogroup that will be assigned during testing tells us unquestionably whether or not his direct matrilineal ancestor was Native on her mother’s line, or not. If not, it may well tell us where that specific line originated.

You can view the countries around the world where Y-DNA haplogroups are found, here, and mitochondrial haplogroups, here.

If John’s mitochondrial DNA haplogroup is Native, that confirms that one specific line is Native. If he can find other testers in his various lines to test either their Y-DNA or mitochondrial DNA, John can determine if other ancestors were Native too. If not, those tests will reveal the origins of that line, separate from the rest of his genealogical lines.

Although John didn’t mention his father’s line, if he takes a Y-DNA test, especially at the Big Y-700 level, that will also reveal the origins of his direct paternal line. Y-DNA doesn’t combine with the other parent’s DNA either, so it reaches far back in time too.

Y-DNA and mitochondrial DNA tests are laser-focused on one line each, and only one line. You don’t have to try to sort it out of the ethnicity “pot,” wondering which ancestor was or was not Native.

My Recommendation

When putting together a testing strategy, I recommend taking advantage of free uploads and inexpensive unlocks when possible.

  • To confirm Native American ancestry via ethnicity testing, I recommend testing at 23andMe and uploading to FamilyTreeDNA, then purchasing the $19 unlock. The free upload and $19 unlock are less expensive than testing there directly.
  • For matching, I recommend testing at Ancestry and uploading to MyHeritage, then unlocking the MyHeritage advanced features for $29, which is less expensive than retesting. Ancestry does not provide segment information, but MyHeritage (and the others) do.

At this point, John will have taken two DNA tests, but is now in all four databases, plus GEDmatch if he uploads there.

  • For genealogy research on John’s lines to determine whether or not his mother’s lines were Native, I recommend an Ancestry and a MyHeritage records subscription, plus using WikiTree, which is free.
  • To determine if John’s mother’s direct matrilineal female line was Native, I recommend that John order the mitochondrial DNA test at FamilyTreeDNA.
  • When ordering multiple tests, or uploading at FamilyTreeDNA, be sure to upload/order all of one person’s tests on the same DNA kit so that those results can be used in combination with each other.

Both males and females can take autosomal and mitochondrial DNA tests.

  • To discover what he doesn’t know about his direct paternal, meaning John’s surname line – I recommend the Big Y-700 test at FamilyTreeDNA.

Only males can take a Y-DNA test, so women would need to ask their father, brother, or paternal uncle, for example, to test their direct paternal line.

  • If John can find a male Davis from his mother’s line, I recommend that he purchase the Big Y-700 test at FamilyTreeDNA for that person, or check to see if someone from his Davis line may have already tested by viewing the Davis DNA Project. Like with mitochondrial DNA, the Y-DNA haplogroup will tell John the origins of his direct Davis male ancestor – plus matching of course. He will be able to determine if they were Native, and if not, discover the origins of the Davis line.
  • For assigning segments to ancestors and triangulating to confirm descent from a common ancestor, I recommend 23andMe, MyHeritage, FamilyTreeDNA and GEDmatch, paired with DNAPainter as a tool.

Shopping and Research List

Here are the tests and links recommended above:

More Than He Asked

I realize this answer is way more than John expected or even knew to ask. That’s because there is often no “one” or “one best” answer. There are many ways to approach the question after the goal is defined, and the first “answer” received may be a bit out of context.

For example, let’s say John has 2% Native ancestry and took a test at a vendor who didn’t detect it. John would believe he had none. But a different vendor might find that 2%. If it’s on his mother’s direct matrilineal line, mitochondrial DNA testing will confirm, or refute Native, beyond any doubt, regardless of autosomal ethnicity results – but only for that specific ancestral line.

Autosomal DNA can suggest Native across all your DNA, but Y-DNA and mitochondrial DNA confirm it for each individual ancestor.

Even when autosomal testing does NOT show Native American, or African, for example, it’s certainly possible that it’s just too far back in time or has not been passed down during random recombination, but either Y-DNA or mitochondrial DNA will unquestionably confirm (or refute) the ancestry in question if the right person is tested.

This is exactly why I attempt to find a cousin who descends appropriately from every ancestor and provide testing scholarships. It’s important to obtain Y-DNA and mitochondrial DNA information for each ancestor.

Which Test Should I Order?

What steps will help you decide which test or tests to take?

  1. Define your testing goal.
  2. Determine if your Y-DNA or mitochondrial DNA will help answer the question.
  3. Determine if you need to find ancestors another generation or two back in time to get the most benefit from DNA testing. In our example, if John discovered that both of his grandparents were enrolled tribal members, that’s huge, and the tribe might have additional information about his family.
  4. Subscribe to Ancestry and MyHeritage records collections as appropriate to perform genealogical research. Additional information not only provides context for your family, it also provides you with the ability to confirm or better understand your ethnicity results.
  5. Extend your tree so that you can obtain the best results from the three vendors who support trees; Ancestry, FamilyTreeDNA, and MyHeritage. All three use trees combined with DNA tests to provide you with additional information.
  6. Order 23andMe and Ancestry autosomal DNA tests.
  7. Either test at or upload one of those tests to MyHeritage, FamilyTreeDNA, and GEDmatch.
  8. If a male, order the Big Y-700 DNA test. Or, find a male from your ancestral line who has taken or will take that test. I always offer a testing scholarship and, of course, share the exciting results!
  9. Order a mitochondrial DNA test for yourself and for appropriately descended family members to represent other ancestors. Remember that your father (and his siblings) all carry your paternal grandmother’s mitochondrial DNA. That’s often a good place to start after testing your own DNA.
  10. If your parents or grandparents are alive, or aunts and uncles, test their autosomal DNA too. They are (at least) one generation closer to your ancestors than you are and will carry more of your ancestors’ DNA.
  11. Your siblings will carry some of your ancestors’ DNA that you do not, so test them too if both of your parents aren’t available for testing.

Enjoy!!!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Comparing DNA Results – Different Tests at the Same Testing Company

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

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

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

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

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

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

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

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

Multiple Tests at the Same DNA Testing Company

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

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

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

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

Chips and Chip Evolution

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

23andMe

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

23andMe named their ethnicity results Ancestry Composition.

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

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

Click to enlarge any graphic

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

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

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

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

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

Matches at 23andMe

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

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

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

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

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

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

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

23and Me Summary

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

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

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

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

Reprocessing Tests

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

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

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

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

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

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

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

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

Ancestry

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

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

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

Ancestry results were updated in June 2022

However, my V2 results do include Native American ethnicity.

Matches at Ancestry

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

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

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

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

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

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

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

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

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

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

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

Ancestry Summary

The results of the two Ancestry tests are very close.

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

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

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

Companies that Accept Uploads

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

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

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

FamilyTreeDNA

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

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

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

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

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

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

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

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

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

FamilyTreeDNA Matches

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

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

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

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

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

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

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

FamilyTreeDNA Summary

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

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

MyHeritage

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

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

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

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

MyHeritage Matching

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

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

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

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

MyHeritage Summary

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

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

Your Matches Aren’t Everyplace

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

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

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

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

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

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

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

The Answer

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

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

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

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

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

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research