Susanna, the wife of John Johnson, was born about 1607. (She was recorded as aged 24 as a passenger in 1635). Her last name, parents and place of birth are unknown. (See Research Notes ) A 19th-century genealogy claims that "[t]he Johnsons who settled here [Andover], and at Charlestown and Woburn, were emigrants from Hern Hill in Kent County England."[1] Their first two children were baptized in Strood, Kent, some 30 miles from Hernhill, giving some credence to their natal places being Kent.[2]
Immigration
13 July 1635 John Johnson, 26, Suzan Johnson, 24 [b. c. 1611], Eliza: Johnson, 2, and Tho: Johnson 18 months enrolled at London as passengers aboard the James bound for New England,[3]
The family first settled in Agawam (Ipswich), Massachusetts, and then removed to Andover, Massachusetts, by 1657.[2]
Children
Children: Note that Anderson mentions that there is proof that Elizabeth, Thomas and Hannah are children of this couple, but the others are based on the fact that John was the only available Johnson in Andover to be their father.[2]
Elizabeth bp Strood, Kent 1 Nov 1631; no further record after passenger list
Thomas, bp Strood, Kent, 28 Jul 1633; m Andover 5 Jul 1657 Mary Holt, dau of Nicholas Holt
Mary, b say 1638; m Andover 29 December 1660 Ephraim Davis
Stephen, b abt 1640; m Andover 5 Nov 1661 Elizabeth Dane.
Hannah, b say 1642; m Andover 24 Jun 1662 Samuel Hutchins[on]
Timothy Johnson, b abt 1644; m Andover 15 Dec 1674 Rebecca Aslebee
Susanna Johnson, b say 1648; m Andover 26 Feb 1667/8? Walter Wright
Joanna Johnson, b say 1651; m Andover 23 Oct 1671 Moses Haggett
William Johnson, b say 1653; m Andover 23 May 1678 Sarah Lovejoy
Disputed Last Names: A couple of last names at birth have been claimed for Susan. As there is no reliable evidence supporting either, she is currently Unknown.
Susanna Asherst:[6][7] A Susan Asherst m. 29 Apr 1631, John Power in Faversham, Kent, England[8] suggests that there was an Asherst family in Kent, but provides no association to the Susan who married John Johnson.
Claimed birth date: FindAGrave claims without source that John Johnsons wife was Susanna "Munter" was born 8 Mar 1611 in Herne Hill, Kent, England.[9]
Sources
↑ Bailey, Sarah Loring. Historical sketches of Andover, (comprising the present towns of North Andover and Andover).(Boston: Houghton, 1880) p. 116
↑ 2.02.12.2 Great Migration 1634-1635, I-L. (Online database. AmericanAncestors.org. New England Historic Genealogical Society, 2008.) Originally published as: The Great Migration, Immigrants to New England, 1634-1635, Volume IV, I-L, by Robert Charles Anderson. Boston: New England Historic Genealogical Society, 2005. Link at AmericanAncestors ($)
↑ Hotten, John Camden (editor). The Original Lists of Persons of Quality: Emigrants, Religious Exiles, Political Rebels, Serving Men Sold for a Term of Years, Apprentices, Children Stolen, Maidens Pressed, and Others, who Went from Great Britain to the American Plantations, 1600-1700. (London: John Camden Hotten, 1874.) p. 108
↑ 9.09.1 Find a Grave, database and images (https://www.findagrave.com/memorial/36810469/susanna-johnson: accessed 20 September 2023), memorial page for Susanna Munter Johnson (8 Mar 1611–12 Sep 1683), Find a Grave Memorial ID 36810469, citing Old North Parish Burying Ground, North Andover, Essex County, Massachusetts, USA; Maintained by V. Nareen Lake (contributor 46613568). Find A Grave: Memorial #36810469 A memorial stone erected later in the Old North Parish Burying Ground Andover
If we don't know her parents or surname, shouldn't the specific birth date and birthplace be deleted? ("Great Migration" says "about 1611" with no suggested birthplace.)
Since there is no source for her maiden name, it needs to be changed to Unknown and project protected. To aid others in finding the profile, the names "Asherst" and "Munter" will be placed in OLN - then the explanation that neither one of these are accurate, and that her maiden name is unknown.
I'm going to move forward, since there is so much discussion already (below).
From reading the comments, it looks like there is no source for the LNAB of Asherst, or the specific birth date 8 Mar 1611. I see FindAGrave proposes her last name is Munter. Especially since there are two unproven names, can her LNAB be updated to Unknown and then Project Protect the profile?
Michelle, I understand your point. And this has been discussed many times in multiple venues. But the policy (whether there's consensus about it or not) is to use Unknown as LNAB in these cases.
We've used "Other Last Names" for unsourced surnames to hopefully deter creation of duplicates. Sometimes it works; sometimes it doesn't.
The previous merge with Unknown-214161 went in the wrong direction because the Unknown profile wasn't project protected; if it had been, it would have controlled the direction of the merge.
The problem with Unknown as a last name on Wikitree - if theres a LNAB thats a possibility - profiles will be undoubtedly be created with the possible LNAB and these will need to be merged with the Unknown LNAB profile, even if the Unknown LNAB is a protected profile.
Its less time consuming to leave the possible LNAB and make a note in the Biography Space about the Unknown LNAB and parentage to stave off duplicate profiles for this person.
I had a profile for this person that was UNKNOWN-214161 - but it was decided it was best to merge it with the current profile.
Due to lack of sources or evidence, Susan's surname should be changed to Unknown. Objections? If one of the managers would kindly make the change it would be appreciated.
The birthplace should be changed to just Kent, England also, for accuracy
UNKNOWN-214161 and Asherst-3 appear to represent the same person because: Seems to be the first wife of John JOhnson. Same birth and death dates and places.
edited by Carol (Jennings) Thoma
I'm going to move forward, since there is so much discussion already (below).
Cheryl Skordahl
We've used "Other Last Names" for unsourced surnames to hopefully deter creation of duplicates. Sometimes it works; sometimes it doesn't.
The previous merge with Unknown-214161 went in the wrong direction because the Unknown profile wasn't project protected; if it had been, it would have controlled the direction of the merge.
Its less time consuming to leave the possible LNAB and make a note in the Biography Space about the Unknown LNAB and parentage to stave off duplicate profiles for this person.
I had a profile for this person that was UNKNOWN-214161 - but it was decided it was best to merge it with the current profile.
The birthplace should be changed to just Kent, England also, for accuracy