Migration full history of all ledgers

sjc01234

We are upgrading re-implementing Navision. We are moving from NAV2009 Classic Client to NAV2017. So, we have lots of data to move over into the new database with lots of little details to work out.

We are of course trying to plan out the actual go-live and what it means for all of our active and open entries. Do we just bring over balances and open entries? Or - why not just bring over entire ledgers, including full history and any open activity?

Has anyone done this before (bringing over the entire history of all ledgers). Is it recommended not to for any reason?

Slawek_Guzek

Data-wise by bringing over all the details you are doing the upgrade.

Do some analysis of upgrade toolkits, for example, 2009 -> 2013, and 2013 -> 2017 to see what are they are doing with the data. You would need to extend them to include all custom fields added to standard tables anyway. You may also attempt to merge the two separate toolkits code to save on upgrade time.

If you decide to do re-implementation (data-wise) then you should not bring over any ledger entries, but journal-in balances, and re-create open documents - as if you implement NAV from scratch.

Mixed approach, in my view, makes little sense, as you would have to prepare your version of upgrade toolkit, dealing with existing ledger entries, only to bring in a subset, and on the top of that, you will still have to prepare some interfaces to journal-in balances. The only advantage of mixed approach would be to reduce your data significantly, therefore reducing time processing during of go-live (still re-implementation would be possibly faster)

davmac1

I have done a few data only upgrades where people do new mods from scratch but want to keep the existing data - or sometimes drop some custom fields.
My method is to only add the custom fields - then do standard upgrades to NAV 2009 (if necessary), do the database rebuild with 2013 executable, but use the data upgrade in 2015 (step 1 and step2 from 2009 to 2015) where it is easy to do a force sync to drop unwanted fields and tables. From 2015 do the upgrade to the latest version.
This type of upgrade is simple and does not take much developer time.