Skip to main content

marketplace_migration_steps

Marketplace Integration ONLY Migration Process

Overview​

If you have ONLY a Marketplace integration and DO NOT have a Drive Integration, please follow the steps below.

Please note: If you have an existing Drive Integration please follow the Migration Process linked here.

How to Migrate​

  1. Create a Developer Portal account by using this link here, click ‘Sign Up’, and follow the process to create an account.

    • Please note: That by creating this account, you agree that the linked Consumer Terms and Conditions and Consumer Privacy Policy will govern your use of a DoorDash account to order food as a consumer, but that your use of this Developer Portal will be governed by your existing Middleware Agreement (or Merchant Services Agreement if you do not have a Middleware Agreement) with DoorDash.
  2. Once the account is created, you will be redirected to the generic DoorDash Developer Portal homepage and will see that the request for the Marketplace integration is ‘Pending Activation’.

    • Please note: You will be able to add additional members to the Developer Portal once signed in by following the Add Members documentation.
  3. After creating the account, please contact our team through our Developer Portal Support Process and provide the email you used to sign up with. If you have any questions on the status of your integration or issues with making the Updates Required, please contact our team via the Support form in the Portal.

  4. Your Developer Account will be reviewed by the DoorDash team and moved to an Approved state the next business day. At this point, your legacy integration information will be accessible in the Portal including all current subscriptions and test stores.

    • [IMPORTANT] Your legacy integration will still be active and working as expected during the migration process.
  5. To complete the migration process, the following changes must be completed on your side.

  6. Notify DoorDash once these updates have been made through our Developer Portal Support Process. Once our team has verified these changes, we will let you know and approve the migration.

  7. Once approved, you can cutover to use the new hostname, url paths, and JWT for authentication for your Production Marketplace Integration.

  8. The migration is complete and you can now manage your integration within the Developer Portal. Please continue working with our team through the Developer Portal Support Process for future questions.

  9. Success! You have fully updated your legacy Marketplace Integration!

Have any questions? Please refer to the Migration FAQ page.

Developer Support Process​

You can inbound through our Developer Portal Support process using the below process. These inbounds will be sent to our team of Technical Account Managers who will respond to your questions.

Developer Portal Support Option

Developer Portal Support Option