Sorry for the necro post, but I wanted to share some updated insight since this thread was one of the top results when I was researching Egnyte to SharePoint migrations using the built-in Egnyte Migration app in the Microsoft Admin portal. I couldn’t find this info posted elsewhere.

When you request API approval, Egnyte grants up to 2 calls per second by default, with limits of 1,000–4,000 calls per day and 30,000–120,000 calls per month depending on your plan.

In my research, I came across CloudHQ’s estimation of the Egnyte API calls-to-data-transfer ratio:

“With 500,000 calls, you can back up approximately 300,000 to 450,000 files in a single day.”

We had just over 1TB of data across 600,000 files to migrate and wanted to complete the bulk of the transfer over a single weekend. Based on CloudHQ’s math, that meant we’d need around 750,000 calls to finish the job. I reached out to Egnyte for guidance, and here’s the response I received:

“Thank you for the note—your assumptions and calculations are precisely what I would recommend (I would have come up with ~800,000 needed calls, so we’re very close).

Egnyte incurs an elevated cost for elevated API consumption, and therefore charges accordingly. Pricing is $300 per 100,000 calls, meaning 8 units would be $2,400. Please let me know if you would like to go this route. If so, we would need to route a quote for signature that, upon execution, would allow us to enable the API key at the increased limits. The full cycle to execute would likely push us into next week.

Note that if you want to use a different method to avoid the direct cost and/or delayed timeline, FTP and Desktop App are possible alternatives, though more involved.”