Tamil Genealogy Records Search

Tamil genealogy is one of the record-rich branches of family history, and most beginners underestimate what actually survives. The records are scattered — across national archives on three continents, temple trusts, church parish registers, colonial revenue offices, and today's electoral rolls — but they exist, they're mostly accessible, and the combination often reaches deeper than families expect.

This guide walks the eight record layers that reach the deepest for Tamil families, in the order that usually helps. It names the specific archives worth contacting, the coverage TamizhConnect indexes for each, and the practical starting point when you know one thing and want to find the next.

Voter rolls: the living side of the family

Tamil Nadu's electoral rolls are the largest single genealogical dataset for the region — tens of millions of records, refreshed annually by the Election Commission, and covering every registered voter with an address that includes their village or ward. For a family whose primary line emigrated a hundred years ago, the extended kin who stayed behind almost always show up on the current voter roll.

TamizhConnect's voter search covers Tamil Nadu together with the Union Territory of Puducherry (which includes Karaikal, Yanam and Mahé). You can filter by village name, by surname, or by the father's or husband's name — the last of those is the "stayed-behind" pattern that works especially well for diaspora families where the emigrating ancestor's surname is known but their in-laws' names aren't.

The current-generation nature of the data is what makes it powerful: hitting a household with the ancestral surname at the ancestral village usually means a living cousin who can tell you what the archives can't.

Indenture archives: the emigrating side of the family

Between 1830 and 1920, roughly 1.5 million Indian labourers were shipped overseas under indenture — around a third from the Madras Presidency, which is where most Tamil diaspora ancestry originates. Every arriving labourer was recorded at the destination-side depot with their name, father's name, native district and often village, ship, arrival date, physical description, and estate assignment. Those records survive at unusually high coverage.

TamizhConnect ingests multiple indenture and slave-register collections that between them account for most Tamil-descent diaspora families:

III (from theiii.in) is a multi-destination collection covering South Africa, Fiji and Suriname arrivals — roughly 241,000 records spread across those three destinations; each record's true destination is captured in the record itself. GLDC (the Gandhi-Luthuli Documentation Centre at UKZN) covers Natal's arrivals — roughly 152,000 records for 1860–1911. GIRMITIYA_MADRAS covers the Madras-recruited slice of the Fiji girmit records, around 12,000 arrivals. SURINAME_BS is the Surinamese civil registration series from around 1902 forward — the largest single collection, about 905,000 records, primarily Bhojpuri but including the smaller Tamil-descent Surinamese population. SURINAME_SLAVEN is the Suriname slave registers 1830–1863 — around 161,000 records — for Afro-Surinamese lineages that pre-date the indenture era. TNA is the UK National Archives passenger-list series (BT 26 inbound, BT 27 outbound), which captures voyages passing through UK ports. And a family of destination-specific UK Colonial Office collections — TNA_MAURITIUS, TNA_TRINIDAD, TNA_GUYANA, TNA_JAMAICA, TNA_CEYLON, TNA_FIJI and several smaller ones — each covers one colony's Colonial Office indenture correspondence and depot papers.

For Mauritius specifically, TNA_MAURITIUS (the UK Colonial Office record layer) is the TamizhConnect-indexed source. The Aapravasi Ghat archive at the Mahatma Gandhi Institute in Moka is the deeper source we don't fully ingest and is worth an email enquiry for any specific Mauritian ancestor.

Working search: indenture search. A bare search (no country filter) is the widest option — it covers the everyday indenture providers and does NOT restrict by destination, so a common surname returns matches across every country. Adding a country filter (e.g. ?country=mauritius) is a narrowing operation, not a widening one: it restricts the query to that country's mapped providers (for Mauritius that's GIRMITIYA_MADRAS, III, TNA_MAURITIUS), which is faster and more relevant when you already know the destination but excludes the general UK Passenger Lists (TNA) and any other country's records. So use the country filter when you know the destination; drop it and search bare when you don't. For the Surinamese SURINAME_BS and SURINAME_SLAVEN collections specifically, ?country=suriname is the direct route into that dataset. For the mechanics of working through results, see Trace your indenture roots. For anyone whose family story anchors on "we came from Madras," start with 'Madras' was a port — your village is somewhere else, which is the single biggest knowledge gap for diaspora Tamil ancestry.

Church, baptism and marriage registers

Tamil Christian families — Roman Catholic, Church of South India, Anglican, Danish Lutheran — often have the deepest continuous records of any Tamil community. Some parish registers reach the 1600s, especially in Nagapattinam, Tharangambadi (Tranquebar), and coastal Ramnad. The Portuguese missionary presence on the Fisher Coast from the sixteenth century, the Danish Tranquebar mission from 1706, and the CSI's Anglican-Methodist inheritance all left dense sacramental archives that never got fully consolidated into any national record.

The Roman Catholic Archdiocese of Madras-Mylapore holds the largest Tamil-language sacramental collection. The Tranquebar mission archive has been digitised at the Franckesche Stiftungen in Halle, Germany, and includes baptism and marriage registers going back to the earliest decades of the mission. Most other parish registers are still held on-site by the individual parish, and access is through the parish priest.

For a Tamil Christian family, the baptism record — with names of parents and godparents — often reaches earlier than any secular register. Marriage records name both families; burial records typically capture age at death, and sometimes cause. It's the layer that makes deep Tamil Christian lineages traceable back four to six generations without any special research.

Temple registers and kula deivam records

Tamil village temples maintain lineage records — the paramparai — through the temple trust (koil manram) and the officiating priests. The kula deivam (family deity) affiliation ties every Tamil family to a specific ancestral temple, usually located at the family's original village.

For genealogy, the value is anchoring. When two similarly-named families both plausibly match an indenture record, the deity is a strong tie-breaker — provided you have the specific epithet and temple, not just the broad category name. Mariamman, Murugan and Kaliamman are worshipped across thousands of families and are not, on their own, disambiguating. But "the Murugan at Palani" or "the Mariamman of Anakkarai village" narrows to a specific tradition and a specific village, which is where the tie-break works. When oral history says "our village is somewhere in Trichy district" and the archive can't confirm, the deity + specific temple combination often names the village.

TamizhConnect's kula deivam finder is a searchable directory of deity-to-temple-to-district mappings. From there, the temple trust usually holds the paramparai records themselves; many trusts now list WhatsApp numbers publicly. The temple records guide covers the practical mechanics of working with temple archives — how to request lineage records, what to bring with you, what the priest typically knows without needing to check any book.

Land and revenue records

The British Madras Presidency kept detailed jamabandi (revenue settlement) and patta (land title) records from the early 1800s. These name every landholder in a village, their crop, their annual tax assessment, and often their neighbours — which is how a family historian recovers kin relationships that no vital record captured. Adjacent-plot landholders in a nineteenth-century patta register are almost always related to each other.

The Tamil Nadu State Archives in Egmore, Chennai holds the surviving colonial land registers. They are not systematically digitised, and retrieval is on-site through a paid research request. For a family with any landholding history in Tamil Nadu, this is the layer that closes the eighteenth-century gap — nothing else reaches earlier. The heritage ambassadors program coordinates on-site research at Egmore for families outside India.

Immigration and passenger lists

Indenture records are the departure side. The arrival-side records at destination countries are a complementary layer that often names people missing from the outbound registers.

For UK arrivals, TNA's BT 26 series holds inward-passenger lists from 1878 forward; BT 27 holds outward. For South African arrivals, the Cape Town Archives Repository and the Pietermaritzburg Archives hold arrival ledgers from 1860 onward. Trinidad's arrival registers are at the National Archives in Port of Spain; Guyana's are split between Georgetown (post-1945 survivors) and Kew (Colonial Office duplicates). Fiji's arrivals are at the National Archives of Fiji in Suva.

Cross-referencing an outbound Indian record with an inbound destination-country record is the strongest single-piece evidence method in Tamil diaspora genealogy. Three independent archives naming the same person on the same ship removes almost all doubt.

Newspapers, obituaries and colonial gazettes

Under-used but powerful. The Madras Mail, The Hindu (from 1878), the Asylum Press Almanack series, and diaspora papers like the Trinidad Guardian, Fiji Times, and Post (South Africa) all published birth-marriage-death notices, obituaries, and biographical sketches for Tamil families. For exact dates — which vital records often round to the year — and for cause-of-death and spouse-family detail, newspaper notices are frequently the primary source.

Most Tamil newspaper obituary research still runs through the individual paper's own archive. The Asylum Press Almanack 1919 corpus and other Madras Presidency directories are searchable at the Internet Archive; The Hindu's pre-1950 archive is on microfilm at the Roja Muthiah Research Library in Chennai. For diaspora papers, the destination-country national libraries (Trinidad's National Library, Fiji's, and South Africa's KwaZulu-Natal Society library for the Post) hold digitised runs of most twentieth-century Tamil community papers.

DNA testing

Autosomal DNA testing (23andMe, AncestryDNA, MyHeritage) gives you admixture percentages — how much of your DNA clusters with Tamil, versus North Indian, Sinhalese, Adivasi, or European reference populations — and matches you with distant genetic cousins who have also tested. Specialised Y-STR and mtDNA tests trace the deep paternal or maternal line, though they answer different questions from autosomal.

For Tamil families specifically, the weakness is reference-database size. Tamil populations are underrepresented in the commercial databases compared to European populations, so results often cluster as "South Indian" rather than distinguishing Tamil, Telugu, or Malayalam origins precisely. Distant-cousin matching improves as more Tamil families test, but the base rate is still lower than for European ancestry.

DNA is best treated as a confirming or ruling-out layer rather than a primary source. When records and DNA agree, the tree is unusually well-anchored. When they disagree, records usually win — DNA cousinship matching has enough noise at the third-cousin-and-beyond distance that a genuine paper trail should outweigh a probabilistic genetic match.

Combining records: the three-source rule

No single record proves a lineage. The evidence bar for a confirmed Tamil ancestor is three independent sources naming the same individual with consistent attributes.

For a diaspora family, that usually looks like: (1) an indenture arrival record naming the ancestor, their father, their village, and their ship; (2) a temple record from the village's main temple confirming the family's kula deivam and one or two named generations of the same lineage; and (3) either an oral history from a village elder that names the emigrating ancestor by name, or a Tamil Nadu-side land record (patta) naming the ancestor or their sibling as a landholder in the same village. A present-day voter-roll match for a household with the same surname in the same village is supporting evidence — it points to potential living cousins — but doesn't count as one of the three "same-individual" sources because the voter record names a descendant, not the emigrating ancestor. Any single one of the three primary sources could be a false positive; the combination is what reads as confirmed.

For a Tamil Nadu-resident family researching diaspora branches, the triangle inverts: a voter record for the household, a patta register for the ancestral landholding, and an indenture record for the branch that left. Same three-source discipline, different anchor points.

Where to start based on what you already know

If you already have a village name but no ancestor names, find Tamil ancestors by village name is the reverse-lookup mechanic — search the voter roll for that village first, then check indenture records for people whose place of origin matches, then triangulate with temple records.

If you have an ancestor's name but no village, the practical route depends on the era. For diaspora ancestors (1830–1920), start with the indenture search — the village of origin is captured on most records. For Tamil Nadu-resident families where the village is unknown, oral history usually gets you to a district within an hour, and voter-roll surname clustering does the rest.

If your evidence is a diaspora ancestor and you don't know their Tamil Nadu origin, trace your indenture roots walks the search from a family-name-plus-destination-country starting point through to a specific arrival record.

If your evidence is a DNA match to Tamil Nadu but no specific family lore, the pattern is: take the district or region the match clusters in, run voter-roll searches for the matched surname in that district, and see whether the surname clusters at particular villages. DNA matches don't name villages, but voter data lets you map a surname distribution across Tamil Nadu at village granularity.

The two-search rule

For any Tamil genealogy question, the answer usually appears within two of the eight archives above — rarely just one, almost never more than three. If you've searched two and drawn blank, the problem is almost always spelling variation, not that the ancestor doesn't exist. Try the phonetic variants first (Muthusamy / Muthuswamy / Mootoosamy / Muddoosami / Mudduswamy — all the same name), then broaden to the colonial-era district (British-era North Arcot is today's Vellore, Ranipet, Tirupathur and Tiruvannamalai all together), then try the sibling archive (III + GLDC for South-facing families; GIRMITIYA_MADRAS + TNA for Pacific-facing families).

Most searches that feel stuck are one spelling drift away from a match.

Next steps

Pick one record type from the eight above based on what you already know. Run the same query against a second type to triangulate. Then build an evidence-notes doc so future-you doesn't repeat searches you've already made — a plain text file with search date, terms tried, and result is enough.

Ready to search? Voter rolls · indenture archives · kula deivam finder.