By using this website, you agree to our Terms of Use (click here)
We working with a consultant to set up our Acumatica and move away from Everest, our current software. Is it a big commitment (cost) to import our historical data from Everest into Acumatica? Or do most installations of Acumatica "start clean" without the historical data?
Hey Doug,
My first question would be, why is your historical data important to you? if your answer is for reporting and analysis purposes I would be directing you towards a BI tool that can capture data from multiple sources such as Everest and Acumatica.
The saving in implementation costs of extracting, cleansing and importing data could probably cover the BI licensing for 2 years.
If the reason is more simplistic, resend an overdue sales invoice or lookup a serial number my advice would be to reduce your Everest licensing down to one user and just pay the annual ALF to maintain that software for these ad-hoc queries and regulary review the need for this every 6 months. Again this could be cheaper than the implementation costs of data migration.
Hope that helps
Carl
Carl
Your insights are greatly appreciated. I was not thinking this way. Both of your ideas are spot-on to our issues. I will look into both of your solutions. Thank you so much.
I am going to circulate your comment to our internal team. Thank you again,
Doug
I also like the BI route. A Data Warehouse is a great place to park old data that isn't going to change, then combine it with Acumatica data that continues to be refreshed.
Another option if you just want to lookup old data but not combine it with Acumatica data is to load it into custom Acumatica tables, then make it available to users via Generic Inquiries like this:
https://www.augforums.com/importing-historical-data-acumatica-cool-twist/