If you’re still using OAuth 1.0, we need to understand your migration plans so we can minimize customer disruption for our mutual customers.
With the Dec. 17, 2019 OAuth Migration deadline quickly approaching, we now require all apps that are still using OAuth 1.0 to share their migration intentions by Oct. 31, 2019. Sharing your migration intentions will take you less than one minute.
What happens if I don’t share my migration plans by October 31?
If your app uses OAuth 1.0, and we don’t hear from you by Oct, 31 (if you inform us that you will not migrate your app to OAuth 2.0), we will begin the process of making these changes in November:
- We will reach out to your application’s users to inform them of the December 17 deadline, and explain that your app is in jeopardy of breaking. This will give them the opportunity to reach out to you for more information or search for another app that will provide them the functionality they need.
- If your app is listed on Apps.com, we will delist that app from Apps
If you would like to avoid these situations, you can fill out the form to share your migration intentions.
Not sure what to consider in your plan?
If you haven’t already done so, we suggest that you review your migration options as you develop your plan.
Based on feedback from our developer community, you can expect to spend 10 to 20 hours to develop a full end-to-end plan for OAuth Migration. The time it takes to iron out a plan depends on factors, such as the volume or complexity of your connections, how your app is hosted, and others. Note that this benchmark was determined based on apps that used the QuickBooks SDKs and OAuth client libraries.
Some key steps to consider in your plan:
- Consider rewriting your existing QuickBooks Online accounting and/or payments API connection process, so that all new connections use OAuth 2.0. In the meantime, let existing connections continue to use OAuth 1.0 for a short transition period.
- Decide how you’ll migrate the existing active connections. For example, write a one-time script that uses Intuit’s Migration API to migrate the tokens (all at once or in batches). Or, use the OAuth Migration Playground to migrate those tokens one at a time.
- If you need to provide a description of work to a client, system integrator, or a freelancer, check out this Change Management Request template for ideas about what to include.
Next steps
After you tell us your target date and anything else we should know about it, and you’ll earn 50 points that you can apply toward current and/or future rewards on The Bridge.
Note: This mission and offer is for developers whose apps still use OAuth 1.0 for QuickBooks Online accounting and payments API calls. As a reminder, you must migrate to OAuth 2.0 by Dec. 17, 2019 at the latest. We strongly recommend you plan to migrate sooner.
As always, please feel free to ask questions about OAuth migration in our OAuth help community!
Leave a Reply