title: What are the best practices for migrating to marketplace v2
body: <p>I have an app in the Google Apps Marketplace V1 using OpenID for login and a bunch of APIs using OAuth1.0 for authentication.</p>
  
  <p>Now I need to migrate it to the Google Apps Marketplace V2, so I followed the docs <a href="https://developers.google.com/apps-marketplace/preparing" rel="nofollow">here</a> and <a href="https://developers.google.com/apps-marketplace/listing" rel="nofollow">here</a> to update my app to use OAuth2.0 for authentication and updated all my API calls to authenticate with OAuth2.0.</p>
  
  <p>Everything works fine, but now I need to switch from Marketplace V1 to Marketplace V2. The problem is that I can only have 1 version of my app live at any given time - either it uses OpenID &amp; OAuth1.0, or it uses OAuth2.0 - it cannot use both.</p>
  
  <p>So, I have 2 problems:</p>
  
  <ol>
  <li>I need to submit my app for review using <a href="https://docs.google.com/a/google.com/forms/d/14QOb8PbSLKDgwIp8Zv-luoAAVurPXUqtzL0Hgikp3rk/viewform" rel="nofollow">this form</a>. However, in order for Google to review my app in the new Marketplace, they will need the new version of my app, but I cannot push that code live, as existing customers will be disrupted - they won't even be able to log in.</li>
  <li>When the new marketplace listing does go live, my app will still be running the old codebase, so any new installs wont work.</li>
  </ol>
  
  <p>So, how do you get around this?</p>
  
  <p>I currently have my marketplace listing pointing to a test environment. Question is, can I submit it for review, then change the app it points to when it's been approved? Ideally, when it does get approved it won't automatically be listed publicly in the new marketplace until I have uploaded the new code base. I guess I will then need a period of downtime in order to use the <a href="https://developers.google.com/apps-marketplace/v1migratev2" rel="nofollow">Migration API</a> to move my existing customers over.</p>