Sage 100

Starship upgrades.... Is it as painful as it is starting to sound? First client ever on Starship. They want to move from v2015 to v2016. This is the first response from their tech support. Currently waiting on clarification. If you are upgrading in place, all we have to do is update the Workstations in SS and reattach the Sage Company. If it's a new machine, it's the same work flow. **If you are planning on installing 2016 along side of the current Sage install it will cause issues with connecting to the correct instance while you are doing your testing and migrating info.**

@JohnWilder ??

Why do you have 2 instances of Shipship? Also moving what do you mean... 2016 to 2016?

@JeffSchwenk - Email me directly, see if I can help you out.

Oops, typo...

I haven't found anything with Starship that difficult.

I don't usually pilot the starship. It is a go live test.

Starship will upgrade these for a fixed fee. I've usually had the customer pay the fee largely because I find that Starship tech info is not especially well documented. I agree that it's not that tough to install but have been bitten once or twice with odd requirements.

Starship is handling the upgrade. This was their initial response....

I never pilot the StarShip on an upgrade such as that. My experience is that when you are ready to start using 2016 open the workstation client (v2016) first, then launch StarShip, and ""voila"" it works. Points properly to the newer version.

Good to know. This might not be hard. Now to get Highjump, Ebiz and Multi-bin lined up in a row... Upgrade life is certainly getting complicated...

ALL bets are off with those... all I can say is Good Luck!!!

I've started to strongly advise customers that before they add-on any significant enhancement that they do an upgrade. Most ignore me but I think it's wise to get as current as possible. Most of the third party integrations have been pretty good with upgrades. It is just coordinating all the schedules and getting people to do their part.

We just ran into the issue @JeffSchwenk refers to in his opening quote, but with ShipGear. Client is on v2013. The night before, we installed v2016 on the same server and migrated the production company to begin testing. We copied the v2013 production company to a test company. In the am, they discovered ShipGear was now looking at v2016 instead of v2013. Still working on a solution to running both installations.