Page Comparison

...

Set up the pantheon.yml file

We need to add a pantheon.yml file to configure the environment to match what it was at acquia. 

# Put overrides to your pantheon.upstream.yml file here.
# For more information, see: https://pantheon.io/docs/pantheon-yml/
api_version: 1
php_version: 7.1
drush_version: 8
web_docroot: true

The api_version line is standard. You can use drush status to get the php and drush versions of the current acquia site. Since there is a nested web root, we need to add the web_docroot line.

Available php versions are at: https://pantheon.io/docs/php-versions/

Available drush versions are at: https://pantheon.io/docs/drush-versions/#configure-drush-version

Code Things

Rename the docroot directory to web, since that is what pantheon expects.

Add a symlink from docroot to web to account for any composer config that includes the docroot path.

Sync the files directory

You can use these instructions for Manually transferring drupal files with rsync.

...

NOTE: You may need to rsync directly from the prod site. It seems that when you move files between prod and dev in the acquia control panel, it doesn't delete files from dev, leading to a bunch of orphans. Or you could delete the 

Make sure you get both the files directory and the adjacent files-private directory, if anything is in there.

Then you upload the files to the pantheon dev site:

...

Since we are using a nested web root, the config directory can be in the root code directory, and not in the pantheon default of sites/default/config.

APC, redis, and solr

Follow the instructions to set up redis at: https://pantheon.io/docs/redis/

Protect default drupal files?

Remove Acquia modules

The acquia connector module should be uninstalled after db import. When you are sure that there will be no re-import of the db, you can also remove the connector module from the git repository.

Related articles

...