Rootstech 2024: Friends, Discover Tools, Highways of History and the Storm

I didn’t want to open the curtains Saturday morning, given the blizzard warnings that were worsening all day Friday.

I finally screwed up my courage and peeked out.

Indeed, those skies look dark, grey, and foreboding.

Decision Time

I had a decision to make.

I originally planned to stay in Salt Lake City until Sunday, but I had already changed my flight to late Saturday afternoon following my session. I also changed my hotel reservation accordingly.

However, if I packed and checked out, got to the airport, and my flight was canceled, I was likely going to be stranded, potentially at the airport for at least two days. There aren’t any hotels in the Salt Lake City airport, but there are a few nearby. However, probably not enough rooms to accommodate an airport full of stranded people.

Would Uber even be available?

Could I get back into Salt Lake City to check back into the Marriott or any other hotel? Would they have space?

I was at the go-no-go decision point.

It was probably a 50-50 roll of the dice.

I packed and checked out.

It wasn’t snowing yet, but no one doubted that it would. The only questions were when the snow would begin, whether it would begin as rain and freeze into ice before the snow started falling, and how much snow would there be.

Maybe more important to the people at RootsTech – what about flights?

All day, you could see people obsessively checking their flight information on their phones.

I had two speaking engagements scheduled for the day: a morning Y-DNA “Ask Me Anything” panel and my afternoon session, “Highways of History – Flesh out Your Ancestors Using Discover Case Studies.”

The afternoon session was scheduled to end just half an hour before RootsTech closed for the year, so there really was no getting out early.

In for a penny, in for a pound.

Friends in the Expo Hall

I was still trying to visit every booth on the show floor.

I’ll just admit right now that I failed miserably. Not only was I bone tired by this time, but I kept running into people I knew. I realized that this was my last opportunity to see them this year, so I never made it past the halfway point in the Expo Hall.

I did notice that the crowds were very thin. Saturday was Family Day, but apparently, not many people wanted to risk venturing out. Even the locals were concerned which is never a good sign.

The Heritage Theater had a full schedule of events, but there were very few people in the audience through no fault of the speakers or RootsTech.

For those hearty souls who did attend, they received up-close and personal sessions and information from the presenters.

It was nice to see the folks from Family Tree Magazine again. I’ve written for them off and on for years, but had never met the staff in person before.

Be sure to check out their Best Genetic Genealogy Websites and also their Genealogy Books Guide, listed by subject.

When you get there, check out their other “best of” categories and other topics.

Walking on down the aisle, I stopped to talk to the “One Kind Act a Day” people,

Being the skeptic that I am, I kept trying to find the hook, but I couldn’t. It’s a nonprofit that seems to do exactly what it says.

This is absolutely something I can sign up for, so I did and took the pledge.

Doing one kind act a day is easy, so let’s do two!

You can follow them on Facebook, too.

Reclaim the Records is another nonprofit that has successfully advocated and reclaimed more than 60 million records to date that were behind lock and key.

Take a look at their successes and their to-do list.

They style themselves as intellectual freedom fighters. Did you know so many records were still entirely unavailable?

Hey, isn’t that Myko Cleland sitting at the Reclaim booth, on the left? He’s the Director of Content in Europe for MyHeritage, nicknamed the DapperHistorian, and you just never know where you’re going to find him!

How cool is this? Wear What You Love uses sublimation dying to permanently print/infuse your photos on t-shirts or other materials.

This also works on fabric that can be used in quilts but more reliably on polyester fabrics, not cotton.

Hmmm, I have some ideas.

Y-DNA Ask Me Anything at FamilyTreeDNA

The Y-DNA “Ask Me Anything” session began at 10:30. I don’t think attendees realized that FamilyTreeDNA brought the R&D brain trust and you could literally ask them anything. What an opportunity!

Left to right, Michael Sager, FamilyTreeDNA’s well-known Y-DNA phylogeneticist, Dr. Paul Maier, seated, population geneticist, and Goran Runfeldt, standing at right, Head of R&D.

The team reviewed how to use Discover and what can be revealed.

Janine Cloud, Manager of Group Projects, is beside me in the black shirt, seated at far right. Group Projects are important tools for Y-DNA testing and testers.

In addition to the Discover Time Tree, shown on the screen above, a Group Time Tree shows Big Y project members as grouped by the volunteer administrators, along with their earliest known ancestors (EKA.)

Here’s an example from the Estes surname project that I administer. My grouping of participants is shown at left, the Time Tree in the center, and the locations with earliest known ancestors at right. Results are displayed in the order that they are phylogenetically related, helping genealogists immensely.

Here, the team is explaining the Block Tree which displays matches in a different format.

Men displayed together on the same Block Tree branch are more closely related to each other than to men displayed in other branches.

Michael Sager observes while Paul Maier demonstrates Globetrekker, an innovative interactive map that shows the path that one’s male ancestors took on their journey from Africa to where they are most recently found.

One of the attendees had a question and looks on as the team explains their results using Globetrekker.

We tried to get a team photo after the presentation and managed to corral some of the team. You’ve met several already, but Bennett Greenspan, Founder and President Emeritus of FamilyTreeDNA, is to my right as you look at the photo, with Sherman McRae standing between Bennett and Paul.

I particularly like this “generations” photo.

In the rear, Katherine Borges stands with Bennett Greenspan. Bennett obviously founded the company, and Katherine was one of the early administrators. Dr. Lior Rauchberger, CEO of myDNA, which includes FamilyTreeDNA, is seated at left, along with Alex Zawisza, CFO, at right. MyDNA purchased Gene by Gene, which includes FamilyTreeDNA, just over three years ago, and the team has continued to work together for the benefit of FamilyTreeDNA customers.

Lior traveled from Australia to attend RootsTech. He could be seen checking people out at the booth, so he had the opportunity to talk with customers. He said he heard the words “brick wall” more in those three days than ever before, as in, “Thanks to FamilyTreeDNA, I broke down my brick wall.”

We all owe Lior a huge debt of gratitude for his continued commitment to FamilyTreeDNA research, and in particular, the Big Y-700 tools, such as Discover, along with the Million Mito Project which will be released with a similar tool, MitoDiscover.

Thanks Lior!

I turned around to see Stephanie Gilbert, who gave the keynote at the FamilyTreeDNA conference.

Stephanie is an incredibly engaging speaker, and I’m going to recommend her to RootsTech for next year.

It was wonderful to see Schelly Talalay Dardashti, at left. She has worked for MyHeritage since 2006 and administers the Tracing the Tribe – Jewish Genealogy Facebook group, which has more than 73,000 members. Schelly is a wonderful ambassador, always helpful and incredibly knowledgeable.

Between us is Dana Stewart Leeds, creator of the Leeds Method, a technique that launched the autocluster craze by manually grouping matches. I wrote about the Leeds Method, here, in 2018. When you see AutoClusters at Genetic Affairs or the Collins-Leeds method at DNAGedcom, think of and thank Dana. They automated her process, with her permission, of course, creating some of the most useful tools available to genealogists. You can follow Dana here.

I swear, it was brainiac day at RootsTech!

Mags Gaulden, one of the founders of mitoYDNA and who writes at Grandma’s Genes, was working in the FamilyTreeDNA booth and was quite busy – so busy that I almost didn’t manage a picture with her. We never did get to have a meal together. We will have to do better in October when we are both scheduled to be at the East Coast Genetic Genealogy Conference in person. Oops, did I say that out loud???

Save the dates!

GEDmatch – New AutoCluster Endogamy Tool

I’ve emailed back and forth with Tom Osypian with GEDmatch many times now, but I’ve never met him in person, even though we’ve been in the same place before.

This time, I was determined. Although Tom was busy several times when I stopped by the booth, there were fewer people on Saturday, so I stood a fighting chance.

Tom explained that GEDmatch has a new AutoCluster tool developed by Evert-Jan Blom at Genetic Affairs and Jarret Ross from GeneaVlogger that helps with unraveling endogamy. I told him that I already knew because we used my Mom’s autosomal results during testing. Mom is partly endogamous through her grandfather’s Acadian line.

The Acadian cluster in the upper left quadrant looks like an orange blob with no differentiation, where everyone is related to everyone else – because that’s truly how Acadian descendants are connected. As my Acadian cousin once said, “If you’re related to one Acadian, you’re related to all Acadians,” and it’s true.

Evert-Jan needed to optimize clusters for a partially endogamous person without negatively affecting their non-endogamous clusters.

He did a great job separating my Mom’s big orange blob endogamous cluster into these nice, neat mini-clusters.

To take a look, choose AutoCluster Endogamy on GEDmatch and make your preset selection.

There’s a YouTube video about this tool by GeneaVlogger, here.

Next I ran into Patricia Coleman, a fellow genealogist scientist, who wrote an excellent article about finding segment links to the opposite parent using AutoSegment AutoClusters, here. Check out her blog and published papers, here.

We are incredibly fortunate to have such dedicated researchers and scientists in our community.

Unfortunately, I was running out of time on the show floor.

Sisters of Heart

OK, now, I’m going to say something really sappy. Consider yourself warned.

By this time, I needed to find food and quickly eat before my session, which was scheduled to start at 1:15. This meant I needed to be in the room by 12:45.

Janine was doing consultations in the FamilyTreeDNA booth and couldn’t get away for food either.

Thankfully, with the storm approaching, there weren’t long lines at the food vendors. I peeked outside as I walked down the hallway looking for a food booth that wasn’t very busy.

It was ominously dark and gloomy outside, and had begun to snow.

I found the food stand that looked least bad and got in line. Neither Janine nor I knew what was available at the food vendors, but we’ve known each other for enough years and attended enough conferences that we kind of know what the other likes.

I was standing in line taking pictures of the menu and the pre-made foods in the cooler and messaging them to Janine. People must have wondered if I couldn’t find something better to take pictures of. I just chuckled. I’ll spare you the food pictures because they were unremarkable,

They were out of everything Janine thought looked good. Apparently, everyone else thought those items looked good, too. When it was my turn to order, and I had to choose, I messaged Janine that we were sharing a turkey wrap and asked if she wanted fruit.

“YES! Fruit sounds wonderful.”

Great!

I got both items and paid.

“So do chips. Chips sound great, too.”

Perfect.

I paid again.

Then I saw the muffins. Chocolate sour cream swirl muffins with large shiny sugar crystals baked on top.

No need to message Janine about this one.

Yep, I paid for the third time.

Then, I apologized to the people behind me, hoped they didn’t recognize me, and hurried back to the FamilyTreeDNA booth.

Janine’s customer had just finished up, so I sat down in that seat and spread out our goodies on the table between us. The turkey wrap was cut in half, and we shared half of everything.

I love breaking bread and sharing food with my favorite people. There’s something about feeding the body that nourishes the soul and bonds the heart. I can’t explain it, and I really wasn’t thinking about it just then. Both of us just needed a minute to relax and eat before rushing off to do something else.

I asked Janine if she wanted the last part of my half of the turkey wrap. She told me to take the turkey out and eat it because I needed the protein.

Bless her heart. She was right.

I grabbed two forks in the food booth, and we both ate out of the fruit box positioned halfway between us.

Then, after discussing and laughing that the muffin looked like a geode, I cut it into four sections. We ate them on the cupcake paper with forks, like cake. It tasted wonderful. If you’re thinking that I couldn’t finish my turkey wrap, but had plenty of room for chocolate cake, you’d be exactly right!

Someplace in the midst of our impromptu picnic meal, I realized that four years ago at RootsTech 2020, was the last time we would see each other – for years. A week after RootsTech, everything shut down. People died. Both of us had family members who perished in the Covid epidemic.

Everyone was traumatized.

Neither of us knew if we’d ever see each other again, but neither of us verbalized that because – well – we just couldn’t. Some days during that time, it was all any of us could do to simply hold it together.

I realized just how important these very relaxed impromptu moments, built on years of shared space and breaking bread together, really are. It’s exactly why we don’t have any old photos of “normal” things, just special occasions. Normal isn’t special, until it is – when someone is suddenly gone. Then, “normal” is everything.

None of us know which meal together will be the last. We never know when our number will be called, or how. We really only ever have today.

I wish someone had taken a picture of us smiling and eating, sharing our meal with each other, something we’ve done countless times before. Something so normal that we don’t even think about it. I never thought about taking a picture of something so routine, and neither did anyone else. Why would they?

Regardless, that moment is burned into my memory, along with just how precious our time together is.

Then, the moment of quiet respite, eating chocolate muffins and sharing more than food, was over, and the fragile thought bubble was broken by the ticking of the clock. I had to jump up and run off to my next presentation, and a customer approached and asked Janine a question.

Thank Goodness we were both able to return to RootsTech and relish something so absolutely normal once again.

Highways of History – Flesh Out Your Ancestors Using Discover Case Studies

My class on Friday, “DNA Academy,” was full, and sadly, people were being turned away at the door. Saturday’s “Highways of History” class was held in a larger room, but many people stayed home, so the room was only about three-quarters full. I forgot to ask someone to take a picture, so I’ll just share a few slides.

I really enjoy using AI occasionally for images. This was ChatGPTs idea of Highways of History.

Using Big Y DNA results, I provided examples of using the Discover tools to reveal the stories of my ancestors. Not every Discover tool reveals something amazing about each ancestor, but together, they tell a story we can’t unravel any other way.

I seek out men who descend from every male ancestor paternally through all males and offer a scholarship for Big Y-700 testing.

Here are just a few examples of what I’ve found and documented:

  • A descendant of Etienne Hebert (c1626-c1670), my Acadian ancestor, matches an ancient DNA burial found in Metz, France. Etienne and his brother’s children cluster in a group with a common ancestor about 1650, and the ancient burial dates to about the year 500 CE during the time that Metz was a Gallo Celtic Village. Among other things, we learn that their common ancestors were Celtic.

  • An adopted male matches several Estes men. Based on his Big Y-700 mutations, I can place him in the Estes family tree within two generations. His position in the tree is confirmed by autosomal matches to the ancestors of the wife of Joseph Frank Estes. Autosomal matches confirmed the Big Y-700.

  • Germain Doucet, born in France in the late 1500s, had two sons. One was born in France about 1621, and the second in Acadia (now Nova Scotia) was born to either a second or third wife in 1641 and named after Germain. Based on Big Y-700 tests, the son born in 1621 has a European haplogroup, but Germain, born in 1641, has a Native American father, suggesting the possibility that he may have been adopted by the older Germain Doucet. This was quite an unexpected surprise.

  • A Bowling descendant of Hugh Bowling (1591-1651) born in Chorley, Lancashire, England, had almost no English matches. STR matches are from Saudi Arabia, Algeria, Cyprus, Germany, and Portugal, but the highest percentage are from Spain. Furthermore, his ancient Connections are from Hungary, Israel (4), Armenia, Rome, Italy, Turkey, Lebanon, Lincolnshire, and Norwich, England. Local history reveals a Roman Fort just 19 miles away from where Hugh Bowling lived, and the location, now excavated, was a settlement location for Roman Sarmatian soldiers.

  • Thomas Speak was born about 1634 in Downham, Lancashire, near Chorley, England where the family attended church. Big Y-700 testing shows that he and other English Speak men still living in the area share an ancestor about 1300 CE. When we visited in 2012, we discovered that Myles Standish’s family also attended the same church. Saxon Crosses are found in the graveyard outside, dating to circa 800-900 CE. A Standish male’s Big Y-700 test matches the Speak men, with their common ancestor dating to 850 CE, the same time that the Saxons were settling the region.

  • Bennett Greenspan’s Jewish ancestors were found in Ukraine in the mid-1700s, but he wanted to know more about where they came from originally. Were they Ashkenazi or Sephardic, or something else? By upgrading both close and distant matches to the Big Y-700, Bennett discovered that their common ancestors were in Spain in the year 296 when the two lines diverged and his line left. You can read Bennett’s story in more detail, here.

None of these mysteries or brick walls could have been solved without Big Y-700 tests and without the Discover tools.

This session was so much fun, and I can hardly wait to find more male ancestors and test their direct male-line descendants.

Goodbyes

By the time questions were answered, and I packed up my equipment, there were only about 15 minutes left until the Expo Hall closed at 3. Furthermore, I needed to retrieve my coat from the FamilyTreeDNA booth, retrieve my suitcase from the Marriott bellman, and order an Uber. My flight was only about two and a half hours away, assuming it left.

So far, it hadn’t been cancelled or delayed.

I mentioned my flight concerns to a colleague that I ran into on the way to the booth. He happens to live in Salt Lake City and gave me his phone number, with instructions to call if I got stranded.

My first (unspoken) thought was, “Thank you, but I’d never impose like that.” But then, I realized that was crazy and I really should call him if I needed help. What was wrong with me? I didn’t know him well, but I had known him and the company where he works for many years and felt completely safe. We are Facebook friends too, so I’ve joyfully watched him marry and start a family. I would have done exactly the same for him, and yes, I absolutely WOULD have wanted him to call. Plus, if I actually did wind up staying on his couch for a day or so, I would get time to “Grandma” his children, so HUGE BONUS!

You know who you are, and THANK YOU. I felt so much better after that. Genealogists are just the most amazing people!

Then, I ran into Lisa Rhea Baker who very generously gifted me with bracelets made by her veteran daughter as she healed from surgery. The bracelets around my wrist are beaded, and the one joining our hands is knotted in German colors. I’m wearing that one today. What a very talented and generous young lady.

I was very touched and so grateful. I asked her to thank her daughter on my behalf.

I saw Katherine Borges again in the booth as I was retrieving my coat and we quickly took a selfie. Neither of us realized we hadn’t gotten one earlier, although we did manage to have dinner with a small group where we all chattered like magpies.

Last, Goran, Paul and I took a quick selfie as I was preparing to run out the door. It was 3, closing time, and almost no one was left in the Expo Hall. I knew if I missed this flight, I’d not get another one. Everything was full.

I surely miss seeing these guys. Hopefully, I’ll see them again before the next RootsTech!

The Blizzard Strikes

I stepped outside.

The blizzard had begun in earnest. I could see a couple blocks down the street, but huge flakes of snow were pouring down. The wind was blowing viciously, whipping everything, making it difficult to hang onto my laptop rolling bag. The snow was sticking to everything.

At least it wasn’t slick yet, at least not where I was walking. If the wind hadn’t been so strong, it would have been pretty.

Would the plane be able to take off in this wind? The snow was blowing directly sideways now.

The only distance I had to walk was across the street. This is how much snow accumulated on my coat in just a minute or so.

A little later, Goran took this picture.

Ubers were becoming somewhat scarce, so two of us shared and made it to the airport in time for long TSA lines.

The plane was about 45 minutes late, which didn’t surprise me. I heaved a huge sigh of relief when it pulled up to the gate. At least it arrived, and as soon as it was cleaned a bit, we began to board.

Eventually, we pulled out of the gate and began waiting on the tarmac for the plane to be de-iced.

An hour later, we weren’t even halfway to the front of the line. The pilot estimated it would be another 90 minutes or so.

The snow continued to accumulate.

Would the pilot and crew time out and be unable to fly?

If we had to go back, there would be no prayer of getting another crew. Flights were already being canceled.

The woman beside me was ill. I felt awful for her, and it occurred to me that this might also be a reason to return to the gate.

At least the pilot allowed us to unbuckle our seatbelts and go to the restroom as we waited.

My flight had been scheduled to arrive just after midnight. But now, we were more than four hours late. What time would we get in? My poor husband. I told him to go to sleep and I’d just stay in the hotel in the airport. He said no, nothing doing.

I begged him to at least take a nap and recheck the flights at 3 or 4 AM.

The flight was extremely rough. We couldn’t get above or around the storm, and the seatbelt sign was only off for about 10 minutes during the entire flight.

I tried to sleep, but that wasn’t happening, even though I was beyond exhausted.

This is what love looks like. One single car in the cell lot at around 5 AM, as Jim waited patiently for me.

On the way home, in fact, all of the way home, we drove through the most incredible lightning storm I’ve ever seen.

It was someplace between worrisome/terrifying, and fascinating.

This lightning wasn’t reaching toward the earth in bolts. Instead, the entire sky lit up like daylight, horizon to horizon, flashing like an extremely bright strobe. It was so bright that, at times, it was nearly blinding, and the clouds looked like rainbows as the lightning flashed behind and through them. I had never seen anything like this.

This type of “sheet lightning” is crazy rare. Thankfully, it kept us awake and was stunningly beautiful in a very strange, ethereal way. We worried that we would be caught in a hellacious storm and unable to see in the downpour.

Florida is notorious for vicious storms and torrential downpours. It’s also the lightning strike capital of the US and ranks fourth in the world. This area, in particular, is known as Lightning Alley. Our house was struck last year.

As we exited the expressway, just a couple miles from home, the sky unzipped, and torrential rains began. Thankfully, we were spared for most of the drive.

I was incredibly glad to finally be home and hoped that others had been able to either escape the Utah storm or find a room in a hotel that did not lose power on Sunday. Reports said wind gusts in the Utah mountains were measured at 165 miles an hour, but Salt Lake City, tucked into a valley, was spared most of that.

What an incredible week in so very many ways.

I hope you enjoyed coming along with me. Dates have already been announced for RootsTech 2025.

_____________________________________________________________

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

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

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

Reminder – Free Discover Webinar Through September 5th

Wow – has this ever been a week!!! This article should be subtitled, “Never Argue With a Woman Named Idalia.” Trust me, Idalia will be the least popular baby name for 2023.

But first things first.

I want to provide a friendly reminder that the webinar, Y-DNA Discover Tool – What News Can Your Haplogroup Reveal? is free through September 5th at Legacy Family Tree Webinars and will be available in their library for subscribers thereafter.

Discover is a free Y-DNA tool provided by FamilyTreeDNA.

Anyone can use Discover. You don’t need to have taken a Y-DNA test, but the greatest benefit will be realized with Big Y-700 test results. Don’t worry about that now, though, because I explain the differences between tests in the webinar. You can get a lot out of Discover, even if you only know a base-level haplogroup.

Normally, these webinars are live, but those plans were interrupted by Hurricane Idalia.

Idalia developed so quickly – and we really weren’t sure where it was going until just a day or so in advance – or how severe it would be. It was ugly, and as I write this, Idalia is still torturing the east coast.

When I realized the possible impact, and that the probability of having both power and internet were very remote, I contacted Legacy Family Tree Webinars and discussed options.

We really didn’t want to reschedule since more than 2000 people from around the world had signed up for the webinar. We decided that the best option was to record the webinar in advance as a precaution. Then, if possible and Idalia targeted her wrath elsewhere, I would still give it live.

Needless to say, doing anything live wasn’t in the cards on Wednesday. I should add that I am safe and dry with minimal damage – just some branches and small trees down – but others nearby aren’t nearly so fortunate. Flooding was recorded in feet of water, roads are still closed to vehicles, boats rescuing people who didn’t evacuate are zipping down the flooded streets in many places, and there’s just a massive mess. Thousands of people are displaced.

However, as they say, “the show must go on,” and it did. The webinar was presented even though I couldn’t be there for Q&A. Anticipating that possibility, I recorded a lot of detail for you.

I hope I didn’t sound as rattled as I felt, because I was recording in the midst of hurricane prep and the first bands of wind and rain were already lashing the windows. I knew that we were facing a monster storm. That’s very unsettling.. All things considered, I think the webinar went quite well. I was afraid the power would go out while we were recording, but fortunately, it didn’t.

At the end of the webinar, I pulled everything from all of the Discover tools, the Block Tree, and the Group Time Tree together, then added historical migration records along with known, proven family genealogy.

Given that:

  • How did Discover do?
  • Was it useful?
  • Is it accurate?
  • How accurate?
  • What has it done for the Estes paternal line genealogy?
  • What do I know about my Estes lineage that I didn’t know before?
  • What’s the next step?
  • What can Discover do for you?

I really encourage you to tune in and take advantage of this free educational webinar through September 5th, maybe even over the Labor Day weekend.

Please feel free to share this article and information about the webinar with interested groups and organizations!!!

_____________________________________________________________

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

Y-DNA Discover Tool – Free Webinar

You’re invited to join me for a free, live webinar about the Y-DNA Discover tool on Wednesday, August 30th, at 2 PM EDT, courtesy of Legacy Family Tree Webinars.

FamilyTreeDNA‘s Discover tool can be used with any Y-DNA haplogroup. I’ve written about Discover here and the newest feature, Globetrekker, here

Y-DNA Discover Tool – What News Can Your Haplogroup Reveal? will be free next Wednesday and for the following seven days. After that, this webinar, along with the rest of Legacy Family Tree’s extensive webinar library is available via an annual subscription of $49.95. I think my new webinar will be webinar number 2042 in their library.

A subscription also provides access to the webinar handouts, the webinar chat logs, and a subscribers-only door prize during each webinar. If you’re interested, you can subscribe here.

What’s In the Discover Webinar?

Discover is an amazing tool, but I think many people are missing ways to use it for genealogy. I’ll cover both the free Discover version and the additional functionality for Big Y testers.

Everyone can use Discover for any Y-DNA haplogroup, no matter the haplogroup source. Of course, the more granular or refined the haplogroup, the more relevant the haplogroup will be to your most recent ancestors. Y-DNA haplogroups are available through the following types of tests:

  • Autosomal at 23andMe, LivingDNA – base or midrange level haplogroup derived from target testing a few Y-DNA locations in an autosomal test. These haplogroups are generally at least a few thousand years old. Think tree branches.
  • Haplogroup estimate when taking the 12, 25, 37, 67, or 111 STR marker Y-DNA tests at FamilyTreeDNA. Think tree branches.
  • The Big-Y DNA test, also at FamilyTreeDNA, provides the most refined and detailed haplogroup. Think twigs and leaves that are very specific to your family at the ends of each larger branch.

After briefly introducing Y-DNA, how it works, and why you care, I’ll be stepping through each Discover feature and function. This includes the Group Time Tree, which isn’t part of Discover but is available through FamilyTreeDNA‘s projects and uses the Discover technology.

  • Haplogroup story – description and overview
  • Country Frequency – where this haplogroup and related haplogroups are found in the world
  • Notable Connections – the famous and infamous, and what that means to you
  • Migration Map –  short story, complete with ancient DNA sites
  • Globetrekker – animated, refined story with lots of detail and several options. Paths your ancestors may have taken to arrive where your line is first found.
  • Ancient Connections – ancient Y-DNA that anchors haplogroups
  • Time Tree – when and where haplogroups were born and how they connect
  • Ancestral Path – every step from you to Y-Adam, when and where that step occurred
  • Suggested Projects – relevant projects for collaboration (and buried hints)
  • Scientific Details –  haplogroup age estimates, age ranges, and your haplogroup’s mutations
  • Group Time Tree – for project members only – the Time Tree complete with all Big-Y testers who’ve opted-in to this project and provided a location, plus earliest known ancestors, displayed in groups
  • What you can do to help yourself

I’ll discuss using the various Discover features to understand what the information means to you, why it’s important, and how to utilize it for your genealogy. I’ll also talk about how to incorporate Block Tree information and projects.

If you’d like to listen and educate yourself, that’s great, but you might want to take this opportunity to think of a male-line brick wall you’d like to work on or learn more about. Don’t we all want to know more about every line – even if we’ve run out of known ancestors and records? Keep your focus line in mind as we apply the tools one-by-one to my Estes lineage, building evidence, during the webinar. Discover helps us peel back the veil of time.

At the end, I’ll provide hints and tips about constructing your plan of attack – how to locate testers and what to do next.

Mark your calendar, and don’t forget to convert the time to where you live. Next Wednesday, August 30, at 2 EDT. See you then!!

_____________________________________________________________

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

WikiTree Connections, King Charles III, and DNA

By Copyright House of Lords 2022 / Photography by Annabel Moeller, CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=117865820

I’m not a royal-watcher, but you’d pretty much have to be dead to not be aware that King Charles III is being crowned this Saturday, May 6th.

Have you wondered if you’re related to Charles? Or someone else?

It’s easy to find out on WikiTree.

Go to King Charles’s profile, here.

Notice that under “DNA Connections,” a WikiTree user has entered the Y-DNA of the line of King Charles via an academic sample uploaded to mitoYDNA. That’s interesting!

Tsar Romanov and King Charles III both descend from a common ancestor and are first cousins twice removed (1C2R.) You can also see more about Nicholas Romanov II in the FamilyTreeDNA Discover tool under haplogroup R-M269, in Notable Connections.

Under WikiTree DNA Connections, I notice no one has entered King Charles’s mitochondrial DNA information. Of course, King Charles inherited his mtDNA from his mother, Queen Elizabeth II.

If you know of anyone who carries Queen Elizabeth’s mitochondrial DNA through her direct matrilineal ancestors, by all means, enter this information. If you don’t know how, you can click on help at the bottom of the page or click here. WikiTree has lots of truly helpful volunteers.

You can also enter your information if you’ve taken an autosomal, Y-DNA, or mitochondrial DNA test and are descended appropriately from the person represented in the profile.

Here’s an example from my ancestor, Phebe Cole’s profile. I entered where I tested, and my GEDmatch number.

You can add your DNA test information by clicking on the “Add” button in the top header, then DNA Test Information here.

WikiTree DNA Benefits

WikiTree is a wonderful place to:

  • Upload your DNA to the relevant profile, where it will be populated up the tree appropriately
  • Obtain DNA information, including haplogroups, about your ancestors
  • Discover cousins who descend from that ancestor and who have tested their DNA
  • Discover cousins who may not have tested yet, but might be willing

I use WikiTree regularly to fish for Y and mitochondrial DNA information about my ancestors and to see if I match cousins listed as descendants of a common ancestor.

WikiTree works in the opposite direction from the DNA testing vendors.

At the testing vendors, you find the match and then need to determine how they are related. At WikiTree, you check your ancestor and will find a list of cousins who descend from that ancestor and who have DNA tested. You already know at least one way that each person is related to you. Finding cousin matches by ancestor is part of my triangulation process.

Are You Related?

No known DNA testers or don’t match – no problem.

You can determine whether or not you’re genealogically related to any individual on Wikitree.

Just sign in to your account, and select the profile of the person you want to check.

Scroll very near the bottom or do a browser search for the words “your connection.”

Just click on “Your connection” or “Your genealogical relationship.”

Collaborate is Key

WikiTree is crowd-sourced, so be sure to verify your connection pathway results. If the path isn’t accurate, you can correct the inaccurate person or connection. We are all doing the genealogy community a HUGE favor by ensuring this collaborative tree is accurate.

If you’re unsure about a connection, check the sources and evidence for each generation. If you need information, contact the profile manager.

Add a comment, ask a question, add an image, or provide additional information and sources on any profile.

Ancestral Legacy

I regularly update my ancestors’ profiles with additional information when it becomes available. I appreciate everything others have shared with me over the years, and I want to be sure the information about my ancestors is as accurate as possible.

I don’t know about you, but I’m in this for the long game – for posterity. Leaving as much accurate information, including Y and mitochondrial DNA, is the very least I can do for my ancestors. After all, we wouldn’t be here without them.

So, are you related to King Charles? Is your distant cousin being crowned on Saturday?

_____________________________________________________________

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

So, You Want to Become a Professional Genetic Genealogist

I get asked quite often about what is required to become a professional genetic genealogist.

That’s actually two separate questions.

  • What is required to become a professional genealogist?
  • Then, what is required to specialize as a genetic genealogist?

What It’s Not

Before we have this discussion, I need to make sure that you understand that I’m NOT talking about forensics, meaning IGG, or investigative genetic genealogy in this article.

  • This is NOT forensics (IGG)
  • This is also not a specialty in finding missing parents for adoptees and others searching for unknown parents.

Both IGG and adoption searches utilize the same methodology, a subset of genetic genealogy. I wrote about that in Identifying Unknown Parents and Individuals Using DNA Matching.

The difference between genetic genealogy more broadly and IGG is:

  • What you’re searching for
  • The perspective
  • The methods utilized.

Essentially, the functional difference is that genealogists know who they are and have some information about their ancestors. For example, they know who their parents are and probably at least their grandparents. Genealogists are using both DNA testing and traditional genealogical paper trail research methods to focus and make discoveries going backwards in time.

Both IGG and unknown parent research uses DNA and (sometimes some) paper trail genealogy to find ways to connect the closest matches to the DNA tester (or DNA sample) together to each other to identify either living or recently living people. For example, two people who are are first cousins to the tester should both have the same grandparents if they are related to the tester through the same parent.

If two people who are related to the tester as first cousins do not share the same grandparent(s), then they are related to the tester through different parents of the tester.

The commonality is that DNA testing and some types of records are used for:

  • IGG where you’re searching for the identity of the tester or DNA sample
  • Unknown parent(s) searches where you are searching for the identity of the parent(s)
  • Genetic genealogy

However, the search methodology is different for IGG and unknown parents than for genealogy.

With IGG and unknown parent searches, you’re looking for your closest matches, then attempting to connect them together to identify either currently living or recently living people.

This article focuses specifically on genealogy and genetic genealogy, meaning looking backwards in time to identify ancestors.

I wrote about the techniques used for both IGG and parental searching in the article, Identifying Unknown Parents and Individuals Using DNA Matching.

What Do Genealogists Do?

Genealogy is the study of family history and the descent of a person or a family. Genealogists use a variety of sources and methods to discover and show the ancestry of their subjects and in doing so, create the family trees that are familiar to all of us.

Genealogists use different sources and methods to find and show the descent and kinship of their subjects.

Traditional sources include but are not limited to the following record types:

  • Vital records (birth, marriage, and death certificates)
  • Census
  • Military
  • Immigration
  • Land and tax records
  • Wills and probate
  • Church records
  • Newspapers
  • Obituaries
  • Published and online books
  • Oral histories
  • Genealogy databases
  • And more

Of course, today the four types of DNA can be added to that list.

A professional genealogist needs to know how and where to find these types of records in the target area, any unique cultural or regional factors affecting those records, and how to interpret them both individually and together.

For example, in a deed record in colonial Virginia, why would, or wouldn’t a female release her dower right? What is dower right, and why is it important? How might that record, or lack thereof, affect future probate for that woman/couple? In what type of historical or court record book might one look for these types of records?

Genealogists also need to know how to weigh different types of information in terms of potential accuracy and how to interpret primary and secondary sources.

Primary sources are those that were created at or near the time of an event by someone who was present at the event or who had first-hand knowledge of it. Examples of primary sources include birth certificates, marriage licenses, and census records, although census records are far more likely to be inaccurate or incomplete than a birth certificate or marriage record. Genealogists need to understand why, and where to look for corroboration. Primary sources are considered to be most accurate.

Secondary sources are those that were created later by someone who did not have first-hand knowledge of the event. Examples of secondary sources include family histories and genealogies, published biographies, and sometimes, newspaper articles.

The genealogists “go to” source for understanding and interpreting evidence is Evidence Explained by Elizabeth Shown Mills, available here.

Of course, DNA understanding and analysis needs to be added to this list and has become an important resource in genealogy. Additionally, genetic genealogy has become a specialty within the broader field of genealogy, as has IGG.

Put another way, a genealogist should have expertise and a specialty in some area. Maybe Italian records, or Native American genealogy, or New England records, in addition to the basic skills. At one time, a genealogist didn’t necessarily HAVE TO have expertise in genetic genealogy as well, but that has changed in the past few years. A professional genealogist should MINIMALLY understand the basics of genetic genealogy and when/how it can be useful. They may or may not have ready access to a genetic genealogist within the company where they work.

Being an independent genealogist, unless you specialize only in a specific area, like Dutch genealogy, is much more challenging because you’ll need to be proficient in BOTH Dutch genealogy AND genetic genealogy. It’s tough keeping up with one specialty, let alone two, although in this case, Yvette does an amazing job. However, her primary specialty is Dutch genealogy, and genetic genealogy is the booster rocket when appropriate. Genetic genealogy is not always needed for traditional genealogy, which is why genetic genealogy is a specialty skill.

In addition to all that, you also need to be proficient and comfortable with technology and a good communicator. Walking on water is also helpful:)

Job Description

So, what does the job description for a genealogist look like?

I reached out to Legacy Tree Genealogists because they are one of the largest, if not the largest genealogy research company, and they partner with 23andMe, FamilyTreeDNA, and MyHeritage. Legacy Tree has specialists in many regions and languages, in addition to six genetic genealogists on staff.

Fortunately, they have a job listing posted right now, here, with an excellent description of what is expected.

If you’re interested or wish to sign up for notifications, click here.

Understanding that this job description won’t be posted forever, I reached out to the owner, Jessica Dalley Taylor, and asked if she would send me a sample description to include in this article.

Here you go, courtesy of Jessica:

About You

It’s not easy to make each client’s experience the very best it can possibly be, and it means we can only hire an exceptional genealogist for this position. You will be a great fit if:

    • You are fluent in English and can explain your genealogy discoveries in a way that clients connect with and understand
    • You have taken at least one genetic genealogy test or administered the test of a relative
    • You have introductory genetic genealogy abilities
    • You have at least intermediate traditional genealogical research experience in any geographic locality
    • You are familiar with the repositories of the areas for which you claim expertise and have worked with them to obtain documents
    • You are passionate about genealogy and are a creative problem solver
    • You are great at working independently and hitting deadlines (please don’t overlook this line about deadlines)
    • You are comfortable with Microsoft Office suite
    • You’re familiar with genealogical technology such as pedigree software
    • You have a quiet place to work without distractions, a computer, and great internet
    • You have a strong desire to work as a professional genetic genealogist

Even better if:

    • You have a basic understanding of genetic inheritance and its application to genealogy
    • You have beginning experience with interpretation and use of genetic genealogy test results
    • You have intermediate-level genetic genealogy abilities

What you’ll be doing at Legacy Tree:

    • You’ll be learning how to use genetic testing in identifying family
    • You’ll be learning how to create high-quality research reports
    • You’ll be reading and formatting reports by professional researchers
    • You’ll be assisting with researching and writing genealogy reports
    • You’ll be performing genetic genealogy analysis under the direction of professional mentors
    • You’ll be developing advanced-level genetic genealogy skills and abilities
    • With your input, you’ll do other things as opportunities and needs arise

Please note that Legacy Tree offers both traditional genealogy services, combined with genetic genealogy, along with adoption and unknown parent searches.

As a measure of fundamental basic genetic genealogy skills, you should be able to create and teach a class like First Steps When Your DNA Results Are Ready – Sticking Your Toe in the Genealogy Water.

You should also be able to read and fully comprehend the articles on this blog, as well as explain the content to others. A very wise person once told me that if you can’t explain or teach a topic, you don’t understand it.

As luck would have it, Ancestry also posted a job opening for a genealogist as I was finishing this article. Here’s part of the job requirements.

Contractor or Employee

Please note that many companies have shifted their primary hiring strategy to utilizing contractors for not more than half time, especially now that working remotely has become the norm.

This may or may not be good news for you.

It allows the company to avoid paying benefits like insurance, vacation, leave, and retirement programs which reduces their costs. You may not need these benefits, and it may represent an opportunity for you. For others who need those benefits, it’s a deal-breaker.

Contracting may provide the ability to work part-time, but contracting probably means you need to have business management skills not required when you work for someone else. Let’s just say that I make quarterly estimated tax payments and my annual CPA bill is in the $2,000 range.

Compensation

Pay, either as an employee or contractor for a company, is a sticky wicket in this field.

First, there’s a consumer mindset, although not universal, that genealogy “should be” free. In part, this is due to search angels and a history of well-intentioned people making things free. I’m one of them – guilty as charged – this blog is free. My hourly work, however, when I accepted clients (which I DO NOT now,) was not free.

However, that “should be free” mindset makes it difficult to shift to a “pay to play” mentality when people can go on social media and get what they want for free.

Professional services are not and should not be free.

Professionals should be able to earn a respectable living. The full-time Ancestry job, posted above, with those credentials, nets out to $21.63 per hour for a 40-hour week, with a graduate degree preferred. For comparison, google other jobs and professions.

If you doubt for one second whether professional services should or should not be free, especially ones that require a bachelor’s degree or master’s, just think about what your CPA would do if you asked them to do your taxes because they have the ability, for free. Same for a doctor, lawyer, or any other professional.

People are often shocked at the rates paid to employees versus the rates charged to prospective customers. This discussion has recently gotten spicy on social media, so I’m not going to comment other than to say that when I did take private clients, which I DO NOT ANYMORE, I found it much more beneficial to operate independently than to work for a company.

However, I also had a readily recognizable specialty and an avenue to reach potential clients.

I also already had a business structure set up, and a CPA, and perhaps more important than either of those – I had medical insurance already in place.

The need for benefits is what drives many people to work for companies, which I fully understand. It’s also a big factor in why there are more female genealogists than male genealogists. Married women in the US are eligible to be covered by their spouse’s insurance, assuming the spouse has insurance through their employer.

My very strong recommendation to you is to weigh all of the factors and NEVER to find yourself without medical insurance or coverage.

If you’re going to be “self-employed,” set up a company. If you’re going to set up a company, do it properly, understand the tax ramifications of the various types of corporations and engage a competent CPA to shepherd you through the process from day 1 through taxes. They are worth every penny.

Look at various jobs in the market, review at the associated pay, get a quote for genealogy services of the type you would be providing from the various companies – and decide if this profession is really for you.

I don’t mean to be a wet blanket, just a realist.

Training and Certification

Now for the good news and the bad news.

  • There is professional training for genealogy
  • There are certifications for genealogy
  • There is no “one place” for either
  • There is no certification for genetic genealogy
  • There’s a LOT of misunderstanding and misinformation about genetic genealogy
  • Genetic genealogy changes often

You need to view your education for genealogy/genetic genealogy in the same way you’d view obtaining a college degree – plus continuing education to maintain your education and skills at a current and functional level.

And yes, all of that costs money. If you decide to work for a company, be sure to ask if continuing ed is on their dime and time, or yours.

Genealogy Training

The Board for Certification of Genealogists, BCG, allows graduates to append CG, for Certified Genealogist after their name. BCG is focused on certification of skills and is not a training platform, although they do provide some webinars, etc. It’s not a college curriculum though. Certification is the “end game” for many. Candidates must submit a portfolio for evaluation, complete in a specific timeframe, and must reapply every five years to maintain their certification.

Not all genealogists are certified by BCG, and BCG only lists references of BCG members.

In the field of Genetic Genealogy, that can be problematic because many competent and well-known people are not BCG certified. BCG does not have a genetic genealogy certification.

Lack of BCG certification does not mean that someone is not qualified, and BCG certification certainly does NOT mean or imply that the individual is competent in genetic genealogy, which has more and more become a part of almost every genealogical puzzle. If not for initial discovery, for confirmation.

There are many avenues for genealogical training, including, but not limited to:

  • Brigham Young University Family History Degree
  • NGS Home Study Course
  • Salt Lake Institute of Genealogy (SLIG)
  • Genealogical Research Institute of Pittsburgh (GRIP)
  • Boston University Certificate program
  • Genealogical Institute on Federal Records (Gen-Fed)
  • Institute of Genealogy and Historical Research (IGHR)
  • University of Strathclyde
  • University of Dundee
  • Major Conferences, including RootsTech and NGS, among others
  • Specialty conferences such as the International Conference on Jewish Genealogy (IAJGS)
  • Online conferences and conference proceedings such as Rootstech who maintains a free library of their virtual and recorded conference sessions.
  • Legacy Family Tree Webinars
  • Videos produced by major genealogy companies such as MyHeritage, FamilyTreeDNA and Ancestry, often available through their website, Youtube or both
  • Blogs and learning/help centers of the major genealogy companies

Genetic Genealogy Training

Genetic genealogy training is more challenging because there is no specific program, curriculum, or certification.

Many genetic genealogists obtained their experience as a part of genealogy over 15 or 20 years and have focused on the genetic aspect of genealogy. Several of us had a scientific background that meshed well with this field and is part of why we discovered that our passion is here.

Before I provide this resource list, I need to emphatically state that probably 95% of answers that I see provided on social media platforms in response to questions asked by people are either entirely incorrect, partially incorrect in a way that makes me want to say, “well, not exactly,” or are incomplete in a way that makes a significant difference.

I chose and choose to focus on creating educational tools and making explanations available for everyone, in one place, not one question at a time.

I began publishing my blog in 2012 as an educational tool and I’m dumbstruck by how many people just want a yes or no answer instead of learning. If one doesn’t take the time to learn, they have no idea if the answers they receive are valid, or if there’s more to the story that they are missing.

Social media can mislead you badly if you don’t have the ability to discern between accurate answers, partially accurate answers, and incorrect answers. Furthermore, opinions differ widely on some topics.

Unfortunately, because there is no genetic genealogy credentialling, there is also no “post-nominal letters,” such as CG for certified genealogist. Therefore, a novice has absolutely no idea how to discern between an expert and another overly helpful novice who is unintentionally providing incorrect or partial information.

Many of us who at one time reliably answered questions have simply gotten burned out at the same question being asked over and over, and no longer regularly engage. Burnout is real. Another issue is that askers often don’t provide enough, or accurate, information, so a significant amount of time is spent in clarifying the information around a question. Furthermore, your CPA, lawyer, and physician don’t answer questions online for free, and neither do most people who are busy earning a living in this field.

DNA educational opportunities, some of which are contained within larger conference agendas, include:

There are other blogs, of course, some of which were launched by well-known genetic genealogists but are no longer maintained. Blogging is quite time-consuming.

I’ve covered all kinds of genetic genealogy topics in my blog articles. They are a good source of information, education and hands-on training. I attempt to publish two articles weekly, and there are over 1600 available for your enjoyment.

In addition to the initial learning period, you’ll need to make time to stay engaged and maintain your genealogy and genetic genealogy skills.

Apprenticeship

In addition to training, I think you’d need at least a year interning or working at a junior learning level, minimum. Think of it as your genealogy residency.

  • You could choose to work for a vendor in their help center.
  • You could choose to work for a genealogy company. I’ve mentioned the largest ones, but there are others as well.
  • You could choose to work on your own case studies and those of your friends and family, but if you do, be aware that you won’t have anyone reviewing your work. If you make a mistake or should have approached something differently, and you’re working alone, there’s no one to tell you.
  • You could work as a search angel for others. I have mixed emotions about this, in part due to the lack of review and oversight. But also, in part because “free search angels” perpetuate the idea that genealogy “should be” free.

If you want to work in IGG, after training, an internship under an established mentor is ABSOLUTELY ESSENTIAL for a minimum of 100 or so successful closures.

Genealogists and genetic genealogists have the ethical responsibility to NOT MAKE MISTAKES when working on other people’s family. You need to know what you know, what you don’t know, when to get help, from where and with whom.

Networking Opportunity

A Facebook group named “Genealogy Jobs” has been established to discuss opportunities and all of the topics surrounding this subject.

There’s a Genealogy Career Day event on April 22nd where you can interact with professionals including authors, freelance genealogists, certified genealogists, business owners, and an investigative genetic genealogist. Take a look at the topics. If you’re considering whether or not you want to go pro, you’ll be interested. You can sign up here.

The sessions will be uploaded to their YouTube channel, here, after the event.

I hope you’ve found this article useful and helps you decide if this profession is for you. If so, create a plan and execute.

If you decide you do want to go pro, I wish you the best and welcome you to the fast-paced world of professional genealogy or its specialty, genetic genealogy.

____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, 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

cM Explainer™ – New MyHeritage Relationship Prediction Tool

At RootsTech, MyHeritage introduced cM Explainer, a new tool for all of their DNA customers that utilizes both the total matching cMs (centimorgans) plus the ages of the people involved, if provided by the customers, to estimate the relationship possibilities between two matches.

According to the MyHeritage blog article, here:

DNA Matches are characterized by the amount of DNA shared between two individuals, measured using a unit of genetic distance called centimorgans (cM). cM Explainer™ is unique in the way it uses both the centimorgan value as well as the ages of the two individuals (if known) to fine-tune its predictions, making MyHeritage the only major genealogy company to offer relationship prediction at this level of granularity and accuracy.

cM Explainer™ is fully integrated into the MyHeritage platform to shed light on any DNA Match found on MyHeritage, and is also available as a free standalone tool to benefit individuals who have tested with other DNA services.

Using cM Explainer

cM Explainer is automatically implemented for all MyHeritage DNA customers, so there’s nothing to do except utilize the tool in conjunction with the additional DNA tools already provided by MyHeritage.

Just click on DNA Matches if you’re a DNA customer, or under DNA Tools if you want to use the cM Explainer standalone tool.

Let’s look at my matches.

As you can see, two of my matches have provided their ages which appear in their match information.

The new cM Explainer probable relationship is listed as well. In Charlene’s case, she’s predicted to be a half first cousin, and Cheryl is predicted to be either a half first cousin, or a parent’s 1st cousin, which is another way of saying first cousin once removed.

Recall that “once removed” means one side of the descendant tree is one generation longer than the other. Cheryl and my Mom are first cousins (1C) and Cheryl and I are first cousins once removed (1C1R) or, said another way, I’m Cheryl’s first cousin’s daughter.

Probable Relationships

Some matches receive two listed “Probable Relationships,” but everyone can view additional estimates.

Click on the purple “Review DNA Match” button to view detail information.

My match’s segment information is provided, in addition to the possible relationships, in order of most probable first. To see additional information, click on the “show more relationships” link.

Charlene has a total of 5 possible relationships listed, each with its own probability calculated. One of my matches has a total of 8 possible relationships displayed.

Next, you’ll see the diagram of possible relationships.

Don’t forget to click on the “Relationships” dropdown in the upper right corner of the diagram.

You can click on Full relationships, Half relationships, or All Relationships.

I clicked on “all” which displays everything together.

Clicking the “Show probabilities for MRCA” box in the upper left-hand corner adds the probability that you and your match descend from a specific generation, or MRCA (most recent common ancestor.)

The highest or best probable relationship for cousin Charlene is calculated as 51.8% half first cousin.

The other possibilities are less likely. The second most likely is “Parent’s first cousin,” at 24.3%.

Charlene is my first cousin once removed (1C1R,) at the bottom. Stated another way, Charlene is my first cousin’s child, calculated at 4.5%, which should be genetically equivalent to a half first cousin at 51.8%. As you can see in the chart above, there’s VERY large probability difference between those two, which may be because of the expected comparative ages of the people in those positions involved.

Let’s take a minute to look at how half and “removed” relationships work genetically.

Half and “Removed” Relationships

In this example, John was married twice, to Mary and Sue. John had son Jim with Mary, and both daughters, Anna and Bonnie, with Sue. Their descendants took DNA tests.

In this chart, you can see that half-relationships of any kind carry half the average expected shared DNA as the full version of the same relationship. The yellow people, descendants of John and Mary, are half relationships to the green people because John was married to both Mary and Sue, having children with both wives.

The green people descend from full siblings, Anna and Bonnie, the children of Sue.

In the first generation, Jim and Anna are half siblings and share about 25% of their DNA. Anna and Bonnie are full siblings and share about 50% of their DNA. By extension, of course, Jim and Bonnie are half siblings too, sharing approximately 25% of their DNA, but not the exact same DNA as Jim and Anna share.

In the next generation, Jordan and Andrew are half first cousins and share about 6.25% of their DNA, while Andrew and Brad are full first cousins and share about 12.5% of their DNA.

Below the second cousin level, some cousins won’t match each other, but that doesn’t mean they aren’t cousins. It only means they didn’t happen to inherit a common segment of DNA from their common ancestors.

At the fourth-generation level, Jeremy and Abraham are half third cousins and share less than 1% or about 26.56 cM of their DNA, while Abraham and Betty are full third cousins and share about 53.13 cM of their DNA.

That half division of DNA occurred several generations earlier because Jim and Anna are half siblings which means that they only share half as much DNA as full siblings Anna and Bonnie. Of course, each subsequent generation will be a half relationship, and share roughly half as much as the full equivalent of that same relationship.

Once Removed

However, when the generations are offset by one, or once removed (1R,) the DNA is halved again. Looking at the chart again, half third cousins (3C,) Jeremy and Abraham share about 0.39% or about 25.56 cM of their DNA. Abraham and Beverly, who are 3C1R (third cousins once removed) are ALSO expected to share about 25.56 cM, the same amount of their DNA. In this comparison, the halving occurs in the last generation by the generational offset, when comparing Abraham with Beverly.

Of course, Jeremy and Beverly share the smallest percentage of all, because they are Half third cousins once removed, so they would be expected to share only about 13.28 cM of their DNA, assuming they share any at all.

I wrote about the various percentages expected of each relationship level and compiled a comprehensive chart in this article.

Of course, MyHeritage has included the factor of age to attempt to refine the relationship more succinctly.

How Accurate is cM Explainer?

I created a chart of my closest matches who are known, proven relatives.

Results where My Heritage has provided exact, accurate predictions are shown in red.

My first thought when I saw this new tool was that all of the people with whom I shared a Theory of Family Relativity (TOFR), especially relationships I had confirmed (or at least not rejected) would be predicted in cM Explainer to be that same relationship. Well, I was wrong.

Of the 8 matches with whom I have an accurate TOFR, the relationships of 4, or 50%, are correct, but the other 4 are not, so clearly, MyHeritage is not relying on TOFRs for cM Explainer, at least not solely, if at all.

Person Total cM # Segments Actual Relationship TOFR MyHeritage cM Explainer
Michael 822.8 31 1C Y 1C
Alberta 744.2 25 Half niece *1 (2nd on list) Y 1C
Dana 521.8 17 Half 1C1R (not on list) N 1st C dau, half 1C
Charlene 477.5 24 1C1R *2 (4th on list) N Half 1C
Cheryl 477.2 23 Parent’s 1C (2nd on list) N Half 1C, parent’s 1C
David 460.4 17 2C (3rd on list) N Half 1C
Buster 409.9 16 1C1R *3 N Parent’s 1C
Donald 381.7 17 1C1R (3rd on list) N 2C
Kurt 378.9 16 Half great-nephew (not on list) N 2C
Teresa 330.4 13 Half great-nephew (not on list) Y 2C
Shirley 223.3 8 2C1R (2nd on list) Y 2C
Sydney 217.8 10 Half great-nephew (not on list) N 2C dau, 1C dau
Buzz 212.7 9 2C Y 2C
Amos 182.7 8 1C2R (8th on list) N 2C son
Denny 166.9 6 3C (2nd on list) N 2C
Thomas 156.4 7 2C Y 2C
Patty 150.6 9 2C Y 2C
Cathy 102.9 5 3C Y 3C
Carol 87 7 2C1R (2nd on list) N 3C

*1 – Half aunt/uncle is equivalent to half niece/nephew – it’s simply a matter of perspective.

*2 – 1C1R (first cousin once removed) is the same relationship as a first cousin’s child, just said differently.

*3 – Your parent’s first cousin in your first cousin once removed (1C1R.)

In the Actual Relationship column, I’ve indicated the actual relationship, then if the actual relationship is shown on the chart of possibilities provided by MyHeritage, and if so, at which position.

For example, I’ve listed Alberta’s “Actual Relationship” as my half-niece. Additionally, there’s a comment at *1 below the chart. MyHeritage predicted Alberta as my first cousin, but the correct half-niece designation is shown second on the list.

In this case, I’m fairly sure I know exactly why the relationship miscalculation occurred. Alberta’s mother, my half-sister, was born to my father’s first wife. My mother was 22 years younger than my father, so my mother is roughly the same age as my half-sister. I am the same age as my half-sister’s oldest children. Therefore, we have an unusual generational difference where ages might be misleading.

In the second position, MyHeritage estimated Alberta as half-aunt, which is the same as half niece, depending on whose perspective you’re speaking from, so cM Explainer was close. In normal circumstances, 1st Cousin is probably the most likely relationship although having children separated by two decades certainly is not unheard of.

MyHeritage correctly predicted 6 of 19 relationships, for 31.6% accuracy.

The correct relationship was on the relationship list most of the time, but was omitted entirely 4 times. The common factor in the entirely missing relationships is that they are all half-relationships. While they were not all from the same family line, they did all involve long generations, meaning children born over a very long period. That’s not uncommon with half-siblings, and half relationships are notoriously difficult to sort from other candidate relationships. These situations might possibly be considered statistical outliers.

Equivalent Relationships

A half first cousin should be genetically equivalent to a first cousin, once removed, based on the amount of expected DNA for those relationships.

However, in at least one case, these two relationships are calculated with different resulting probabilities. Half first cousin is 41.5%, and 1st cousins child (aka 1C1R or 1st cousin once removed) is 43.8%.

Keep in mind, though that MyHeritage is using the age of the two individuals in their calculations, which could alter the results based on the combination of factors calculated into the probabilities. It’s 85% likely that the match is one of those two relationships.

Your Thoughts?

I’m interested in your thoughts on this new tool. How does it work for you? What about endogamy or pedigree collapse? Do you find it useful? How are you utilizing it in your research?

Shortly, I’ll do a comparison article with other tools to see how the publicly available cM Explainer tool stacks up against the rest.

Thanks to MyHeritage for making this tool free for all to use, here.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, 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