---
title: "Upgrading Drupal Starter Kits 1.x to 2.x"
date: "2024-10-30T13:24:04+00:00"
summary: "Upgrade Drupal Starter Kits from 1.x to 2.x with our step-by-step guide. Learn profile switching and module management for a smooth transition."
image:
type: "page"
url: "/drupal-starter-kits/upgrading-drupal-starter-kits-1x-2x"
id: "43cdedd4-68b9-48f5-9ec3-2d50fd3f928b"
---

Rebranding notice!

Acquia announces rebranding of its “Acquia CMS” offering, which includes a collection of Drupal modules. “Acquia CMS” is now referred to as “Drupal Starter Kits”.

Use the following steps to upgrade Drupal Starter Kits from 1.x to 2.x by using the profile `switch` command. This command also helps you to add the modules that were deleted from the most recent version but are still necessary for Drupal Starter Kits.

1.  If you use BLT, check your install profile with the following commands:
    
        ./vendor/bin/drush status --fields=install-profile
        Install profile : acquia_cms 
    
    1.  Edit `blt/blt.yml`.
    2.  Change the profile key to minimal.
2.  Run the profile switcher command to switch the profile from `acquia_cms` to `minimal`.
    
        ./vendor/bin/drush acms:switch
        
        The site's install profile will be switched from acquia_cms to minimal.
        
        Do you want to continue? (yes/no) [ yes ]:
        
        > yes
        
        Profile switched from acquia_cms to minimal.
    
3.  Verify the site and ensure that it works as expected.
4.  Export the configurations.
    
    You can observe the changes in the `core.extension` configuration parameter.
    
        ./vendor/bin/drush cex
        
        [notice] Differences of the active config to the export directory:
        
        +------------+---------------------+-----------+
        
        | Collection | Config              | Operation |
        
        +------------+---------------------+-----------+
        
        |            | core.extension      | Update    |
        
        |            | system.theme.global | Update    |
        
        +------------+---------------------+-----------+
        
        The .yml files in your export directory (../config/default) will be deleted and replaced with the active config. (yes/no) [yes]:
        
        > 
        
        [success] Configuration successfully exported to ../config/default.
    
5.  Commit all the changes, deploy them to your development environment, and run the following commands:
    
        ./vendor/bin/drush cr
        
        ./vendor/bin/drush cim --yes
        
        ./vendor/bin/drush updb --yes
    
6.  Verify that your development site works as expected.
7.  Upgrade Drupal Starter Kits to 2.x with the following command:
    
        composer require -W acquia/acquia_cms:^2.0
    
8.  (_Optional_) Add the [Google Analytics](https://www.drupal.org/project/google_analytics) module to your project, if required.
    
        composer require -W drupal/google_analytics:^2.0
    
9.  Update your database.
    
        ./vendor/bin/drush updb -y
    
10.  Commit all changes, deploy them to your development environment, and run the following commands:
     
         ./vendor/bin/drush cr
         
         ./vendor/bin/drush cim --yes
         
         ./vendor/bin/drush updb --yes
     
11.  Verify that your development site works as expected.
     
     The Drupal Starter Kits 2.x module keeps all the required dependencies previously available in the profile. The `acquia_cms` profile codebase does not exist in the `docoot/profiles/contrib` directory.