South African Indenture Records

The Gandhi-Luthuli Documentation Centre (GLDC) archive is the most complete source of Indian indenture records for South African families of Tamil, Telugu, Bhojpuri, or Hindi descent. Held at the University of KwaZulu-Natal in Durban, the archive covers roughly 152,000 named individuals who arrived in Natal on 384 ships between November 1860 and July 1911. If your family's oral history reaches back to indenture, the ancestor is almost certainly in this archive — the challenge is finding them.

The full GLDC dataset is searchable on TamizhConnect's indenture search with the Natal filter. Search by given name and native place, never by surname alone — colonial clerks transliterated Tamil names inconsistently, and surname is usually the least reliable field. Once you have a hit, cross-reference the ancestor's Tamil Nadu village on the voter roll to find surviving relatives.

---

What each GLDC record contains

Every indentured arrival was assigned a colonial number (usually 5–6 digits) on arrival at Port Natal. The register entry for that person contains the fields below.

| Field | What it captures | How reliable it is | |---|---|---| | Colonial number | Sequential ID assigned at Port Natal on arrival | Perfectly reliable, unique | | Ship name | Vessel that carried the ancestor | Very reliable — cross-check against ship-arrival lists | | Arrival date | Port Natal disembarkation date | Very reliable | | Given name | First name as spoken to the clerk | Reliable in meaning, unreliable in spelling | | Father's name | Ancestor's father's first name | Reliable — often the strongest cross-reference clue | | Age at arrival | Age in years | Rough — some ancestors under-reported to appear over 18 | | Native place | Village and district in India | Reliable for district; village name may be transliterated | | Caste | Caste as recorded by the clerk | Recorded per the ancestor's own statement; variable accuracy | | Religion | Hindu / Muslim / Christian | Reliable for the three main categories | | Height | Physical description in feet + inches | Marginal historical value — mostly used for identification then | | Distinguishing marks | Scars, tattoos, deformities | Used for identification; sometimes reveals occupation clues | | Estate assigned | The Natal sugar estate / mine / railway | Very reliable — the first work assignment | | Re-indenture status | Whether the ancestor signed a further 5-year term | Reliable — often revealed by a separate register entry |

The three-anchor rule (for building a candidate list)

Because colonial-era transliteration was inconsistent, matching a modern family memory to a GLDC record works best when three anchors align approximately:

1. Given name (allowing spelling variants) OR father's name
2. Native place (district-level match; village-level exact match is a bonus)
3. Arrival year ±3 years OR specific ship

If two of these three align across your search hits, you have a strong candidate match — a research lead worth investigating further, not a confirmed identification. Before treating a candidate as your definitive ancestor, corroborate with independent evidence: sibling arrivals on the same ship, matching religion / community designation, family oral history of the same estate assignment, or later Natal civil records naming the same person.

A common mistake: treating a GLDC hit as proof. Shared given name, village, and arrival year make a record a candidate for your family, not confirmation. Colonial-era clerks recorded many similarly-named arrivals from adjacent Tamil Nadu villages, and modern family surnames drifted from the original arrival name over 5-6 generations. Confirm through corroborating records — siblings, estate books, civil registration, church records — before adding an archive record to your family tree as a confirmed ancestor.

And don't match on surname alone. In colonial Natal most indentured Tamils were recorded without a family surname, or with a father's given name in the surname field. Modern family surnames often emerged after settlement, based on estate assignment, occupation, or an arbitrary anglicisation. Surname-only matching produces both false negatives (real ancestors filtered out) and false positives (wrong ancestors surfaced).

---

Step-by-step search workflow

Step 1: Gather what you know

Fill in as much of this as possible before opening any archive:

| Field | Sources for the answer | |---|---| | Great-grandfather / great-great-grandfather's given name | Elder testimony, family Bible or Puja register, gravestone | | Ship name (if remembered) | Family oral history — often preserved as "we came on the Truro" or similar | | Approximate arrival decade | Estate history + generation math (roughly 1860s–1900s for great-great-grandparent generation) | | Tamil Nadu district or region | Elder testimony — even a fragment ("from Tirunelveli side" or "somewhere near Ramnad") | | Sugar estate the family first worked on | Family oral history + KZN municipal records | | Religion of the arrival generation | Family religious continuity — usually consistent for 3+ generations | | Any Tamil first name still in family memory | Grandfather / great-grandfather / great-great-grandfather's given name |

Step 2: Open the search

Go to TamizhConnect indenture search and:

1. Filter to Natal / GLDC provider
2. Enter the ancestor's given name (try 3 spelling variants — e.g., Ramaswamy / Ramaswami / Ramasamy)
3. Add the district or native place filter if you have it
4. Optionally add the arrival year range (±3–5 years from the estimated generation)

Step 3: Read the results

For each candidate the TamizhConnect indenture search surfaces, you'll see the fields it exposes in the results view — typically given name, father's name, native place, ship, arrival date, age, and (where available) estate assignment. Compare each against what you know:

• Does the father's name match your family's memory of the great-great-grandfather's father?
• Does the native place match (district level at minimum, village level ideally)?
• Does the ship + arrival date align with family oral history about when the family arrived?
• Is the age plausible for the generation you're tracing?
• Where estate is shown, does it match known family work history in Natal?

Additional fields exist in the underlying GLDC register — caste, religion, height, distinguishing marks, re-indenture status — but these may not all appear in the search UI results. For those extra fields, request the full register scan directly from GLDC (contact docs@ukzn.ac.za with the colonial number surfaced in your TamizhConnect result).

If you get 5+ candidate rows, tighten by adding filters or a narrower spelling variant. If you get 0, loosen by removing filters one at a time and trying new spelling variants.

Step 4: Extract the Tamil Nadu village

Once you have the winning GLDC record, note the native place field. It usually contains:

• A village name (may be transliterated)
• A district name (usually reliable)
• Occasionally a taluk / firka / parish designation

The village name may need a quick lookup — colonial-era Tamil village names sometimes changed post-Independence (Chingleput → Chengalpattu, Trichinopoly → Tiruchirappalli, Palayamkottai spelling variants, etc.).

Step 5: Cross-reference to the Tamil Nadu voter roll

This is the closing move — turn the historical record into modern relatives.

| Tamil-side action | What it does | |---|---| | Search the ancestor's village on TamizhConnect voter roll | 50M+ current voters indexed — Tamil families often stay in the same village for 5+ generations | | Cross-reference father's name / caste / community | Narrows village hits to the specific family cluster | | Try the same search on nearby villages | If exact-village search fails, families sometimes shifted within a district over the century | | Village browse | See who else has traced back to the same place | | Kula Deivam finder | For Hindu families, the pre-migration village deity often matches |

Step 6: Save the record and possible relatives, then annotate

Save your candidate GLDC record from the indenture search result view — that action attaches the archive ancestor to your TamizhConnect family tree. Any voter-roll matches you save from the voter search go on your tree as possible relatives (they're not automatically confirmed kin — you evaluate each one against additional evidence). On the ancestor's profile in your family tree, add a note capturing the archive references you'll want to preserve: colonial number, ship arrival date, estate assignment, and any GLDC register volume/page reference from the source scan. This is what makes the discovery permanent and shareable with other family members — with the ambiguity of "candidate" vs "confirmed" visible in the notes so future family researchers can pick up where you left off.

---

Search tips for the tricky cases

| Problem | Workaround | |---|---| | Your ancestor's name doesn't appear at all | Try father's name in the given-name field; ancestors were sometimes recorded as "Rama son of Muthu" and Muthu shows up separately | | Multiple ancestors with the same given name in the same village | Use age + arrival year to discriminate; check re-indenture records for the same person's later entries | | Native place field is illegible / blank | Fall back to ship + estate + arrival year; then browse voter roll by district to find plausible village candidates | | Colonial clerk misheard the village name | Try phonetic variants; also try nearby villages in the same district (villages often shift by 5–10 km over the century) | | Ancestor was Tamil Christian and used a Christian first name at arrival | Search both the Christian name (David, Peter) and the Tamil pre-conversion name if known (Muthusamy, Ramasamy) | | Ancestor was Tamil Muslim with an Arabic name | Search by the Arabic given name (Muhammad, Abdul, Ismail); father's name is usually also Arabic |

---

What GLDC records will NOT tell you

• The specific street or house in the Tamil Nadu village. Only village-level.
• The estate work history after arrival — that's in separate estate labour books held at KZN archives.
• Marriages, deaths, or births in Natal. Those are in KZN civil registration (post-1876) held at Home Affairs, or in Anglican / Roman Catholic diocesan registers.
• The reason for indenture. The GLDC record doesn't say WHY the ancestor left India (famine, indebtedness, family conflict, adventure). That's the domain of oral history.
• Post-1911 arrivals. Indenture ended in 1911. Later Indian arrivals to Natal (free traders, passengers, mission staff) are in different records.

---

Frequently asked questions

What is the difference between the GLDC and the KZN Archives Repository?

Gandhi-Luthuli Documentation Centre (GLDC) at UKZN Durban holds the digitised indenture registers — the arrival records specifically. KZN Archives Repository in Pietermaritzburg holds the wider colonial state archive: estate labour books, magistrates' court records, immigration correspondence, hospital records, and post-indenture civil papers. For the arrival-and-village question, start with GLDC. For estate history, marriages, deaths, and later civil records, use PMB.

How is TamizhConnect's indenture search different from searching GLDC directly?

The GLDC has its own reader-services search, but it requires (a) travel or writing to Durban, and (b) knowing the ancestor's colonial number or approximate ship. TamizhConnect ingests the full GLDC dataset AND cross-links it with the Tamil Nadu voter roll and village browse — so once you find the ancestor's village on the GLDC side, the voter cross-reference is one click. That combined workflow is the key advantage.

My ancestor came on the second ship, the Belvedere — but I heard it was from Calcutta, not Madras. Was my ancestor even Tamil?

The Belvedere sailed from Calcutta with predominantly Bhojpuri / Hindi speakers, not Tamil. If your family's oral history genuinely places you on the Belvedere but you also identify as Tamil, likely explanations: (a) your Tamil identity comes through the OTHER side of the family who arrived on a different ship, (b) family memory has mixed up the specific ship over time, or (c) your ancestor was a Tamil family who happened to embark from Calcutta (rare but not impossible). Check the GLDC record for language and native place — if it says Madras Presidency, ship name may be misremembered.

My family has always said we're "Tamil Christian" and came on the Truro. Is that plausible?

Yes, plausible but check. The Truro (Nov 1860, first ship from Madras) had 342 passengers — mostly Hindu Tamils, with some Tamil Christians and Muslims. If your family has strong continuous Tamil Christian identity going back 5+ generations, an ancestor on the Truro is possible. Confirm by searching the GLDC Truro passenger list for the ancestor's given name + Christian religion designation. If not on the Truro, try the Umvoti (1880s), British Peer (1880s), and other Madras ships.

Can I access GLDC records if I don't live in South Africa?

Yes. Two routes: (a) TamizhConnect's indenture search offers the digitised dataset online, searchable from anywhere. (b) The GLDC's own reader services accept remote inquiries — write to docs@ukzn.ac.za with the ancestor's approximate details, and they'll do a paid lookup and send the register scan.

My ancestor's caste is listed differently in the GLDC record than what my family says today. What does that mean?

Caste designations were recorded per the ancestor's own statement at Port Natal — often in a hurried, chaotic arrival process. Some ancestors under-reported their caste (to avoid perceived stigma), some over-reported (to claim status), some had regional caste names that colonial clerks misheard. Modern family caste identity may reflect post-arrival community reorganisation in Natal. Don't treat the GLDC caste field as definitive; treat it as one data point among many.

Do the GLDC records include women and children?

Yes. Roughly 30% of indentured arrivals were women (below the 40% required by the "40 women per 100 men" colonial regulation, but still substantial). Children who arrived with parents also have their own numbered register entries. Search for female ancestors by given name + native place the same way as men.

---

Where to go next

• South African Tamil Ancestry: The Complete Guide — the overview and historical context for the archive covered here.
• Tamil Surnames in South Africa — surname patterns (Naidoo, Reddy, Chetty, Naicker, Pillai, Padayachi) and how they map to Tamil Nadu origins.
• How to Trace 10 Generations of South African Tamil Ancestry — the deeper multi-generational method.
• TamizhConnect indenture search — search the 152K GLDC records now.
• TamizhConnect voter search — cross-reference the ancestor's village to modern relatives.

The GLDC archive is the single most complete named-individual record you'll ever find for a South African Tamil ancestor. Learn to read it and everything else — village, family, cousins in Tamil Nadu — becomes reachable.