evernote export local notebook to another

Our service is comprised of the following building blocks. It’s probably best that we start at the beginning with an overview of the Evernote service. This is not intended to be a full runbook of the migration, but should cover the key decisions we had to make and how we approached them. And seemingly in the blink of some very weary eyes it was over, we completed the migration from a standing start in 70 days!įor those of you who want to understand how we approached and executed the migration or are even considering such a migration, we want to give you a deeper view of what we did and how we did it so quickly. Since we made the first announcement, we have been working in the background to complete the migration out of our physical datacenters into our new home on Google Cloud Platform (GCP). The decision to move to the public cloud was an easy business decision and an exciting one for all of us at Evernote. While the infrastructure we had was well suited to support Evernote at the time, it lacked the speed and flexibility we needed for tomorrow. But it was also limiting – difficult to scale, slow to upgrade and expensive to maintain. This approach gave us the ability to build the service we wanted the way we wanted to build it.

Since inception of the service in 2008, Evernote has owned, configured, and maintained its own servers and network.

Evernote export local notebook to another