What’s Changed? –  Autosomal DNA Vendor Feature Changes Since the 23andMe Data Compromise

The 23andMe customer data compromise has reverberated throughout the technology industry, not limited to DNA testing.

The 23andMe compromise has provided the impetus for reflection and security and policy reviews at each DNA testing vendor.

That’s a good thing.

What has been and remains challenging is keeping track of which features have been disabled and are no longer available at each vendor as the vendors, including 23andMe, attempt to right themselves from this blow. Unfortunately, or maybe fortunately, we can’t just return to “business as usual.”

Some of these feature removals may only be paused, and a few have already returned. Some may never be resumed.

We don’t really know yet.

If you’re having trouble keeping track, welcome to the club.

The features that have been disabled are features that were exploited at 23andMe or could have been exploited by bad actors who signed on “as you,” exposing not only your data but that of your matches in one way or another.

To be very clear, there was no data leak or compromise at any other vendor, but some other vendors provide(d) similar features for their customers. Every vendor offering DNA testing to genealogists had to stop, pause, and reevaluate their security measures. That’s exactly what they should have done. Genetic genealogy is a team sport where compromising one person’s account exposes at least some information about thousands more individuals.

Every company has proceeded somewhat differently based on how their features work.

I’ve compiled a chart listing the four primary vendors alphabetically, with affected features.

The Scorecard

In this chart, “Not available” means the feature was available before the 23andMe incident but is not currently available.

Feature 23andMe Ancestry FamilyTreeDNA MyHeritage
Two-factor Authentication (2FA)[1] Required Required Will be required for project administrators and available for all users[2] Will be required soon.
Forced Password Reset Yes No May be required for project administrators. Yes
Match information download[3] Not available Never was available Not available until after 2FA implementation Not available
Matching segment download[4] Not available Never was available Not available until after 2FA implementation Not available
Shared matches[5] Not available Available[6] Available Available
Shared matches who match each other Not available Never was available Available thru Matrix, but not segments Partially available through triangulation
Shared matches match segments Not available Never was available Never was available Never was available
Shared matches relationship to each other Not available Never was available Never was available Predicted available
Triangulation Not available Never was available Available[7] Available
Chromosome Browser Not available Never was available Available Available
Daily matching or browse rate limited[8] No No No Yes
Shared ethnicity with matches[9] Not available Available Available by opt-in Not available
Filter matches by ethnicity Never was available Never was available Never was available Not available

 

Accepts 23andMe DNA file uploads Not applicable Never was available Paused Not restricted but not available because 23andMe does not currently allow the download of your raw data file

Other features remain unchanged, so they are not mentioned.

I think I accounted for everything that has changed, including some features already resumed at MyHeritage.

23andMe has not stated if or when they will return any of the functionality that has been removed.

FamilyTreeDNA plans to return their paused features after 2FA has been implemented in early 2024.

Please note that this information may change at any time.

_____________________________________________________________

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

[1] There has been a great deal of gnashing of teeth surrounding 2FA and how it’s implemented at each vendor. If you experience issues, please contact the vendor in question.

[2] At FamilyTreeDNA, testers utilize a kit number as their username, not their name or email. No place is the kit number publicly associated with the user’s name. In the 23andMe breach, the user’s email and passwords had been exposed in earlier breaches, so the hacker simply tried the same username and password at 23andMe, with great success. That scenario cannot occur at FamilyTreeDNA because the username is not their email address, which is why 2FA is not required for users. Administrators can select their username, so they will be required to utilize 2FA soon.

[3] This means information about your DNA matches other than your matching segments, such as email address, maternal or paternal matches, notes, surnames, and other relevant information.

[4] Matching segment information for each match. Used for triangulation, ancestor identification, and at DNAPainter.

[5] Shared matches between you and another match.

[6] Ancestry has recently announced that they will require a membership to view several features available with a DNA test, including Common Ancestors (ThruLines), Notes, Trees, Groups, and filtering matches by unviewed status. These features will not be available to DNA testers without an Ancestry subscription.

[7] Available if maternal/paternal matching is enabled. When matching, each individual who matches the tester and other testers and is bucketed on the same maternal/paternal side will triangulate on at least one segment.

[8] This is to prevent data scraping if a bad actor gains access to your account.

[9] The 23andMe data was reported to have focused on both Jewish and Chinese customers

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

FamilyTreeDNA Provides Y DNA Haplogroups from Family Finder Autosomal Tests

Big News! FamilyTreeDNA is delivering holiday gifts early!

Y DNA haplogroups are beginning to be delivered as a free benefit to men who took the Family Finder test at FamilyTreeDNA. This is the first wave of a staggered rollout. Haplogroup results will be delivered to several thousand people at a time, in batches, beginning today.

This is no trivial gift and includes LOTS of information that can be used in various ways for your genealogy. Please feel free to share this article. The new Family Finder haplogroups are another reason to take a Family Finder test and to encourage other family members to do so as well.

How is this Even Possible?

Clearly, Y DNA is not autosomal DNA, so how is it possible to obtain a Y DNA or mitochondrial DNA haplogroup from an autosomal test? Great question!

Many autosomal DNA processing chips include a limited number of targeted Y and mitochondrial DNA SNP locations. Generally, those locations are haplogroup predictive, which is how haplogroup information can be obtained from an autosomal DNA test.

Compared to the actual Y DNA and mitochondrial DNA tests, only a small fraction of the information is available through autosomal tests. Only the full sequence mitochondrial DNA test or the Big Y-700 test will provide you with the full story, including your most refined haplogroup, additional information, and matching with other customers.

Having said that, haplogroups obtained from Family Finder provide important clues and genealogical information that will hopefully whet recipients’ appetites for learning even more.

Delivery Schedule

This first group of men to receive haplogroup results consists of testers who have purchased the Family Finder test since March 2019 when the most recent chip was put into production.

FamilyTreeDNA will be rolling haplogroups out in batches of a few thousand each day until everyone’s is complete, in the following order:

  • Family Finder tests purchased since March 2019 (their V3 chip)
  • Family Finder tests purchased between the fall of 2015 to March 2019 (their V2 chip)
  • Family Finder tests purchased from 2010 to the fall of 2015 (their V1 chip)
  • Autosomal uploads from other vendors for customers who have unlocked the advanced Family Finder features for $19

Uploaded DNA Files from Other Vendors

After the results are available for all males who have tested at FamilyTreeDNA, haplogroups will begin to be rolled out to customers who uploaded autosomal DNA files from other companies, meaning MyHeritage, Vitagene, 23andMe, and Ancestry.

To receive haplogroups for files uploaded from other vendors, the Family Finder advanced tool unlock must have been (or can be) purchased for $19. In addition to haplogroups, the unlock also provides access to the chromosome browser, myOrigins (ethnicity), Chromosome painting for myOrigins ethnicity, and ancient Origins.

Both MyHeritage and Vitagene tests are performed in the Gene by Gene lab. Those “uploads” are actually a secure business-to-business transaction, so the file integrity is assured.

Ancestry and 23andMe DNA files are downloaded from those companies, then uploaded to FamilyTreeDNA. Some people build “composite” files in the format of these companies, so FamilyTreeDNA has no way to assure that the original DNA upload file hasn’t been modified and it is a legitimate, unmodified, file from either 23andMe or Ancestry. Hence, in some situations, they are treated differently.

Both Ancestry and 23andMe utilize different chips than FamilyTreeDNA, covering different SNPs. Those results may vary slightly from results available from native FamilyTreeDNA tests, and will also vary from each other. In other words, there’s no consistency, and therefore haplogroup accuracy cannot be confirmed.

Haplogroups resulting from tests performed in the FamilyTreeDNA lab will be visible to matches and on the SNP pages within projects. They will also be used in both Discover and the haplotree statistics. This includes Family Finder plus MyHeritage and Vitagene DNA file uploads.

Tests performed elsewhere will receive haplogroups that will only be visible to the user, or a group administrator viewing a kit within a project. They will not be visible to matches, used in trees or for statistics.

At their recent conference, FamilyTreeDNA provided this slide during an update about what to expect from Family Finder haplogroups.

Today, only Y DNA haplogroups are being provided, but after the new mitochondrial tree is available, customer haplogroups are updated, and MitoDiscover (my name, not theirs) is released, FamilyTreeDNA is planning to provide mitochondrial DNA haplogroups for Family Finder customers as well. The current haplogroup estimate is late 2024 or even into 2025.

Unfortunately, some of Ancestry’s DNA files don’t include mitochondrial DNA SNPs, so some customers who’ve uploaded Ancestry files won’t receive mitochondrial haplogroups.

STR Haplogroups to be Updated

All FamilyTreeDNA customers who have taken Y DNA STR tests, meaning 12, 25, 37, 67, or 111 markers, receive predicted haplogroups. Often, the Family Finder extracted results can provide a more refined haplogroup.

When that is possible, STR test predicted haplogroup results will be updated to the more refined Family Finder haplogroup.

Furthermore, while STR results are quite reliably predicted, Family Finder results are SNP-confirmed.

Notification

When your Family Finder test has received a haplogroup or your STR-derived haplogroup has been updated, you’ll receive an email notification with a link to a short, less than 2-minute video explaining what you’re receiving.

You can also expect emails in the following days with links to additional short videos. If you’d like to watch the videos now, click here.

You can also check your results, of course. If you should have received an email and didn’t, check your spam folder, and if it’s not there, notify FamilyTreeDNA in case your email has managed to get on the bounce list.

Group project administrators will receive notifications when a haplogroup is updated for a member in a project that they manage. This doesn’t just apply to Family Finder haplogroup updates for STR results – notifications will arrive when Big Y haplogroups are updated, too.

Emails about haplogroup updates will include both the old and the updated haplogroup.

Haplogroups may change as other testers receive results, forming a new haplogroup. The Big Y-700 test is evergreen, meaning as the Y tree grows, testers’ results are updated on an ongoing basis.

New View

Let’s take a look at what customers will receive.

In one of my surname projects, one male has taken a Family Finder test, but not the Y DNA test.

Several other men in that same paternal line, who are clearly related (including his brother), have taken Y DNA tests – both STR and the Big Y-700.

We have men who have taken the Big Y-700 test, STR tests only (no Big Y), and one with only a Family Finder test, so let’s compare all three, beginning with the man who has taken a Family Finder test but no Y DNA tests.

He has now been assigned to haplogroup I-BY1031, thanks to his Family Finder test.

Before today, because he has not taken a Y DNA test, he had no haplogroup or Y DNA Results section on his personal page.

Today, he does. Of course, he doesn’t have STR results or matches, but he DOES have confirmed SNP results, at least part way down the tree.

He can view these results on the Haplotree & SNPs tab or in Discover. Let’s look at both.

Haplotree & SNPs

By clicking on the Haplotree & SNPs link, you can view the results by variants (mutations,) as shown below, or by countries, surnames, or recommended projects for each haplogroup.

Of course, as more Family Finder results are rolled out, the more names and countries will appear on the Haplotree.

Recommended Projects

It’s easy to determine which haplogroup projects would be a good fit for people with these new haplogroups to join.

Just view by Recommended Projects, then scan up that column above the selected haplogroup. You can even just click right there to join. It’s that easy!

Results still won’t show on the public project page, because these testers don’t have STR results to display. Perhaps this will encourage additional testing in order to match with other men.

Download SNP Results

If you’re interested, you can download your SNP results in spreadsheet format.

I’m only showing four of my cousin’s positive SNPs, but FamilyTreeDNA was able to extract 358 positive SNPs to assign him to haplogroup I-BY1031.

Are Family Finder Haplogroups Better Than STR Test Predicted Haplogroups?

How do Family Finder haplogroups stack up against STR-predicted haplogroups?

Viewing the Y DNA results of related cousins who have taken STR tests, but not the Big Y-700, we see that their Y DNA haplogroup was predicted as I-M253.

We also know that the haplogroup determined by the Big Y-700 for this line is I-BY73911.

How can we use this information beneficially, and what does it mean?

Discover

Family Finder haplogroups can access Discover, which I wrote about, here.

Clicking on the Discover link takes you to your haplogroup story.

Let’s look at the new Family Finder Haplogroup Story for this tester.

Haplogroup I-BY1031 is about 3100 years old and is found in England, Sweden, the US, and 14 other countries. Of course, as more Family Finder haplogroups are provided to customers, this information will change for many haplogroups, so check back often.

Of course, you’ll want to review every single tab, which are chapters in your ancestral story! The Time Tree shows your haplogroup age in perspective to other haplogroups and their formation, and Ancient Connections anchors haplogroups through archaeology.

You can share any Discover page in several ways. This is a good opportunity to excite other family members about the discoveries revealed through DNA testing and genealogy. Prices are reduced right now with the Holiday Sale, too, so it’s a great time to gift someone else or yourself.

Compare – How Good is Good?

Ok, so how much better is the Family Finder haplogroup than the STR-predicted haplogroup, and how much better is the Big Y-700 haplogroup than the other two?

I’ll use the Discover “Compare” feature to answer these questions.

First, let’s compare the STR-predicted haplogroup of I-M253 to the Family Finder haplogroup of I-BY1031.

I clicked on Compare and entered the haplogroup I wish to compare to I-BY1031.

I-M253 I-BY1031 I-BY73199
Haplogroup Source STR Predicted Family Finder Big Y-700
Formation Year 2600 BCE 1100 BCE 1750 CE
Age – Years ago 4600 3100 270
Era Stone Age, Metal Age Metal Age Modern
Ancestral Locations England, Sweden, Germany, UK, +100 Sweden, England, US, +14 Netherlands
Tested Descendants 26,572 121 2
Branches 6779 69 0 – this is the pot-of-gold end leaf on the branch today

I created this chart to compare the major features of all three haplogroups.

The STR-predicted haplogroup, I-M253, takes you to about 2,600 BCE, or about 4,600 years ago. The Family Finder haplogroup shifts that significantly to about 1100 BCE, or 3100 years ago, so it’s about 1500 years more recent. However, the Big Y haplogroup takes you home – from 3100 years ago to about 270 years ago.

Notice that there’s a LOT of room for refinement under haplogroup I-M253. A Big Y tester might wind up on any of those 6779 branches, and might well be assigned to a newly formed branch with his test. The Family Finder haplogroup, I-BY1031, which was, by the way, discovered through Big Y testing, moved the autosomal test taker forward 1500 years where there are 121 descendants in 69 branches. The Big Y-700 test is the most refined possible, moving you directly into a genealogically relevant timeframe with a very specific location.

I-M253 is found in over 100 countries, I-BY1031 in 17 and I-BY73199 is found only in one – the Netherlands.

Based on confirmed genealogy, the common ancestor of the two men who have Big Y-700 haplogroup I-BY73199 was a man named Hendrik Jans Ferwerda, born in 1806 in the Netherlands, so 217 years ago. Of course, that haplogroup itself could have been born a generation or two before Hendrik. We simply won’t know for sure until more men test. More testers refine the haplotree, haplogroup ages, and refine our genealogy as well.

Haplogroup Comparison and Analysis

Let’s look at the Discover “Compare” feature of the three haplogroups from my family line from the Netherlands. Please note that your results will differ because every haplogroup is different, but this is a good way to compare the three types of haplogroup results and an excellent avenue to illustrate why testing and upgrades are so important.

The haplogroup ages are according to the Discover Time Tree.

Y-Adam to Haplogroup I1 I-M253 STR Haplogroup  to I-BY1031 Family Finder Haplogroup I-BY1031 Family Finder Haplogroup to BY73199 Big Y Haplogroup
Y-Adam (haplogroup A-PR2921) lived about 234,000 years ago
A0-T
A1
A1b
CT
CF
F
GHIJK
HIJK
IJK
IJ
I
M170
Z2699
L840
I1 I1
I-M253 lived about 4600 years ago
DF29
Z58
Z2041
Z2040
Z382
Y3643
Y2170
FT92441
FT45372
PH1178
BY1031 I-BY1031 lived about 3100 years ago
FT230048
BY65928
BY61100
I-BY73199 lived about 270 years ago

 All of the base haplogroups in the first column leading to Haplogroup I span the longest elapsed time, about 230,000 years, from Y-Adam to I-M253, the STR-predicted haplogroup, but are the least relevant to contemporary genealogy. They do tell us where we came from more distantly.

The second column moves you about 1500 years forward in time to the Family Finder confirmed haplogroup, reducing the location from pretty much everyplace in Europe (plus a few more locations) with more than 6700 branches, to 69 branches in only 17 countries.

With the fewest haplogroups, the third column spans the most recent 2800 years, bringing you unquestionably into the genealogically relevant timeframe, 270 years ago, in only one country where surnames apply.

If we had more testers from the Netherlands or nearby regions, there would probably be more branches on the tree between BY1031 and BY73199, the Big Y-700 haplogroup.

The second column is clearly an improvement over the first column which gets us to I-M253. The Family Finder upgrade from I-M253 to BY1031 provides information about our ancestors 3000-4500 years ago, where they lived and culturally, what they were doing. Ancient Connections enhance that understanding.

But the third column moves into the modern area where surnames are relevant and is the holy grail of genealogy. It’s a journey to get from Adam to the Netherlands in one family 270 years ago, but we can do it successfully between Family Finder and the Big Y-700.

Family Finder Matching

Given that these new haplogroups result from Family Finder, how do these results show in Family Finder matching? How do we know if someone with a haplogroup has taken a Y DNA test or if their haplogroup is from their Family Finder test?

  • All Family Finder haplogroups will show in the results for people who tested at FamilyTreeDNA as soon as they are all rolled out
  • All MyHeritage and Vitagene uploads, because they are processed by the Gene by Gene lab, will be shown IF they have purchased the unlock.
  • No Ancestry or 23andMe haplogroups will be shown to Family Finder matches

To determine whether or not your matches’ haplogroups result from a Y DNA test or a Family Finder haplogroup, on your Family Finder match page, look just beneath the name of your matches.

The first man above received the Family Finder haplogroup. You can see he has no other tests listed. The second man has taken the Big Y-700 test. You can see that he has a different haplogroup, and if you look beneath his name, you’ll see that he took the Big Y-700 test.

For other men, you may see the 67 or 111 marker tests, for example, so you’ll know that they are available for Y-DNA matching. That may be important information because you can then visit the appropriate surname project to see if they happen to be listed with an earliest known ancestor.

After the rollout is complete, If you have a male Family Finder match with no haplogroup shown, you know that:

  • They did not test at FamilyTree DNA
  • If they uploaded from MyHeritage or Vitagene, they did not unlock the advanced Family Finder features
  • Or, they tested at either 23andMe or Ancestry, and uploaded their results

You can always reach out to your match and ask.

How to Use This Information

There are several great ways to utilize this new information.

I have a roadblock with my Moore line. Moore is a common surname with many, many origins, so I have autosomal matches to several Moore individuals who may or may not be from my Moore line.

I do know the base haplogroup of my Moore men, but I do not have a Big Y, unfortunately, and can’t upgrade because the tester is deceased. (I wish I had ordered the Big Y out the gate, but too late now.)

As soon as the results are complete for all of the testers, I’ll be able, by process of elimination to some extent, focus ONLY on the testers who fall into Family Finder haplogroup of my Moore cousins, or at least haplogroup close for Ancestry or 23andMe upload customers. In other words, I can eliminate the rest.

I can then ask the men with a similar haplogroup to my proven Moore cousins for more information, including whether they would be willing to take a Y DNA test.

  • Second, as soon as the Family Finder processing is complete, I will know that all male Family Finder matches and uploads from MyHeritage and Vitagene that have paid for the unlock will have haplogroups displayed on the Family Finder Match page. Therefore, if there’s a male Moore with no haplogroup, I can reach out to see where they tested and if a haplogroup has been assigned, even if it’s from Ancestry or 23andMe and isn’t displayed in Family Finder.

If so, and they share the haplogroup with me, I’ll be able to include or exclude them. If included, I can then ask if they would consider taking a Y DNA test.

  • Third, for lines I don’t yet have Y DNA testers for, I can now peruse my matches, and my cousins’ matches for that line. See items one and two, above. Even if they don’t reply or agree to Y DNA testing, at least now I have SOME haplogroup for that missing line.

Discover will help me flesh out the information I have, narrow regions, find projects, look at ancient DNA for hints, and more.

  • Fourth, the haplogroups themselves. I don’t know how many million tests FamilyTreeDNA has in their database, but if we assume that half of those are male, some percentage won’t have taken a Y DNA test at all. We’ll be able to obtain Y-DNA information for lines where there may be no other living descendant. I have at least one like that. He was the end of the surname line and is deceased, with no sons.

I’m literally ecstatic that I’ll be able to obtain at least something for that line. If it’s anything like my example Netherlands lineage, the Family Finder haplogroup may be able to point me to an important region of Europe – or maybe someplace else very unexpected.

The Bottom Line

Here’s the bottom line. You don’t know what you don’t know – and our ancestors are FULL of surprises.

I can’t even begin to tell you how MUCH I’m looking forward to this haplogroup rollout.

To prepare, I’m making a list of my genealogical lines:

  • If the paternal line, meaning surname line, is represented by any match in any database
  • If that line is represented by a known person in the FamilyTreeDNA database and by whom
  • If they or someone from that line has joined a surname or other FamilyTreeDNA project, and if so, which one
  • If they’ve taken a Y DNA test, and what kind – watch STR results for an updated haplogroup
  • If they’ve taken a Family Finder test – my cousin is a good example of a known individual whose kit I can watch for a new haplogroup
  • Old and new haplogroup, if applicable

If my only relative from that line is in another vendor’s database, I’ll ask if they will upload their file to FamilyTreeDNA – and explain why by sharing this article. (Feel free to do the same.) A Y DNA haplogroup is a good incentive, and I would be glad to pay for the unlock at FamilyTreeDNA for cousins who represent Y and mitochondrial DNA lines I don’t already have.

One way I sweeten the pie is to offer testing scholarships to select lines where I need either the Y DNA or mitochondrial DNA of relevant ancestors. It’s a good thing these haplogroups are being rolled out a few thousand at a time! I need to budget for all the scholarships I’ll want to offer.

I feel like I won the lottery, and FamilyTreeDNA is giving me a free haplogroup encyclopedia of information about my ancestors through my cousins – even those who haven’t taken Y DNA tests. I can’t even express how happy this makes me.

What lines do you want to discover more about, and what is your plan? Tests are on sale now if you need them!

_____________________________________________________________

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

Geneanet DNA to End on December 20, 2023

Today, Geneanet announced that they are discontinuing all DNA features on their platform.

Geneanet was purchased by Ancestry more than three years ago and offered DNA uploads and matching, with a chromosome browser, beginning in 2020. They did not offer DNA testing, so anyone who uploaded has to have tested elsewhere, meaning they are in another database somewhere.

Geneanet announced that:

  • As of today, DNA uploads will no longer be accepted.
  • On December 20th, in exactly 30 days, the entire DNA section will be permanently deleted, including your DNA file that you uploaded.

They don’t give any reason other than the DNA program didn’t meet their expectations, and they will focus on other customer-requested features now.

My initial reaction was that this might be due to the 23andMe data exposure issue that I wrote about here, here, and here. However, given the 7-week delay, I think that’s unlikely. Additionally, Geneanet is encouraging people to download their matches now, before the deletion. During this same time, other genealogy DNA companies have removed or restricted match downloads, which makes the 23andMe issue seem like an unlikely catalyst for their decision.

Geneanet states that none of its premium member features will be affected by this decision.

If Geneanet’s pending DNA exit affects you, you might want to take whatever action you deem appropriate, now, before the holidays distract you and you forget about it altogether.

Many people used Geneanet for its European focus to connect with European DNA matches. If this applies to you, I suggest that you upload your DNA files to both MyHeritage (here) and FamilyTreeDNA (here) if you haven’t already done so. MyHeritage has a significant European customer base, thanks to their abundant genealogy research records, and FamilyTreeDNA has many European testers with its 23-year history and European project offerings.

While the Geneanet exit from DNA may be inconvenient, it’s not a disastrous loss. You can find those Geneanet DNA matches elsewhere because they didn’t test at Geneanet.

You can read Geneanet’s blog posting, 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

Holiday DNA Sales Are Here!!!

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

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

MyHeritage

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

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

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

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

FamilyTreeDNA

Every test is on sale at FamilyTreeDNA.

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

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

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

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

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

Genealogy Goals

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

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

My goal is to:

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

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

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

Introduction

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

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

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

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

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

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

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

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

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

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

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

Ancient DNA

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

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

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

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

Wesley Revels’ Lineage

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

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

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

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

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

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

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

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

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

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

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

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

Mr. Lynn

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

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

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

Family members are found in Baldwin Township, shown above.

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

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

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

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

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

The 1890 census does not exist.

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

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

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

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

Subclades of Haplogroup O

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

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

How Closely Related Are These Haplogroup O Men?

How closely related are these two men?

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

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

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

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

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

Information provided by the project administrators is as follows:

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

Resources:

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

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

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

Haplogroup O Project Group Time Tree

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

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

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

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

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

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

Discover Time Tree

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

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

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

Geography

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

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

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

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

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

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

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

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

Academic Papers

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

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

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

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

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

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

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

The Spanish

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

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

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

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

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

Five Possibilities

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

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

Do we have any additional evidence?

Other Haplogroup O DNA

From my book, DNA for Native American Genealogy:

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

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

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

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

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

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

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

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

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

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

FamilyTreeDNA Haplotree and Discover

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

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

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

Let’s look at our three distinct clusters.

Cluster 1 – Pacific Northwest – Alaska and Canada

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

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

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

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

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

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

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

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

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

Cluster 2 – Mexico

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

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

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

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

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

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

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

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

Cluster 3 – East Coast

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Returning to the Discover Time Tree Maps

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Timeline

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

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

Conclusions

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

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

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

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

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

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

What’s Next?

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

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Étienne Hebert (c1625-c1670): Two French Brothers & Their Ancient Ancestors – 52 Ancestors #413

In the book, Les vielles familles d’Yamachiche: vingt-trois généalogies, v. 4 published in 1908 in Ontario, we discover that Étienne Hebert is one of two brothers who came from France and settled in Acadia, now Nova Scotia. Étienne married Marie Gaudet and Antoine Hebert married Genevieve LeFranc.

We know that Étienne and Antoine were brothers because in the 2nd marriage record for Jean-Jacques Hébert (1681-?) to Marguerite Leprince on April 27, 1734, at Saint-Charles-les-Mines, they were granted a dispensation from a 3rd degree consanguine relationship. The only overlap in their two family trees would be the parents of Étienne and Antoine Hebert.

Thank goodness for those church records.

Origins

Stephen A. White provided the following information about Étienne.

HÉBERT, Étienne, came from France with his wife Marie Gaudet, according to nine depositions: one from his grandson Jean Hébert (Doc. inéd., Vol. III, p. 11), one from Pierre Trahan, husband of his granddaughter Madeleine Comeau (ibid., p. 8), one from Pierre and Madeleine’s son Pierre Trahan (ibid., pp. 110-111) and one from their nephews Sylvestre and Simon Trahan (ibid., p. 30), two from husbands of Étienne’s great-granddaughters (ibid., Vol. II, p. 182; Vol. III, p. 90), one from a great-great-grandson (ibid., Vol. III, pp. 93-94), and two from husbands of his great-great-granddaughters (ibid., pp. 45, 92-93). Seven of these depositions name his wife as Marie Gaudet; only those of the two Pierre Trahans, father and son, do not.

Lucy LeBlanc Consentino documents these priceless depositions here.

Parents

There have been several proposed and presumed parents of Étienne and Antoine Hebert. None are proven, and some have been disproven. I’m not going to recount each theory here. I’ll briefly mention the most common ones and strongly suggest that anyone tempted to assign parents for these men consult existing resources and arguments first.

Tim Hebert’s website is no longer online, but you can view it here at Wayback Machine. Tim did an exceptional job documenting the various theories and Hebert descendants.

It has been said that possibly the brothers were from south of Loudon (LaChaussee, Martaize, etc.), however, since Charles Menou d’Aulnay’s family had land in that vicinity. If he recruited settlers from that area, there is a chance they came from there, but there is no proof of where they (or most other) Acadians came from. The linguistic studies by Genevieve Massignon tried to say that they were from the Loudon area, but perhaps she was focusing too much. It is probably true that they came from western France. But the lack of documentation in the Loudon region means that perhaps we’re looking in the wrong place. Michael Poirier has suggested they came from west of Loudon at the coast … near Baie de Bourgneuf.

He bases this on:
– the location of the monastery of the Assumption (on the island Chauvet), which was regularly attended by Richelieu and was the property of his brother, Alphonse.
– Port-Royal and the church of St Jean-Baptiste
– salt-water marshes in the area were drained … much like the dyke system utilized in Acadia
– it was a zone surrounded by Protestants and enclosing Catholics

Genevieve Massignon (1921-1966) argues that a number of familial alliances existed among the first Acadian settlers PRIOR to their arrival from France, pointing to a common French origin. She believes they lived in the Acadian Governor d’Aulnay’s seigneury in France near Loudun (comprised of the villages of Angliers, Aulnay, Martaizé, and La Chausée). The Hébert family was allied with the Gaudets through Étienne’s marriage to Marie. Marie’s sister Francoise was also allied with the Leblanc family through her marriage to Daniel. Evidence of their marriages in France is found in the Belle-Isle-en-Mer declarations in 1767. Moreover, a certain Jean Gaudet was censistaire in 1634 on land at Martaizé (Vienne) in the Seigneurie owned by the mother of Acadian governor Charles d’Aulnay. However, Massignon’s research failed to find any relevant baptismal or marriage records.

Another couple, Jacques Hebert and Marie Juneau have been debunked as parents, based on the date of their marriage and analysis by Stephen White. Jacques was found in Acadia 30 years before Étienne and Antoine, then moved into mainland Canada. It’s unlikely that his two sons would be found in Acadia and not near or with him. Not to mention the depositions that state that Étienne and Antoine were born in France.

Another parent candidate was Louis Habert who is generally considered to have been the first permanent settler in Canada, arriving in 1604. He married Marie Rolet in Paris in 1602 but wasn’t known to live in Acadia. Spelling variations of this family name include Hebert, Harbert, Herbert, Herbot, Harbelot, and others. You can read more about this at FamilySearch here.

One source stated that Stephen White reported that Etienne Hebert arrived on the ship, La Verge in 1648. Karen Theriot Reader, upon further examination, determined that the page given as the source does not in fact provide that information, nor elsewhere by White.

However, the Verve did arrive in 1648, chartered by Emmanuel LeBorgne, Sieur of Coudray, to transport supplies. No passenger list exists, and several ships arrived in Acadia over the years.

In a letter to Tim Hebert, Stephen White stated that their parents are “unknown.” No birth records have been found, and White found none of the proposed parents convincing or even probable.

We simply don’t know when and where Étienne and Antoine were born. It’s fair to say it was in France because families weren’t imported until 1636. The Hebert brothers were born in the 1620s. They would have been teenagers or young men in 1636.

What Was Happening in Acadia?

Warm up your tea or coffee, ‘cause this is a fascinating tale.

Acadia was truly the frontier and constantly caught in the middle in a tug of war between France and England for control of both the land and resources, along with the people.

Settlement in Acadia began in 1604, but we’re joining this history 28 years later.

In 1632, control of Acadia passed from the English back to the French, who immediately launched voyages transporting traders and workers, some of whom became settlers. Their initial goal wasn’t settlement, though, but trading posts.

Port Royal is shown on Champlain’s 1632 map.

Isaac de Razilly was a French noble sea captain and knight who convinced his cousin, Cardinal Richelieu, chief minister to the King of France, that colonizing and establishing fur trade with Acadia was a profitable business venture. As a bonus that probably sounded attractive to Richelieu, they could convert and baptize the Native people, too.

Razilly’s 1632 voyage on the L’Esperance a Dieu included about 300 people, mostly men with possibly 12-15 women. A French newspaper report from that time states that a third ship from Rochelle joined the other two. A mason, baker, nailmaker-blacksmith, joiners, gunsmiths, sawyers, laborers, and soldiers signed up.

In 1640, notarial records in La Rochelle, France, show many contracts of engagement for workers in Acadia, although most of those people aren’t shown in the 1671 census, meaning they either died or returned to France when their engagement was over. In 1640, at least 25 men and 5 women signed up.

Couillard-Despres in “Les Gouvernors” states that 63 men arrived on the Saint Clement in 1642 to assist Charles LaTour.

After Razilly’s death in 1635, his cousin, Charles de Menou d’Aulnay, de Charnisay prepared to take over the administration of Acadia. By this time, there were 44 inhabitants at Le Have, Razily’s base of operation. Sometime between 1635 and 1640, d’Aulnay moved the settlement to Port Royal, but the men who had married Native American women likely did not move with him.

However, Charles La Tour, who had lived in Acadia since he was 17 and was married to a Mi’kmaq woman, had other plans. His father, Claude, obtained a grant for Nova Scotia from the English king, and Charles was appointed Governor, serving from 1631-1642. In essence, the LaTour father-son duo had outsmarted d’Aulnay.

Workers still continued to arrive. The 1636 passenger list of the St. Jehan, including occupations and some location origins, still exists.

d’Aulnay and La Tour began as competitors, with LaTour working out of Cap Sable and the St. John River area with traders, and d’Aulnay, who moved the Acadian settlement from La Have to Port Royal, beginning cultivation. Given where we find Étienne Hebert living, he likely arrived with d’Aulnay.

However, the competition between those men soon became animosity, then open warfare, with both men claiming to be in charge of all of Acadia.

If you think there was no drama in a relatively unpopulated area, just try to keep this next bit straight.

In 1640, after LaTour’s Mi’kmaq wife died, he married a French Huguenot woman, Françoise-Marie Jacquelin, who had powerful connections.

In 1642, d’Aulnay had LaTour, a Huguenot, charged with treason against France. LaTour’s well-connected wife traveled to France to advocate on behalf of her husband, returning with a warship for him to defend himself.

Perhaps this was a bit hasty.

In the Spring of 1643, La Tour led a party of English mercenaries against the French Acadian colony at Port-Royal. His 270 Puritan and Huguenot troops killed three men, burned a mill, slaughtered cattle, and seized 18,000 livres worth of furs.

Apparently, LaTour was a traitor after all, at least from the French perspective.

LaTour then traveled to Boston seeking reinforcements from the English, and while he was gone, d’Aulnay seized all of his possessions and outposts, including Fort LaTour.

Are you keeping track of this? I think the score was 3 to 3 here, with a Hail Mary pass underway. Get the popcorn.

LaTour may have been traveling to Boston, but his wife, Françoise-Marie, had remained at home and was not about to relinquish Fort LaTour without a fight.

In the ensuing battle, Françoise-Marie, at the ripe old age of 23, defended Fort LaTour in the Battle of St. John for three days, using the warship. D’Aulnay lost 33 men but on the fourth day, was able to capture the fort. LaTour’s men were hung at the gallows as Françoise-Marie was forced to watch with a rope around her neck, just in case she got any bright ideas. She was clearly not a woman to be trifled with.

Françoise-Marie was not hung, but Nicolas Denys recorded in his journal that she died three weeks later as a prisoner in captivity. The cause remains unknown, but it’s safe to say that her death was a volley in war. 

After learning that his wife had died, his possessions confiscated, and his men killed, LaTour sought refuge in Quebec City. He did not return to Acadia for several years, but return he would – eventually.

For the time being, d’Aulnay was firmly in control, but that only lasted a few years.

In 1650, d’Aulnay drowned when his canoe overturned, which provided the opening LaTour had been waiting for. LaTour sailed to France, obtained royal favor, his property restored, and returned to Acadia as governor in 1653, accompanied by several new colonists, including Philippe Mius d’Entremont, 1st Baron of Pobomcoup.

It was about this time, around 1650, that Étienne Hebert married Marie Gaudet. Perhaps they hoped that living near her parents, a dozen miles upriver, would be more peaceful and less exposed to attack and conflict.

LaTour had remained a widower since his wife’s death defending Fort LaTour in 1645, but in 1653, he married…wait for it… d’Aulnay’s widow, Jeanne Motin. It was not a marriage in name only, as they had five children. Some said they married to heal the rift between the warring d’Aulnay and LaTour camps, some think it was simply a marriage of convenience for both, and others feel it was LaTour’s final victory over d’Aulnay. However, Jeanne was no shrinking violet because she evicted Nicolas Denys when he attempted to exploit d’Aulnay’s death by setting up trading posts at St. Ann and St. Peters.

LaTour wasn’t off the hook, though, because in an odd sort of way, d’Aulnay still managed to be a thorn in LaTour’s side – even from beyond the grave.

Along with d’Aulnay’s property and wife came his substantial debts to Emmanuel Le Borgne, his main financier from La Rochelle. There were two sides to this story because, as part of the deal, La Bourg and other seigneurs were supposed to recruit and transport new settlers to Acadia and care for them by building communal resources like mills and bake-ovens, but they didn’t.

It appears that the Acadians and their French sponsors were both relatively unhappy. The French did not live up to their end of the bargain by building mills and ovens, and consequently, the Acadians resisted paying taxes. Everyone resented the English, but the English needed the Acadian settlers to work the land. And, of course, the land passed back and forth between the French and English from time to time, punctuated by skirmishes and outright attacks.

Acadia, for an Atlantic peninsula of land with few people, was drama-central.

By 1653, it was estimated that there were 45-50 households at Port Royal and La Have, which provides us an estimate of 300-350 people, including 60 single men. Étienne Hebert was lucky to find a bride, any bride.

In 1654, Port Royal was still small, with approximately 270 residents, as estimated by pioneer Nicholas Denys. Denys was a French prisoner at Port Royal who had been responsible for recruiting volunteers for the 1632 Razilly expedition of 300 men from Rochelle, France. They landed at La Hève near modern Bridgewater, the eventual site of the Gaudet village. This location was near the upper reaches of the tidal portion of the Riviere du Dauphine, and their boat probably could not progress further.

Denys did us the favor of describing Port Royal in 1653:

There are numbers of meadows on both shores, and two islands which possess meadows, and which are 3 or 4 leagues from the fort in ascending. There is a great extent of meadows which the sea used to cover, and which the Sieur d’Aulnay had drained. It bears now fine and good wheat, and since the English have been masters of the country, the residents who were lodged near the fort have for the most part abandoned there houses and have gone to settle on the upper part of the river. They have made their clearings below and above this great meadow, which belongs at present to Madame de La Tour. There they have again drained other lands which bear wheat in much greater abundance than those which they cultivated round the fort, good though those were. All the inhabitants there are the ones whome Monsieur le Commandeur de Razilly had brought from France to La Have; since that time they have multiplied much at Port Royal, where they have a great number of cattle and swine.

The commentary about the French settling on the upper part of the river may be very important for the Hebert family because that’s exactly where they are found.

Denys also recorded that Robert Sedgewick of Boston had been ordered by Robert Cromwell to attack New Holland (New York). As Sedgewick prepared, a peace treaty was signed between the English and the Dutch. Since he was “all dressed up with nowhere to go,” he attacked Acadia in August 1654 and destroyed most of the settlements, including Port Royal, La Have, and the Saint John River village. Sedgewick left the area but appointed an Acadian council with Guillaume Trahan in charge. Some of the French may have returned to France at this point.

Denys doesn’t say if Sedgewick burned the upper river homesteads and farms or if he was satisfied with torching Port Royal. Living 12-14 miles away in the out-country may have been the saving grace of the Hebert and Gaudet families. Or, their homesteads and farms may have been destroyed, too. Certainly, if not burned out, they were devastated by Acadia falling to the English.

Acadia was back under English rule and would remain so until being returned, again, to the French in 1667.

After Sedgewick captured Acadia for the English, LaTour went to London to regain his property, again. Being a Protestant would have worked in his favor, as well as having led the English in raids against Port Royal in 1643.

In 1656, Cromwell granted property to two Englishmen and LaTour, but LaTour sold his share to the Englishmen and moved to Cap Sable, on the southern end of the peninsula, to attempt to live the rest of his life in peace.

We don’t know positively that the Hebert brothers were in Acadia at this time, but it’s almost assured. They had probably been in Acadia for between 10 and 30 years. If White is correct, they had resided in Acadia for eight years. Windows of immigration existed, but generally only when the French were in charge, although France imported settlers to other nearby parts of New France. The French were not imported directly into Acadia when the English ruled.

In 1666, France stopped sending colonists, ostensibly for fear of depopulating the mother-country. However, the English were still arriving in the colonies to escape religious prosecution and for economic reasons. Therefore, the Acadians were exposed to at least some English settlers, probably spoke and understood at least a little English, and established some level of trade with the English colonies along the Eastern seaboard.

By Mikmaq – Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=1351882

Given the 1671 census and the ages of his children, we know Étienne was married by 1651 and that his wife’s parents also settled in Acadia.

Life in Acadia always seemed to be contentious and apparently, in no small part, dangerous.

Étienne was probably in his mid to late 40s when he died, about 1670. He clearly didn’t die of old age, but probably as a result of hunting, fishing, or farming – some accident. Or, perhaps, there was a skirmish. It seemed like there was always some sort of skirmish, but a simple act of daily living such as fishing carried the risk of drowning.

The Catholic church records don’t exist, if they even had a priest at that time, so we don’t know when Étienne died. We can rest assured that, if possible, he was buried in the parish cemetery, now the Garrison Cemetery in Annapolis Royal, beside the fort and the Catholic church.

The First Acadian Census

Even though Acadia was officially returned to France in 1667, it didn’t actually happen right away. In 1670, the English surrendered the fort at Port Royal, apparently without incident. The new French governor arrived, bringing with him another 60 settlers and 30 soldiers. The new governor ordered a census, thankfully. He likely needed to know how many people would be paying taxes.

The first Acadian census was taken in 1671, documenting between 240 and 350  Acadian residents (depending which count you utilize) in 68 households in Port Royal and one household each in three other locations. Historians know some residents in settlements weren’t counted, and neither were Acadian/Native American families living with the Native people. Estimates of the entire Acadian population reach as high as 500.

Étienne was already deceased, but we can tell quite a bit from his widow’s census record, transcribed here by Lucy LeBlanc Consentino.

Marie Gaudet, widow of Étienne Hebert, 38. She has 10 children, two married children: Marie 20, Marguerite 19; Emmanuel 18, not yet married, Étienne 17, Jean 13, Francoise 10, Catherine 9, Martine 6, Michel 5, Antoine 1, 4 cattle, 5 sheep and 3 arpents of cultivated land.

This tells us that Etienne and Marie were married in about 1650, or maybe somewhat earlier. Their eldest living child was age 20. Étienne was probably about 25 years old when he married, so I’d estimate his birth year as 1625, give or take a few years. It appears that Marie Gaudet and her daughter, Marie Hebert, and her husband, Michel de Forest, and their families were probably living either on the same farm or even in the same house.

Marie’s youngest child was age 1, so we know that Étienne died sometime between 1669 and 1671.

His brother, Antoine Hebert is listed three houses away as a 50-year-old cooper, so he was born about 1621.

Hebert and Gaudet Allied Families

It’s clear that the Hebert family was somehow allied with the Gaudet family as early as 1650 when their children married. It’s possible that they married in France, or Acadia.

What we do know is that these two families lived in close proximity on the Riviere de Dauphine, now the Annapolis River.

This 1733 map at the Nova Scotia Archives is based on the 1707 census route and shows about a mile and a half or two miles distance between the Hebert and Gaudet homesteads – 57 years after Étienne Hebert and Marie Gaudet married.

Etienne Hebert lived along Bloody Creek, where the Hebert Village is found, courtesy of MapAnnapolis, below.

We know where Etienne, Marie, and their family lived and at least something about their life – but what else can we unearth?

The Hebert DNA Story

Eventually, the answer to where the Hebert brothers originated in France will be told through their Y-DNA, passed directly from father to son through the generations without ever being admixed with the mother’s DNA, or divided.

The Hebert family is well-represented in the Acadian AmerIndian Project with three Big-Y testers showing the same haplogroup. Haplogroup R-BY31006 was born about 1650, almost exactly when Étienne and his brother were marrying and having children near Fort Royal.

Click to enlarge any image

Two present-day project members descend from Étienne, and one descends from Étienne’s brother, Antoine. They have the same high-resolution haplogroup, so we know that their father had the same mutation that he gave to both sons. How I wish some Hebert men from France could test, but DNA testing for genealogy is illegal there.

Unfortunately, no other contemporary man of any surname is close to our Hebert cluster. The haplogroup ancestor upstream of R-BY31006 is the parent haplogroup R-BY31008 that occurred about 245 BCE, or 2245 years ago. The descendants of that man are also found in England, Norway, and Scotland, in addition to our Hebert men in France.

That’s quite interesting.

But there’s something even more interesting.

Ancient DNA

Looking at Ancient Connections in Discover, I note that one of the Hebert Ancient Connections was found in France and has been placed into haplogroup R-Z31644. I wonder what the connection is. Let’s take a look at that haplogroup.

The TimeTree shows us that nine ancient DNA samples are found on different haplogroup branches of R-Z31644, of which only one is found in Metz, France, and the rest in the British Isles. It’s unclear exactly what this means. Only the French sample and three others in England and Ireland are found in the current era, meaning after 1 CE. This was clearly prior to the Battle of Hastings in 1066, after which an influx of French settled in England.

Eight ancient DNA results are found in England, but none share a common ancestor earlier than 4300 years ago. Notably, one English burial from about 2000-2300 years ago shares a common ancestor with the Metz, France remains about 4000 years ago. The eight English remains, and our Metz guy descend from a common ancestor about 4300 years ago.

Did Étienne’s ancestors descend from the ancient sample at Metz? Maybe the study provides more clues.

According to the study’s authors:

The Sablon district, which is located in the southern part of the city of Metz, was, during the Gallo-Roman period, a huge necropolis where both inhumations and cremations are found. Towards the end of the 19th century, the exploitation of the sandpits enabled the uncovering of sarcophagi (stone), cists (brick and tile), coffins (wood) and vats (lead).

These characterise the new burial practices developed during late Antiquity. [Spans from about the 3rd to the 6th or 7th centuries.]

The largest funerary space spans almost a kilometre, on either side of the via Scarponensis (portion of the Reims/Metz road).

The Sablon area can be compared to the Collatina necropolis close to Rome by its chaotic organisation, although at a different scale

Looking at a map of Metz helps put this in context.

It’s unclear exactly where along this route the burials were discovered beginning in the late 1800s. They extend for more than a kilometer on both sides of the road in the Sablon neighborhood of Metz.

The Sablon neighborhood extends from near the old city center along the main artery that crosses railroad tracks that appear to sever the original road into the city.

Does the history of Metz tell us who lived there and what was occurring during this time? Indeed, it does.

Metz is located at the confluence of the Moselle and Seille rivers, near the junction of France, Germany, and Luxembourg. The original inhabitants were Celtic. The town was known as the “city of Mediomatrici,” a fortified city of the tribe by the same name.

The Mediomatrici village evolved into a Gallo-Celtic city after Julius Caesar conquered the Gauls in 52 BCE.

Named Divodurum Mediomatricum by the Romans, present-day Metz was integrated into the Roman empire in the first century CE, after which it was colloquially referred to as the Holy Village.

The historic district has kept part of the Gallo-Roman city with Divodurum’s Cardo Maximus, then called Via Scarponensis. Today, this is Trinitaires, Taison, and Serpenoise streets in the old city center, and the Decumanus Maximus, which is En Fournirue and d’Estrées streets. The Roman Forum was located at the Cardo and Decumanus intersection and is the Saint-Jacques Square today, as shown below.

By Alice Volkwardsen at German Wikipedia, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=10681319

The ancient burial occurred between 432 and 551 CE, as calculated from a molar and was found in a very large Gallo-Roman necropolis, more than a kilometer long, located on both sides along the old Roman road.

This cityscape shows Divodurum Mediomatricum in the second century CE, capital of the Mediomatrici, ancestor city of present-day Metz. The original Roman amphitheater is shown at far left, and the living quarters are located within the city walls, protecting them from attack. A wonderful summary of archaeological findings can be found here.

Today the the Centre Pompidou-Metzocation is found at the site of the original large Roman amphitheater. This amphitheater held upwards of 25,000 people and was the largest and most consequential amphitheater outside of Rome.

Rome’s influence ended when the city was attacked, pillaged and burned by the Huns on April 7, 451, then passed into the hands of the Franks about 50 years later. By 511, Metz was the capital of the Kingdom of Austrasia.

How Does the Metz Burial Connect to England?

How do the dots between Metz and the British Isles connect, given that the common ancestor of our Metz burial and the British Isles burials has descendants scattered throughout the British Isles and in Metz?

The Celts first migrated to the British Isles about 1000 BCE, or about 3000 years ago, so this ancient French man and the other ancient burials in the British Isles make sense. Their common ancestor lived 4300 years ago in Europe. The closest common ancestor of our Metz man and any English burial occurred 4000 years ago, 1000 years before the earliest Celtic migrations across the English Channel.

This man from Metz lived 1500 or 1600 years ago and shares an ancestor with several ancient British men in addition to our Hebert line and was likely Celtic..

Of course, not every Celtic man left Europe. Many stayed and eventually integrated with whoever the next conquering army was. That ensured survival. Metz was a prize to be won, controlled over the centuries by many masters.

We don’t know if this specific Celtic man buried along the Gallo-Roman Road was a direct ancestor to our Hebert line, but if not, they were assuredly related and shared common ancestors. The descendants of haplogroup R-BY31008 are unquestionably the ancestors of our Hebert line.

Back to Étienne

Étienne’s Y-DNA has identified his ancestors as Celtic some 4000 years, or 200 generations ago.

More recently, his Y-DNA confirmed his connection to Antoine Hebert, and the church records of both of their descendants confirmed them as brothers.

Depositions given by Étienne’s grandchildren, spouses of grandchildren, great-grandchildren, nieces, and nephews confirm that Étienne was born in France, but, unfortunately, does not say where. This information alone debunked some of his parent candidates.

We find no suggestion of his parents in Acadia, although that’s not impossible. Many people died and never made it into existing records. The Hebert brothers likely arrived together as young men. Antoine may have married in France, as his wife’s surname is not found in Acadia. Of course, her father could have died and left no record. Étienne’s wife’s family lives next to the Heberts in Acadia, but we don’t know if Étienne and Marie Gaudet married in France or after arrival in Acadia.

How well did Étienne remember France? Did he look over his slice of countryside along the Riviere du Dauphine, with its dikes holding the tidal river at bay, and think of similar dikes constructed by his ancestors in France?

What about his parents?

Did they die, or did he sail away, knowing he and his brother would never see them or their siblings again?

Did their family shrink into tiny dots on the horizon, waving from the wharf, then disappear forever?

Did the brothers leave because they wanted to, or did they leave perhaps because they had no family left? Often, orphans had few options in their home country, and any opportunity was welcomed.

Did Étienne marry Marie Gaudet in Acadia, or did they marry someplace in France, then two Hebert boys immigrating to the new land with the Gaudet family?

In one way, we know so much – that Étienne matches an ancient Celtic burial in Metz who died about 1500 years ago, with whom he shared a common ancestor about 4000 years ago – yet we can’t identify Étienne’s parents. At least not today, but hope springs eternal. Two years ago, we didn’t know this.

Hopefully, one day, DNA testing for genealogy will be available to men in France. Our answers lie in Hebert men in some small French village, probably along a river that was once a highway of history.

Acknowledgments

I’m incredibly grateful to the Hebert men who have taken the Big Y-700 DNA test at FamilyTreeDNA, and to FamilyTreeDNA, because without those tests and the Discover tool that includes ancient DNA connections, we would never be able to peer beyond the mists of time into their deep ancestry.

As more men test and more academic studies and ancient DNA results are added to the Discover database, we’ll continue to learn more. The Big-Y DNA test is the gift that just keeps on giving.

_____________________________________________________________

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

Ancestry’s ThruLines Are a Hot Mess Right Now – But Here Are Some Great Alternatives

Right now, ThruLines at Ancestry is one hot mess.

Aside from the inherent frustration, especially over a holiday weekend when many people had planned to work on their genealogy, I’d like to say, “don’t panic.”

I don’t have any inside information about what’s going on at Ancestry, and I’ve attempted to make contact through their support page with no luck. They make talking to a person exceedingly difficult; plus, it’s a holiday weekend, and they are probably inundated.

Regardless, I have an idea of what is happening. Ancestry has been in the midst of recalculating “things,” perhaps in relation to their other changes, which I’ll write about separately in a few days.

In any event, Ancestry SURELY MUST KNOW there’s a significant problem because I imagine thousands of their customers are screaming right about now. Adding another voice won’t be helpful.

Symptoms

  • You may not have ThruLines at all.
  • If you do have ThruLines, don’t trust the information, or more to the point, don’t trust that it’s in any way complete.

I have two tests at Ancestry, both connected to different trees so that my matches and Thrulines are calculated separately for each test.

Test One

My first Ancestry test is connected to my primary tree. I’ve been amassing Thrulines cousins ever since the feature was released. I have hundreds of cousin matches descended from some of my more prolific ancestors.

Additionally, my sister’s grandchildren have tested, as have other close relatives who have connected their tests to their trees.

Today, those people are still showing on my match list, but are NOT showing as matches in ThruLines. None of them. Most of my ThruLines ancestors are showing zero matches, and the rest are only showing very few. Ancestors who had hundreds before now have 2, for example.

Here’s an example with my cousin, Erik.

My grandfather, William George Estes, shown in Erik’s tree, above, is his great-grandfather. Erik is my half first cousin, once removed, and we share 417 cM over 16 segments.

Yet, looking at my ThruLine for William George Estes, neither he nor my other cousins are shown as matches. Same for William George’s parents, and so forth.

ThruLines is VERY ill right now.

Test Two

My second DNA test at Ancestry is even worse. There are no ThruLines calculated, even though my DNA is tree-attached, and I had ThruLines previously.

I see this message now, and I can’t even begin to tell you how irritating this is – in part because it suggests the problem is my fault. It’s clearly not. My tree hasn’t changed one bit. I’m not alone, either. I’ve seen other people posting this same message.

And yes, if you’re thinking that there is absolutely no excuse for this – you’re right.

However, outrage isn’t good for us and won’t help – so let’s all do something else fun and productive instead.

Productive Genealogy Plans

Here are some productive suggestions.

At MyHeritage:

At FamilyTreeDNA:

  • Build your haplogroup pedigree chart by locating people through different companies descended from each ancestor in your tree through the appropriate line of descent, and see if they have or will take a Y-DNA or mtDNA test.
  • Tests are on sale right now, and there’s no subscription required at FamilyTreeDNA for anything.
  • Check Y-DNA and mtDNA tests to see if there are new matches and if you share a common ancestor.

At 23andMe:

  • Check for new matches and triangulation.
  • Check to see if 23andMe has added any of your new matches to your genetic tree.

Remember, the parental sides are typically accurate, but the exact placement may not be, and 23andMe deals poorly with half-relationships. It’s certainly still worth checking though, because 23andMe does a lot of heavy lifting for you.

DNAPainter

For me, the most productive thing to do this weekend would be to copy the segment information from new matches with whom I can identify common ancestors at FamilyTreeDNA, MyHeritage and 23andMe – the vendors who provide segment data – and paint those segments to DNAPainter.

Not only does DNAPainter allow me to consolidate my match data in one place, DNAPainter provides the ability for me to confirm ancestors through triangulation, and to assign unknown matches to ancestors as well.

As you can see, I’ve successfully assigned about 90% of my segments to an ancestor, meaning I’ve confirmed descent from that ancestor based on my autosomal matches’ descent from that same ancestor – preferably through another child. Will new matches propel me to 91%? I hope so.

What percentage can you or have you been able to assign?

If you need help getting started, or ideas, I’ve written about DNAPainter several times and provided a compiled resource library of those articles, here.

Have fun!!!

_____________________________________________________________

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

23andMe and GlaxoSmithKline Partnership Ends, Sparking Additional Layoffs

23andMe has been slimming down. In April, they announced they were cutting about 75 jobs in their therapeutics division, equating to about 9% of their workforce, and now they have cut another 71 employees in response to the end of the five-year GSK partnership.

GenomeWeb reported the earlier and most recent 23andMe layoffs, along with a 6% revenue dip, here. 23andMe is a publicly held company and reported a net loss of $104.6 million.

In 2018, 23andMe partnered with GSK, GlaxoSmithKline, a British drug company, to jointly develop drugs based on the genomic profiles of their customers who choose to participate in this type of research. You may have noticed that 23andMe asks a wide variety of questions that genealogy testing companies typically don’t, and they also report on health and traits.

At the onset of the partnership, GSK made a $300 million equity investment in 23andMe. If you need to cure insomnia, you can read the SEC filing, here.

The original partnership was to last four years and could be extended for an additional 5th year, which it was, landing another 50 million dollars in the 23andMe coffers.

According to the press release by 23andMe and this 2020 blog article, the partnership has been successful, adding more than 40 genetically validated drug discovery programs to the GSK portfolio, making me wonder why the partnership was not extended.

Customers

The 23andMe page for medical professionals states that they have more than 12 million customers worldwide.

23and Me has stated several times that about 80% of their customers opt-in to research, which means that their de-identified DNA sequences are made available to both 23andMe and their selected partners for research purposes.

Accordingly, about 8 million people have opted-in to research.

If you’re doing the math, that means that:

  • 23andMe received $29.17 for each of their 12 million customers

Viewed another way:

  • 23andMe received $43.75 for each of their 8 million customers who are opted-in for research

Attempting to Increase Revenues

In the past several months, 23andMe has attempted to staunch the corporate blood flow by:

Neither of these moves have been well-received by genealogists.

Purchase Price

23andMe sells two types of tests. One is for both health and ancestry, and the second is for ancestry, aka genealogy, only.

  • The 23andMe Health and Ancestry test is currently priced at $229. The yearly membership costs an additional $69, for a total of $298, but the membership is currently free during the first year. That’s a lot for an autosomal test that only buys you up to 5000 matches.
  • The 23andMe ancestry-only test is $119, but comes with restrictions, including the 1500 match limit.

For comparison purposes, this article shows how many matches I have at each vendor.

If you want more than 1500 matches, you MUST PURCHASE the Health and Ancestry test, not the lower-cost genealogy-only test, plus the additional membership.

This is a very difficult pill to swallow (pardon the pun.) None of the other DNA testing companies limit your matches or charge for matching, and their prices right now for their autosomal tests are as follows:

Subscription aka Membership

In order to entice customers into purchasing subscriptions, called memberships, 23andMe allows up to 5000 matches instead of 1500. 23andMe has also limited additional features, taking them away from their original customers and putting them behind the subscription paywall.

In October 2020, when they implemented subscriptions, called memberships, along with these changes, they reduced their customers’ original match limit from 2000 to 1500. Of course, to receive more matches, you could purchase a new test and subscribe. No thank you.

In another attempt to throttle services to earlier customers, there were initially no ethnicity updates for people in October of 2020 who had tested on V2, V3 or V4 chips, although following public outcry, they reversed that position for at least the V3 and V4 customers. No other DNA testing company excludes customers from ethnicity updates. 

One cannot perform other functions, such as sort or filter by haplogroup on their site, unless you purchase the Health and Ancestry test, plus a membership. You can, however, download your matches and sort/filter that way..

What’s Next for 23andMe?

23andMe says they are now actively pursuing new big pharma partners.

I hope they can find their way forward. While I don’t often find relevant matches at 23andMe anymore, and I have an issue with their subscription policy, especially removing features from existing customers, they do have a pool of 12 million-ish people. These matches certainly help many people, especially because their health customers probably won’t have tested elsewhere.

Having said that, I can’t help but wonder how many of those 12 million are the same person multiple times because they’ve had to purchase multiple tests. I’ve purchased three for myself over the years, and I’m not purchasing a fourth – but I digress.

  • 23andMe is still a good site for matching, especially for adoptees or people seeking unknown family members. You can also see how your matches match each other. You just never know where that critical match is going to pop up.
  • 23andMe provides painted ethnicity chromosome segments, along with FamilyTreeDNA. In my opinion, they are the top two vendors for ethnicity accuracy.
  • 23andMe and FamilyTreeDNA both report X-DNA matching, which can be very useful.
  • 23andMe is still the only vendor to construct a genetic tree – and yes – I know it’s not always completely accurate. Still, their tree creation is innovative and automated – based on how you match people and how they match each other. For adoptees and people seeking parents or grandparents, it’s essential because they start with nothing.
  • 23andMe doesn’t allow customers to upload or create a family tree, so you can’t view the family tree of your matches to find a common ancestor. You can include a link to your online family tree in your Enhanced Profile under Settings, but many people never see this, or aren’t genealogists.

Unfortunately, 23andMe is not focused on genealogy – at all. Their focus has always been medicine and health. From their perspective, genealogists are candidates to opt-in for genetic research, but that doesn’t mean genealogists can’t still benefit – even if we don’t opt-in, don’t purchase the more expensive $229 Health and Ancestry test, and don’t purchase their membership.

If you’re interested in more recent relatives, 23andMe is great because the 1500 match limit won’t impact you at all. Closer relatives will cluster at the top of your match list.

If you’re looking for matches that descend from more distant ancestors, you may find it worthwhile to purchase the more expensive test and the membership, at least for one year.

Filtering/Sorting Restriction Workaround 

While there’s no way around the 1500 or 5000 match limit, except that 23andMe won’t roll someone off of your match list if you’ve communicated with them, or tried to, there is a workaround for the restrictive filtering.

I check my matches periodically, sorting by the newest matched relatives. I also download my match list occasionally. I find it easier to review the information in spreadsheet format because I can search for surnames, locations, haplogroups and other information much more easily than online, especially given the restrictive filters.

However, when you download your match list, that information is downloaded as well.

Be sure to record notes on each match at 23andMe when you discover relevant information by clicking on the match and scrolling to the very bottom of the page. Your notes at 23andMe are downloaded onto the spreadsheet along with the rest of their information.

The instructions for downloading your match list, which is NOT the same as downloading your DNA file, are contained in this article. Give it a try!

_____________________________________________________________

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

Haplogroups: DNA SNPs Are Breadcrumbs – Follow Their Path

Recently a reader asked some great questions.

If Y-DNA is unchanged, then why isn’t the Y-DNA of every man the same today? And if it’s not the same, then how do we know that all men descend from Y-Adam? Are the scientists just guessing?

The scientists aren’t guessing, and the recent scientific innovations behind how this works is pretty amazing, so let’s unravel these questions one at a time.

The first thing we need to understand is how Y-DNA is inherited differently from autosomal DNA, and how it mutates.

First, a reminder that:

  • Y-DNA tests the Y chromosome passed from father to son in every generation, unmixed with any DNA of the mother. This article focuses on Y-DNA.
  • Mitochondrial DNA tests the mitochondria passed from mothers to all of their children, but is only passed on by the females, unmixed with the DNA of the father. This article also pertains to mitochondrial SNPS, but we will cover that more specifically later in another article.
  • Autosomal DNA is passed from both parents to their children. Each child inherits half of each parent’s autosomal DNA.

Let’s look at how this works.

Autosomal vs Y-DNA Inheritance

Click on image to enlarge

Autosomal DNA, shown here with the green (male) and pink (female) images, divides in each generation as it’s passed from the parent to their child. Each child inherits half of each parent’s autosomal DNA, meaning chromosomes 1-22. For this discussion, each descendant shown above is a male and has a Y chromosome.

This means that in the first generation, which would be the great-grandfather, about 700,000 locations of his green autosomal DNA are tested for genealogy purposes.

His female partner (pink) also has about 700,000 locations. During recombination, they each contribute about 350,000 SNPs (Single Nucleotide Polymorphisms) of autosomal DNA to their child. Their offspring then has a total of 700,000 SNPs, 350,000 green and 350,000 pink contributed by each parent.

This process is repeated for each child, whether male or female (with the exception of the X chromosome, which is beyond the scope of this article), but each child does not receive exactly the same half of their parents’ autosomal DNA. Recombination is random.

In the four generations shown above, the green autosomal DNA of generation one, the great-grandfather, has been divided and recombined three times. The original 700,000 locations of great-grandfather’s green DNA has now been whittled down to about 87,500 locations of his green DNA.

Y-DNA in the Same Generation

Looking now at the blue Y-DNA at left, the Y-DNA remains the same in each generation with the exception of one mutation approximately every two or three generations.

As you can see in the chart, in the exact same number of generations, the Y-DNA of each male, which he inherited from his father:

  • Never recombines with any DNA from the mother
  • Never divides and gets smaller in subsequent generations
  • Remains essentially unchanged in each generation

The key word here is “essentially.”

Y-DNA

The Y chromosome consists of about 59 million locations or SNPs of DNA. STR tests, Short Tandem Repeats, which are essentially insertions and deletions, test limited numbers of carefully curated markers selected for the fact that they mutate in a genealogically relevant timeframe. These markers are combined in panels of either 67 or 111 marker tests available for purchase at FamilyTreeDNA today, or historically 12, 25, 37, 67, and 111 marker panels. The STR test was the original Y-DNA test for genealogy and is still used as an introductory test or to see if a male matches a specific line, or not.

From the STR tests, in addition to matching, FamilyTreeDNA can reliably predict a relatively high-level haplogroup, or genetic clan, based on the frequency of the combinations of those marker values in specific STR locations.

SNPs are much more reliable than STRs, which tend to be comparatively unstable, mutating at an unreliable rate, and back mutating, which can be very disconcerting for genealogy. We need reliable consistency to be able to assign a male tester to a specific lineage with confidence. We can, however, find genealogically relevant matches that may be quite important, so I never disregard STR tests or testers. STR tests aren’t relevant for deeper history, nor can they reliably discern a specific lineage within a surname. SNP tests can and do.

The Big Y-700 SNP test gives us that and more, along with the earlier Big Y-500 test which scanned about 30 million locations. The Big Y-700 is a significant improvement; men can upgrade from the Big Y-500 or STR tests.

The Big Y-700 test scans about 50 million Y-DNA locations, known as the gold standard region, for all mutations. It reports 700 or more STR markers for matching, but more importantly, it scans for all SNP mutations in those 50 million locations.

All mutations are confirmed by at least five positive repeat scans and are then assigned a haplogroup name if found in two or more men.

Y-DNA Testing

If Y-DNA remained exactly the same, then the Y-DNA of men today would be entirely indistinguishable from each other – essentially all matching humankind’s first common ancestor. With no changes, Y-DNA would not be useful for genealogy. We need inherited mutations to be able to compare men and determine their level of relatedness to each other.

Fortunately, Y-DNA SNPs do mutate. Y-DNA is never divided or combined, so it stays essentially the same except for occasional mutations which are inherited by the following generations.

Using SNP markers scanned in the Big Y test, one new mutation happens on the average of every two or three generations. Of course, that means that sometimes there are no mutations for a few generations, and sometimes there are two mutations between father and son.

What this does, though, very effectively, is provide a trail of SNP mutations – breadcrumbs essentially – that we can use for matching, AND for tracking our mutations, which equate to ancestors, back in time.

Estes Male Breadcrumb Trail

I’ve tested several Estes men of known lineage, so I’m going to use this line as an example of how mutations act as breadcrumbs, allowing us to track our ancestors back in time and across the globe.

Multiple cousins in my Estes line have taken the Big Y-700 test.

My closest male cousin matches two other men on a unique mutation. That SNP has been named haplogroup R-ZS3700.

We know, based on our genealogy, that this mutation occurred in Virginia and is found in the sons of Moses Estes born in 1711.

How do we know that?

We know that because three of Moses’s descendants have tested and all three of those men have the same mutation, R-ZS3700, and none of the sons of Moses’s brothers have that mutation.

I’ve created a chart to illustrate the Estes pedigree chart, and the haplogroups assigned to those men. So, it’s a DNA pedigree chart too. This is exactly what the Big-Y DNA test does for us.

In the red-bordered block of testers, you can see the three men that all have R-ZS3700 (in red), and all are sons of Moses born in 1711. I have not typed the names of all the men in each generation because, for purposes of this illustration, names aren’t important. However, the concept and the fact that we have been able to connect them genealogically, either before or because of Y-DNA testing, is crucial.

Directly above Moses born in 1711, you can see his father Abraham born in 1647, along with Moses’ brothers at right and left; John, Richard, Sylvester, and Elisha whose descendants have taken the Big Y-700 test. Moses’s brothers’ descendants all have haplogroup R-BY490 (in blue), but NOT R-ZS3700. That tells us that the mutation responsible for R-ZS3700 happened between Abraham born in 1647, and Moses born in 1711. Otherwise, Moses’s brothers would have the mutation if his father had the mutation.

Moses’s descendants also have R-BY490, but it’s NOT the last SNP or haplogroup in their lineage. For Moses’s descendants, R-ZS3700 occurred after R-BY490.

You can see haplogroup R-BY490 boxed in blue.

We know that Moses and his father, Abraham, both have haplogroup R-BY490 because all of Abraham’s sons have this haplogroup. Additionally, we know that Abraham’s father, Silvester also had haplogroup R-BY490.

How do we know that?

Abraham’s brother, Richard’s descendant, tested and he has haplogroup R-BY490.

However, Silvester’s father, Robert born in 1555 did NOT have R-BY490, so it formed between him and his son, Silvester.

How do we know that?

Robert’s other son, Robert born in 1603 has a descendant who tested and has haplogroup R-BY482, but does NOT have R-BY490 or R-ZS3700.

All of the other Eates testers also have R-BY482, blocked in green, in addition to R-BY490, so we know that the mutation of R-BY490 developed between Robert born in 1555 and his son, Silvester born in 1600, because his other son’s descendant does not have it.

Looking at only the descent of the haplogroups, in order, we have

  • R-BY482 (green) found in Robert born in 1555 and all of his descendants.
  • R-BY490 (blue) found in Silvester born in 1600 and all of his descendants, but not his brother
  • R-ZS3700 (red) found in Moses born in 1711 and all of his descendants, but not his brothers

If we had Estes men who descend from the two additional documented generations upstream of Robert born in 1555, we might discover when R-BY482 occurred, but to date, we don’t have any additional testers from those lines.

Now that we understand the genesis of these three haplogroups in the Estes lineage, what else can we discover through our haplogroup breadcrumbs?

The Discover Reports

By entering the haplogroup in the Discover tool, either on the public page, here, or clicking on Discover on your personal page at FamilyTreeDNA if you’ve taken the Big-Y test, you will see several reports for your haplogroup.

I strongly suggest reviewing each category, because they cumulatively act as chapters to the book of your haplogroup story, but we’re going to skip directly to the breadcrumbs, which is called the Ancestral Path.

The Ancestral Path begins with your haplogroup in Line 1 then lists the first upstream or parent haplogroup in Line 2. In this case, the haplogroup I entered is R-ZS3700.

You can see the estimated age of the haplogroup, meaning when it formed, at about 1700 CE. Moses Estes who was born in 1711 is the first Estes man to carry haplogroup R-ZS3700, so that’s extremely close.

Line 2, R-BY490 occurred or was born about 1650, and we know that it actually occurred between Robert and Silvester born in 1600, so that’s close too.

Scanning down to Line 3, R-BY482 is estimated to have occurred about 1500 CE, and we know for sure it had occurred by 1555 when Robert was born.

We see the parent haplogroup of R-BY487 on Line 4, dating from about 750 CE. Of course, if more men test, it’s possible that more haplogroups will emerge between BY482 and BY487, forming a new branch. Given the time involved, those men wouldn’t be expected to carry the Estes surname, as surnames hadn’t yet been adopted in that timeframe.

Moving down to Line 9, we see R-ZP18 from 2250 BCE, or about 4250 years ago. Looking at the right column, there’s one ancient sample with that haplogroup. The location of ancient samples anchors haplogroups definitively in a particular location at a specific time.

Haplogroup by haplogroup, step by step, we can follow the breadcrumbs back in time to Y-Adam, the first homo sapiens male known to have descendants today, meaning he’s the MRCA, or most recent common ancestor for all men.

Neanderthals and Denisovans follow, but their Y-DNA is only available through ancient samples. They have no known direct male survivors, but someday, maybe someone will test and their Y-DNA will be found to descend from Neanderthals or Denisovans.

Now that we know when those haplogroups occurred, how did our ancestors get from Africa 232,000 years ago to Kent, England, in the 1400s? What path did they take?

The new Globetrekker tool answers that question.

The Breadcrumb Trail

In Globetrekker, each haplogroup’s location is placed by a combination of testers’ results, their identified earliest known ancestor (EKA) country and location, combined with ancient samples, climatic factors like glaciers and sea levels, and geographic features. You can read about Globetrekker here and here.

To view the Globetrekker tool, you must sign it to an account that has taken the Big Y test. It’s a tool exclusively provided for Big-Y testers.

You can click at the bottom of your Globetrekker map to play the animated video.

Beginning in Africa, our ancestors began their journey with Y-Adam, then migrated through the Near East, South Asia, East Asia, then west through central Asia into Europe. The Estes ancestors crossed the English Channel and migrated around what is now England before settling in Deal, on the east coast.

Clicking on any haplogroup provides a description of that haplogroup and how it was placed in that location.

Enabling the option for ancient DNA shows those locations as well, near the haplogroups they represent when the animation is playing.

Clicking on the shovel icon explains about that particular ancient DNA sample, what is known, and how it relates to the haplogroup it’s connected to by a dotted line on the map.

Pretty cool, huh!!

End to End

As you can see from this example, Big Y results are an end-to-end tool.

We can use the Big Y-700 haplogroups very successfully for recent genealogy – assigning testers to specific lines in a genealogy timeframe. Some haplogroups are so specific that, without additional information, we can place a man in his exact generation, or within a generation or two.

Not shown in my Estes pedigree chart is an adoptee with a different surname, of course. We know that he descends from Moses’s line because he carries haplogroup R-ZS3700, but we are still working on the more recent generations using autosomal DNA to connect him accurately.  If more of Moses’s descendants tested, we could probably place him very specifically. Without the Big Y-700 test, he wouldn’t know his biological surname or that he descends from Moses. That’s a HUGE breakthrough for him.

There’s more about the Estes line to learn, however.

If our Estes cousins tested their brothers, uncles or other Estes males in their line, they would likely receive a more refined haplogroup that’s relevant only to that line.

Using Big-Y test results, we can place men within a couple of generations and identify a common ancestor, even when all men within a haplogroup don’t know their genealogical lineage. Using those same test results, we can follow the breadcrumbs all 50 steps back in time more than 230,000 years to Y-Adam.

End to end, the Big-Y test coupled with breadcrumbs in Discover, Globetrekker, and other amazing tools is absolutely the most informative and powerful test available to male testers for their paternal line genealogy.

These amazing innovations tracking more than 50,000 haplogroups across the globe answer the original questions about how we know.

The more people who take or upgrade to the Big Y-700 test, the more haplogroup branches will be added, and the more refined the breadcrumbs, ages, and maps will become. In other words, there’s still more to learn.

Test if you haven’t, and check back often for new matches and breadcrumbs, aka updates.

_____________________________________________________________

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

  • com – Lots of wonderful genealogy research books
  • American Ancestors – Wonderful selection of genealogy books

Genealogy Research