We're making changes to the Community, so you may have received some notifications - thanks for your patience and welcome back. Learn more here.

Forum Discussion

Paul C.32's avatar
Paul C.32
Helpful | Level 5
2 years ago

Google migration deleted unnamed file

Looking at the "Google Migration Report.csv" file I see entries for a file that could not be converted and so it was deleted. The problem is that the "Source path" column is empty, so I have no way t...
Google
Third party apps
Third Party Integrations
  • Sam DBX's avatar
    Sam DBX
    2 years ago
    Hi all,
     
    Happy to jump in on the conversation to clarify a few points:
     
    As you know, the GDD migration started and processed files of specific set of users, with some receiving a migration report (CSV file). 
     
    For files that were already deleted by our users - we didn’t do any migration or any other changes. Our migration logic was, in very simple terms:
    • found a file
    • identified this file was a deleted file> it is not eligible for migration > the file was then skipped for migration.
    We understand that the message about deleted file was not very clear: Conversion failed,  File ineligible for migration, Deleted file.
     
    Once again, they were not deleted by Dropbox in the migration, but they were omitted because they were deleted prior to the migration. 
     
    We have partnered with our engineering team to clear up this messaging in the log as it does cause confusion about where the deleted files mentioned originate from.
     
    Let me know if you have any other questions,
     
    Thanks!
Paul C.32's avatar
Paul C.32
Helpful | Level 5

Hi Megan:

 

I'm confused, because the CSV report explicitly says a file was deleted. Are you saying that the entry in that report is wrong and we should ignore it?

 

Or, are you saying that the "deletion" didn't really delete anything because *I* deleted the file before the migration started? If this is the case, I'm still confused, because:
a) I did not remove files manually like that,
b) if a file was deleted, how could the migration even try to process it, if it was no longer there??

Sam DBX's avatar
Sam DBX
Icon for Community Manager rankCommunity Manager
2 years ago
Hi all,
 
Happy to jump in on the conversation to clarify a few points:
 
As you know, the GDD migration started and processed files of specific set of users, with some receiving a migration report (CSV file). 
 
For files that were already deleted by our users - we didn’t do any migration or any other changes. Our migration logic was, in very simple terms:
  • found a file
  • identified this file was a deleted file> it is not eligible for migration > the file was then skipped for migration.
We understand that the message about deleted file was not very clear: Conversion failed,  File ineligible for migration, Deleted file.
 
Once again, they were not deleted by Dropbox in the migration, but they were omitted because they were deleted prior to the migration. 
 
We have partnered with our engineering team to clear up this messaging in the log as it does cause confusion about where the deleted files mentioned originate from.
 
Let me know if you have any other questions,
 
Thanks!

About Integrations

Find solutions to issues with third-party integrations from the Dropbox Community. Share advice and help members with their integration questions.

Need more support

If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.

For more info on available support options for your Dropbox plan, see this article.

If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!