QuickBooks Online merchants face mandatory move from OneSaas to new connectors
QuickBooks Online merchants using legacy OneSaas apps are being moved to rebuilt e-commerce connectors through a migration banner inside the product.
Online sellers who push store transactions into QuickBooks Online through the older OneSaas apps are in the middle of a forced platform change. Intuit has rebuilt its e-commerce integrations and folded them into QuickBooks Online itself, and the migration runs through a banner inside the product. Several major store platforms are covered, and the switch is not optional for anyone still on the legacy apps.
Who needs to migrate?
The change applies to merchants using a connector for any of the following platforms:
- Shopify
- Amazon Seller Central
- eBay
- Etsy
- Wix
- WooCommerce
- BigCommerce
- Squarespace
If your store is on that list and the connection runs through OneSaas today, the move applies to you. Sellers on platforms outside the list are not part of this migration.
The improvements that matter
According to the comparison Intuit has published, the new connectors match the old apps on the fundamentals. Detailed order import, product tracking, and customer tracking all carry over, and both generations work worldwide. The differences sit in three areas.
Payout reconciliation, only partial under OneSaas, is fully supported in the new system. Tax handling shifts from manual mapping on your side to mapping handled inside the connector. Management itself moves out of the separate OneSaas interface and into QuickBooks Online, leaving one place to review settings, transactions, and reconciliation.
Why did Intuit rebuild the platform?
The vendor’s stated reasoning is largely structural. A single platform now serves every connection. Settings, transaction review, and reconciliation behave the same way whether the source is a storefront or a payment service such as Square, PayPal, or Stripe.
Intuit also points to the plumbing behind the new connectors. Imports retry automatically when a step fails, which the vendor says prevents duplicates and reduces the risk of missing transactions or payouts at high volume. Fees arrive broken down line by line, and reconciliation follows a defined workflow.
There is a maintenance angle as well. With one platform instead of several legacy systems, fixes and new features reach every connector at the same time.
Get your records straight first
Two preparation steps are worth taking before you touch anything. Finish any pending transaction reviews or reconciliations sitting in your current app, since half-completed review work does not travel cleanly between platforms.
Then write your settings down. Account mappings and the date of your last imported transaction are the two records that matter. Those notes become your reference point if anything looks wrong after the move.
Running the migration from the banner
The banner does most of the work, and the sequence is short:
- Go to All apps, select Accounting, then select Integration transactions.
- Find the migration banner at the top of the page and select Update now.
- Authorise the new app when prompted. QuickBooks then migrates your relevant settings and historical data.
- Review the migrated settings and your sync start date.
- Select Sync now to begin importing data.
The steps assume the banner has appeared for your account. It is the entry point Intuit describes for the move.
The start date is the trap
The one setting that can genuinely distort your books is the transaction start date. The migration flow carries a blunt warning: the date you pick must not overlap data you have already imported.
Overlap means double counting. If your OneSaas app imported sales through the end of last month, start the new sync from the first day of this month. Transactions already in your books will not remove themselves, and a second copy of the same sales period is a cleanup job nobody wants.
Help built into the flow
Assistance lives inside the migration surface itself. Each app tile in Integration transactions carries a chat icon for live help, and the same page holds a feedback option for reporting problems with the new connectors. An email route is listed for the migration as well.
The takeaway
The migration is compulsory, but the mechanics are simple, and the gains are real for anyone who reconciles payouts by hand today. In our read, the practical risk sits in one field: the sync start date. Close out pending reviews, note your mappings, pick a cutoff that starts clean, and the rest of the switch proceeds on its own.