A match list can look like a map of your family, but it is really a list of questions. Each DNA match says that you and another person share a stretch of DNA, and that somewhere in your two trees there may be a common ancestor. The work of turning that into a named ancestor happens in the records. This guide gives a step-by-step method for using DNA matches with Austrian records, from sorting the list to opening the parish book.
What a match tells you, and what it does not
A match tells you that two people are probably related and gives a rough idea of how closely, based on how much DNA they share. It does not tell you which ancestor you share, which side of the family the link is on, or whether the relationship comes through a surname you recognise. Matches from the same company are comparable because they are measured the same way. Matches across companies are not, which is one reason to check how your data can move, as our post on transferring DNA data explains.
A five-step workflow
- Start with the closest matches. Identify who they are and place them in your tree. Known relatives anchor the list.
- Sort the rest into branches. Use shared matches, meaning people who match both you and a known relative, to group matches by side of the family.
- Look for the common thread. Within a group, compare trees for shared surnames, places and dates. Note the Austrian places that recur.
- Form a hypothesis. For example, that a group of matches descends from a family in a particular parish.
- Test it in the records. Open the parish books, civil records or archive files and check whether the candidate family exists and links to your tree.
Most of the effort is in steps three to five, and this is where Austrian research has an advantage: parish books are organised by place and often reach back for centuries, so a hypothesis about a parish can be tested directly. Our Matricula Online guide explains how to search the volumes, and the Matricula site shows which parishes are online.
Reading matches’ trees with an Austrian eye
- Names vary. A match may spell a surname as Swoboda where your records say Svoboda. See spelling variants and Slavic and Hungarian names.
- Places change names. A village may be in a different country now, so check the crown lands guide for the historical name.
- Women’s names change. A match’s tree may list a great-grandmother by her married name, and our post on maiden names explains how to find her birth family.
- Farm names can disguise a surname. A match whose line is recorded under a farm name may belong to your family under another name. See farm names.
- Trees can be wrong. A match’s tree is a lead, not a source. Check against records.
Small matches and distant relatives
Small shared segments are common and often unreliable for identifying a specific ancestor, because they can arise by chance or from distant shared ancestry. Closer matches, with larger shared segments, are more useful. If you work with small matches, look for clusters: several people who match each other and you, with trees that converge on the same place, are more convincing than one isolated match. In regions where families stayed in the same valley for generations, distant cousins can appear in many branches of the tree, so expect some matches to link through more than one line.
Invented example: Imagine an invented researcher, Paul, whose Austrian line stops at a great-grandfather born around 1865 in a Salzburg village. A cluster of six matches shares a common family from a neighbouring village in their trees. Paul’s hypothesis is that the great-grandfather’s mother came from that village. He searches the neighbouring parish’s baptism book for a woman with the right surname and age, finds a candidate and then checks the great-grandfather’s own baptism entry, which names the mother with a maiden name that matches. The DNA cluster suggested the village and the record confirmed it. This is a made-up case.
Using records to extend a match
Once you have a hypothesis, use the strongest available records. For births, marriages and deaths from 1938 and 1939, civil records can be requested, as our post on ordering civil records explains. For earlier periods, church books are the main source, and our Austrian genealogy guide shows where to start. For families that moved to Vienna, the residence cards may name the village of origin, and the Vienna guide explains them.
When the match list is quiet
Sometimes a list yields no clear cluster. That is not a failure. Match lists grow as relatives and strangers test, so check back periodically. In the meantime, work on the records side. Extend your own tree sideways, including siblings and their descendants, because those descendants may be the cousins who test. A fuller tree makes it easier to recognise a link when it appears. Record any shared places and surnames across your matches, and look for patterns you did not notice before.
Contacting matches
Many matches never reply, and that is normal. When you write, be brief, say which ancestor and place you are researching, and ask whether the person has information on a specific family. Do not share the DNA details of other relatives without their consent, and respect that some matches may not know about family secrets. Treat matches as people and not as data, and be careful with sensitive discoveries. Our post on privacy and company changes covers the data side.
Keeping a match log
A simple log saves hours. For each important match, record the name, the amount of shared DNA, the company, the date, the ancestor couple you think you share and the evidence. When you later find a record, note whether it supports or contradicts the hypothesis. The starter kit includes a template. Without a log, it is easy to revisit the same match many times without remembering what you learned.
Where to go next
Read the pillar on choosing a DNA test if you have not tested yet, and what DNA can and cannot show for the limits. MyHeritage and other platforms are compared on the genealogy records hub.
Company tools and policies change, so check each service’s current features before you rely on a method.
