Sage 100

 View Only
  • 1.  v2016 migration (std) from v2014 with Avalara inst

    Posted 05-17-2016 10:47
      |   view attached
    v2016 migration (std) from v2014 with Avalara installed. I have installed v2016, PU 1 and the Avalara connector. When I go to do the initial migration, I get the message below indicating that the modifications will not migrate. This is my first migration involving Avalara. What does this mean exactly. is something not installed properly? Go ahead and migrate, then reinstall the Avalara piece?? Thanks in advance.


  • 2.  RE: v2016 migration (std) from v2014 with Avalara inst

    Posted 05-17-2016 10:51
    You got it - migrate and then re-install.


  • 3.  RE: v2016 migration (std) from v2014 with Avalara inst

    Posted 05-18-2016 09:22
    My interpretation of this warning is that enhancements were found and will need to be installed in the new installation - obviously, they do not migrate. If you have already installed them, do you need to do it again AFTER the migration? This is different from installing an update where you DO have to reinstall the enhancement(s). Simply migrating does not touch the program files, in my mind. Did you attempt to see if Avalara was still active before reinstalling it? Would be interesting to know for future reference.


  • 4.  RE: v2016 migration (std) from v2014 with Avalara inst

    Posted 05-18-2016 11:01
    I migrated a 4.5 with a DSD enhancement to 2016. I didn't have the 2016 enhancement installed but it worked anyway.


  • 5.  RE: v2016 migration (std) from v2014 with Avalara inst

    Posted 05-18-2016 13:12
    Thanks everyone for posting back. Migrations can be a humbling experience. Just when you think you have seen it all, something new pops up. As noted above, this was my first Avalara migration and this message knocked me off my game a bit. I proceeded with the migration which was uneventful. But as a precaution, I reinstalled the Avalara enhancements before verifying the migrated data. In hindsight (always 20/20) I made a mountain out of a molehill. I installed Avalara after installing PU 1 so I think @ThereseLogeais was spot on! You don't have to reinstall Avalara again after the initial migration. All the data appeared, all of the panels were there. Life is much better and client is a couple steps closer to going live in v2016.


  • 6.  RE: v2016 migration (std) from v2014 with Avalara inst

    Posted 05-18-2016 13:42
    Instructions for installing both JobOps and DSD enhancements indicate the third party program should be reinstalled after you migrate so I've gotten in the habit of doing that with all third party programs to avoid issues.