Create migrating-cloud-server.md

Author: michelle-luna

jekyll/_cci2/migrating-cloud-server.md

@@ -0,0 +1,27 @@
+---
+layout: classic-docs
+title: "Migrating from Cloud to Server"
+short-title: "Migrating from Cloud to Server"
+description: "Migrating 2.0 Cloud projects to a 2.0 server installation"
+categories: [getting-started]
+order: 1
+---
+
+*[Migration]({{ site.baseurl }}/2.0/migration/) > Migrating from Cloud to Server*
+
+There is no formal process or toolset to migrate between CircleCI cloud (SaaS) to an installed CircleCI Server setup.
+The process is to perform a fresh install of CircleCI 2.0, using AWS and Terraform, see [Installation]({{ site.baseurl }}/2.0/aws/) for instructions.
+
+Next, you will need to manually copy over all of your project settings including Contexts, environment variables, and API tokens.
+
+**Note:** It is not possible to bring your projects' build histories from SaaS; you will have to re-add all of your projects to your Server installation.
+
+Your 2.0 `config.yml` files should work as-is on Server, assuming they are working on SaaS. There are small differences between the 1.0 build environments that may result in some 1.0 configs not translating 100% from SaaS to Server. 
+
+Custom `machine` executor AMIs and configurable instance types are defined in a specific way, so consider how your teams may be using configurable resources, `resource_class`, on SaaS currently, when defining your build cluster.
+
+## Limitations 
+
+- Currently `macos` executor is not supported on Server.
+- Bitbucket is not supported on Server, GitHub ENterprise is the only supported VCS.
+