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:
For the majority of the time, this is usually okay, as time we'll only be sending little bits of data hourly. However, if we're going to push a whole years worth of data, we'll most likely hit these limits. As a result, we'll have to wait until the limits reset, then send the next portion of data. This isn't a very smooth process, however it's an outside limitation that's not in our control.
Certain specific eCommerce APIs such as eBay are also known to only allow up to 30-90 days' worth of historical data to be extracted.
For example, last year you may have sold an item that you no longer sell today. Now, that item has been deleted from your eCommerce system. The issue here, is that 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 eCommerce 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.
We generally recommend that you explore other historical data migration options first (e.g. CSV import/export features within your eCommerce 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, please contact our support team and acknowledge that you are willing to proceed despite the risks highlighted above. We will then do our best to assist.
PLEASE NOTE: Once data has been sent to your Accounting system, there is no way for OneSaas to reverse this.