Common limitations when you sync historical data with OneSaas

While it may be possible for us to sync historical data going back years, it's not really the focus of our service and we find that if we go back too far, issues can arise. Here are some of those common issues explained further.

API limitations

Sometimes, other systems we integrate with will have API limitations of their own. 3rd party APIs set limits that can prevent us from sending too much data at once.

For the majority of the time, this is usually okay, as the time we'll be sending are little bits of data hourly. However, if we're going to push a whole year’s worth of data, we'll most likely hit these limits. As a result, we'll have to wait until the limits are reset, then send the next portion of the data. This isn't a very smooth process; however. It's an outside limitation that's beyond our control.

Certain specific e-commerce APIs such as eBay only extract up to 30-90 days' worth of historical data.

General Errors with Historical Data

One of the most common issues we find with historical data, is the fact that the older it is, the more outdated and inaccurate it tends to be.

For example, last year you sold an item that you no longer sell today and you already deleted it from your e-commerce system. We still need to integrate sales data associated with the item; however, as this item no longer exists, we're unable to integrate the data. The same situation can play out for older customers as well.

Other reasons for data corruption could be that you used to use an e-commerce extension that you no longer use today. Or you may have had new system updates done to your website which renders old data incompatible with your new database.

Recommendations

We generally recommend that you explore other historical data migration options first. For example, CSV import/export features within your e-commerce and Accounting. 

However, if that is not a viable alternative for your specific situation, and you would like to use our service to attempt historical data migrations, contact our support team. Acknowledge that you are willing to proceed despite the risks highlighted above. We will then do our best to assist.

Note: If the data was already sent to your accounting system, there's no way for QuickBooks Connector to reverse it.