Logo
Home

3 Months To Go: Timeline to Discontinue the QuickBooks Desktop REST API and Intuit Sync Manager

We are three months out from the deprecation of the QuickBooks Desktop REST API and Intuit Sync Manager happening on March 1, 2016. With only three months to go, development and migration to your new application and messaging to your customers should be in full swing.

What do you need to do right now?

  1. Connect with your customers. Let them know your application status and your migration plans. Next week, Intuit will be sending out an email to the remainder of our joint customers. If they havent heard from you lately (or ever), the email from Intuit could come as a surprise and cause confusion or unnecessary cancellations to your application.
  1. Continue your application development and customer migration.
    You have three choices:

    • Move to a QuickBooks Online integration:
      • If you have not already done so, build an integration with QuickBooks Online and publish it on apps.com.
      • Disconnect your existing customers from your QuickBooks Desktop app and migrate them to QuickBooks Online and your new app.
      • Your customers can call the QuickBooks migration hotline at 1-800-488-7330 to discuss their migration options with an expert or get more information on how to migrate online. Once migrated to QuickBooks Online, they can reconnect your app with their data.
    • Move to a QBXML SDK QuickBooks Desktop integration:
      • Build a desktop integration using:
        1. QuickBooks Desktop SDK and the QuickBooks Web Connector.
        2. QuickBooks Desktop SDK and your own uploader.
        3. Hire a 3rd-party dev to help build your app (we can help make connections if you decide to go this route).
      • Disconnect your existing customers from your old app and migrate them to the new app.
      • We recommend that you list which QuickBooks Desktop products – including version/year and release – that you support. Specifying your compatibility with QuickBooks Desktop products will help ensure that customers are picking the right apps for their version of QuickBooks.
    • Discontinue your integration with QuickBooks Desktop:
      • It is okay to discontinue your integration with QuickBooks Desktop. However, please let your customers know that the app will no longer sync with QuickBooks beginning March 1, 2016.
      • Disconnect your customers from your app.
  1. Connect with us on your plans. If we havent yet connected on your plans regarding this discontinuation, please let us know what you plan to do ASAP. We are tracking all apps affected and want to make sure you and your customers receive the help and support you need during this transition.

Whats happened so far?

  • November 2013: We announced we would no longer be onboarding new developers to the QuickBooks Desktop REST API.
  • September 2014: We announced an 18-month timeline to discontinue the Sync Manager and the QuickBooks Desktop REST API via our Intuit Developer blog and through direct email to all impacted developers.
  • March 2015: We reached out again to all impacted developers via email to remind them of this timeline.
  • May 2015: We posted a public reminder to all developers of the timeline.
  • September 2015: We removed the marketing page on apps.com for apps that use the QuickBooks Desktop REST APIs and removed in-product discovery of these apps.
  • October/November 2015: The Intuit Developer Relations team reached out via email and phone to all developers affected by this change to assess application plans.
  • November 2015: Intuit sent emails to a subset of the Pro/Premier and Enterprise customers letting them know that Sync Manager is being discontinued and apps they use may be impacted.

Whats next?

  • December 2015: Intuit will message the remainder of the customer base affected by the discontinuation of the APIs and Sync Manager.
  • March 1, 2016: The QuickBooks Desktop REST APIs and Sync Manager will no longer be accessible by your application.

Need help or have questions? Please comment here, share on our developer forums, or reach out to us directly.


Posted

in

by

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *