Get error when uploading ANcestryDNA

[hansonrf]

Only 13 matches

I Recenty unlocked an Ancestry transfer that has only 13 matches shown. There are thousands on GedMatch with 'same' upload. One big difference is that the Ancestry kit had to be 'processed' to work here using http://www.mapmy23.com/tools/ancestry_ftdna_fix.php Thank the author!!

This is NOT a knock at FTDNA or the conversion, for sure, but only a warning to others that the 'conversion' may be imperfect. Of the 13 matches identified by FTDNA, a few are also the strongest matches on GedMatch.

If I had a choice, I'd take more matches ID'd but with a suitable disclaimer. Sure wouldn't want a lot of false matches, though...

IMHO, Ancestry and 23andMe are driving a wedge in the utility of autosomal DNA for pecuniary interests.

[JohnTF]

error when uploading ANcestryDNA

Hello, I'm a new member to the forum.

My answer to the problem people have transferring Ancestry raw data to FTDNA ….

When you download raw data from Ancestry it adds the date of transfer to the zip file Title.. ie: dna-data-2018-03-03 You Need to REMOVE the Date -2018-03-03 then transfer zipped file dna-data to FTDNA

Kiss..(Keep it simple stupid)

[Jim Barrett]

KISS

Kiss..(Keep it simple stupid)

Those were the Good ol' Days.

[chrisbonisa]

Hello, I'm a new member to the forum.

My answer to the problem people have transferring Ancestry raw data to FTDNA ….

When you download raw data from Ancestry it adds the date of transfer to the zip file Title.. ie: dna-data-2018-03-03 You Need to REMOVE the Date -2018-03-03 then transfer zipped file dna-data to FTDNA

Kiss..(Keep it simple stupid)

John we actually tried that when the original problems started happening and it didn't seem to matter. It would be wonderful if it were this simple though, thats for sure!

[JohnTF]

Since suggesting this on Facebook 18 people have had success (that I know of) The ( - ) before the date should also be removed.. Leaving dna-data On transfer it will read dna-data.zip
Would be interested to hear if this "does/does not" work for anyone

[prairielad]

Since suggesting this on Facebook 18 people have had success (that I know of) The ( - ) before the date should also be removed.. Leaving dna-data On transfer it will read dna-data.zip
Would be interested to hear if this "does/does not" work for anyone

Is this on files that failed to upload on initial attempt (using ancestry original unaltered file)?

Not all ancestry files fail to upload, it is just a subset that for some reason or other have less SNP within file, making it slightly smaller then the normal ancestry Raw Data file....these are the ones that FTDNA was rejecting

[JohnTF]

Is this on files that failed to upload on initial attempt (using ancestry original unaltered file)?

Not all ancestry files fail to upload, it is just a subset that for some reason or other have less SNP within file, making it slightly smaller then the normal ancestry Raw Data file....these are the ones that FTDNA was rejecting

This is on files that failed first...As to whether the files were for any reason a different size and why, is beyond my understanding.
At age 77 I try the simple route or ask someone

[prairielad]

This is on files that failed first...As to whether the files were for any reason a different size and why, is beyond my understanding.
At age 77 I try the simple route or ask someone

[mrsprobsma]

Ancestry uploads elsewhere but not here

Add me to the list, zipped or txt, new or old download, will not load here and same error message and advice to buy kit. Please help.

[prairielad]

Add me to the list, zipped or txt, new or old download, will not load here and same error message and advice to buy kit. Please help.

Have you used the mapmy23 tool to convert ancestry raw data to format ftdna will accept?

[Tim Campbell]

I had some trouble uploading my wife's results. The mapmy23 tool worked. I was concerned I would get a limited number of results or somehow get false positives. So far this doesn't appear to be the case. Thank you for providing the free tool. That's truly above and beyond.

[RossWakelin]

Thanks for a useful thread. Before I discovered the forum I had sent a help request to FTDNA asking what format they required the data to be in (having exhausted all variations I could think of).
While waiting for their reply I found this thread and used the tool to convert the AncestryDNA v2 file and submitted it. Then I got the reply (given below) stating that they no longer were accepting AncestryDNA kits due to an incompatibility. However a few days later the upload of the tool-corrected file went through (with, as noted elsewhere, no distant/speculative matches included).
Hence I assume that FTDNA either cannot tell if an AncestryDNA file has been modified by the tool, or they don't care. They could have pointed to the discussion forum and this thread, but they seem to prefer to not accept the file and hope you will buy a FTDNA kit. Given that choice I think I'd stay with AncestryDNA and import to GEDmatch.

The reply from FTDNA "information specialist" was:
------
Thank you for contacting FTDNA. Normally you should upload the .zip file that Ancestry provides without modifying the file. Unfortunately, Ancestry DNA recently made some changes to their raw data files that make them incompatible with our transfer system. We are not currently able to accept transfers from Ancestry DNA, but we're working to update our transfer system so that we can accept them again in the future.
We do not recommend altering your raw data file in any way prior to uploading it to us. We cannot say how changes to your raw data file will affect your transfer.
-------

[chrisbonisa]

Thanks for a useful thread. Before I discovered the forum I had sent a help request to FTDNA asking what format they required the data to be in (having exhausted all variations I could think of).
While waiting for their reply I found this thread and used the tool to convert the AncestryDNA v2 file and submitted it. Then I got the reply (given below) stating that they no longer were accepting AncestryDNA kits due to an incompatibility. However a few days later the upload of the tool-corrected file went through (with, as noted elsewhere, no distant/speculative matches included).
Hence I assume that FTDNA either cannot tell if an AncestryDNA file has been modified by the tool, or they don't care. They could have pointed to the discussion forum and this thread, but they seem to prefer to not accept the file and hope you will buy a FTDNA kit. Given that choice I think I'd stay with AncestryDNA and import to GEDmatch.

The reply from FTDNA "information specialist" was:
------
Thank you for contacting FTDNA. Normally you should upload the .zip file that Ancestry provides without modifying the file. Unfortunately, Ancestry DNA recently made some changes to their raw data files that make them incompatible with our transfer system. We are not currently able to accept transfers from Ancestry DNA, but we're working to update our transfer system so that we can accept them again in the future.
We do not recommend altering your raw data file in any way prior to uploading it to us. We cannot say how changes to your raw data file will affect your transfer.
-------

I'm fairly certain they are saying that for liability reasons, however the way the tool works is by inserting "no calls" into snps missing from the incompatible ancestry file and deleting snps that are "extra". So its not "modifying your dna" as they say, its more like aligning 99% of it properly with the file format they are expecting, its still 100% your dna thats left in the file and thats why it works as we want it to. Its actually very surprising to me that they still have not adjusted their importer to detect and accept these files as its not that complicated.

[betadams]

FTDNA's cautious approach does not extend to them "blocking" the transfers from mapmy23, or accepting the $ fee for access to the chrome browser

[Jim Barrett]

FTDNA's cautious approach does not extend to them "blocking" the transfers from mapmy23, or accepting the $ fee for access to the chrome browser

Very true, but they are allowing transfers, unlike most companies.