This is not my solution but I found it on the internet because I had the same problem. The credit goes to someone else but it worked for me. I highlighted the solution. Loin Date: May 2017 Location: Brisbane Posts: 13 For those of you unable to upload Ancestry raw dna data to FTDNA. The latest I got from FTDNA Customer Support asserted that "reads for specific SNPs are in the wrong locations in the files". This turns out to be rubbish. I imported into Excel a file that would upload and a file that would not. I then got Excel to identify differences between the files. The differences are NOT associated with SNP locations. The differences are purely related to the pre-amble text in the Ancestry raw dna data files. By changing the preamble text, the files will upload. The following preamble is from a file that will not upload: #AncestryDNA raw data download #This file was generated by AncestryDNA at: 05/15/2017 03:51:26 UTC #Data was collected using AncestryDNA array version: V1.0 #Data is formatted using AncestryDNA converter version: V1.0 #Below is a text version of your DNA file from Ancestry.com DNA, LLC. THIS #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL RESEARCH #ONLY. IT IS NOT INTENDED FOR MEDICAL OR HEALTH PURPOSES. THE EXPORTED DATA IS However, this text will upload: #AncestryDNA raw data download #This file was generated by AncestryDNA at: 05/28/2017 23:32:38 UTC #Data was collected using AncestryDNA array version: V2.0 #Data is formatted using AncestryDNA converter version: V1.0 #Below is a text version of your DNA file from Ancestry.com DNA, LLC. THIS #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL RESEARCH #ONLY. IT IS NOT INTENDED FOR MEDICAL, DIAGNOSTIC, OR HEALTH PURPOSES. THE EXPORTED DATA IS Ignoring the different times in line 2, the key changes are: Line 3: "V2.0" instead of "V1.0" Line beginning "#ONLY": add ", DIAGNOSTIC," When I changed the text as above, two Ancestry files that previously failed (many times) to upload, then uploaded at the first attempt. Heaven knows why the FTDNA upload converter concerns itself with the preamble. Clearly GEDMATCH does not because as I and others discovered our unaltered files would readily upload to GEDMATCH. And shame on you FTDNA to assert the problem was related to SNPs being in the wrong location. FTDNA: get your house in order! There is, of course, another issue related to why Ancestry changed the collection version and other text. Ancestry DNA extractions in Feb and 28 May had "V2.0" text, while extractions on 15 May had "V1.0". I am tackling Ancestry on that point. G ----- Original Message ----- From: "Tim Janzen" <[email protected]> To: <[email protected]> Sent: Sunday, August 27, 2017 2:17 PM Subject: Re: [DNA] Uploading AncestryDNA results to ftDNA >I haven't heard any problems with people uploading AncestryDNA data from >the current chip. Uploading the zipped file should work ok. If there are >problems, I would open the raw data file and make sure that it looks >complete. The zipped file should be about 5.7 MB in size. > Tim Janzen > > -----Original Message----- > From: GENEALOGY-DNA [mailto:[email protected]] On Behalf > Of Brooks Family > Sent: Sunday, August 27, 2017 11:12 AM > To: [email protected] > Subject: [DNA] Uploading AncestryDNA results to ftDNA > > My (new!) cousin is trying to upload her AncestryDNA results to ftDNA, > and running into errors. Two questions: > > * Is ftDNA accepting AncestryDNA's results from its most current chip? > > * Does she upload the zipped or unzipped file? > > Really, I looked on ftDNA and DNAADOPTION.com. Not finding an answer to > the latter question. > > Thanks! > > > > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message