Skip to content

Migrate from SFTP to Google Cloud Storage (GCS ) for Preferred Provider Program.

To enhance efficiency, security, and scalability for content delivery, we are transitioning from SFTP to Google Cloud Storage (GCS). GCS provides a fully managed, durable, and high-performance storage solution that seamlessly integrates with our existing systems.

This guide outlines the steps to migrate your content delivery workflow from SFTP to GCS, ensuring a smooth process with minimal disruption. 

💡 note:

You do not need to redeliver all your older content as part of this migration. Older content already delivered via SFTP will remain accessible and does not need to be duplicated in the new GCS setup.

Steps to Migrate to GCS ( Google Cloud Service )

1. Create a GCS Service Account

  • Start by creating a Google Cloud Storage (GCS) service account through the Google Cloud Platform (GCP). The service account email will follow this format:

    service-account-name@project-id.iam.gserviceaccount.com

    This service account will be used to grant the necessary permissions and provide access to the bucket, allowing you to begin the content ingestion process and testing.

    Ensure that you have the service account credentials ready before proceeding to the next step . 

    Once you provide us with the service account details, we will grant access to the designated bucket. For all info related to Google Cloud Service accounts overview Please visit this link .

2. Submit the Request Form

  • Fill out the [GCS Migration Request Form]. Once submitted, Please allow up to 4 working days  for us to create the GCS bucket for you.

3. Testing the Bucket and Content Delivery

  • Once you have received your GCS bucket details, you can proceed with testing the content delivery to the live environment. Follow the steps below to perform the necessary tests and verify the delivery status through the Spotify for Music Providers portal:

Step 1

Deliver New Content:

Deliver a new piece of content with a unique UPC to test the insertion of new content into the system.

Step 2

Update Existing Content:

Perform an update on content that has already been delivered. This can involve either:

1- Changing metadata (e.g., updating track details or artist information).

2- Requesting a takedown of the content.

After completing these tests, use the Spotify for Music Providers  portal to verify the delivery status and ensure the tests were successful.

4. Submit Confirmation

  • If the test delivery is successful and everything looks good, confirm the migration by submitting the ingested UPCs. This can be done through the Evidence Submission section in the PPP section within the Spotify for Music Providers portal.

Note : After completing the migration and successfully delivering content for at least one week without any issues, your SFTP access will be deprecated 2 weeks post-migration.

If you encounter any issues during the migration process, please reach out through the ‘’ Contact us ‘’ section in the PPP Portal .