Sage 100

EES 1.3 to 1.4 migration protocol For those of you who have upgraded clients (Dawn, I know you've got at least one under your belt), have you used a protocol that involves a test environment? If so, how have you handled testing 1.4 with the SageCRM component? Create a separate install of the SageCRM server? Does anyone have a protocol for this process?

We have installed a test install of EES 1.4, and migrated the data, etc. but have not done anything with SageCRM. After upgrading live, it just worked. We later are scheduling upgrades to SageCRM 7.0 as a separate project. I have done the same thing with the web engine, no test install just live (only for that piece).

Just completed the first 1.3 to 1.4 to SageCRM 6.2. Relatively painless. Planning to upgrade SageCRM to 7.0 SP1 next. I have read the Customer Letter on the SageCRM page of BOSS, and am downloading the 550MB download even as we speak. Anyone covered this ground yet? Gotchas? @Dawn?

Sounds like a good question for the Wolfman to jump in on........

I have no idea on the SageCRM part. I don't do SageCRM.

Ah... sorry I missed this one @BarbaraGoldstein! We have a three stage upgrade process that we follow for SageCRM (and we only deviate if the client begs and pleads and signs off on ""you are responsible for putting your production environment at risk. Sign here: ________"": 1. Trial upgrade - we usually do this as a small, fixed fee engagement. The purpose is to do a quick and dirty upgrade to shake out any problems with the upgrade process itself. 2. Client review - we provide a checklist of areas for them to check and actually sign off on (as opposed to saying ""go test it"" which results in 5 minutes of poking around and ""looks good!""). 3. Production system upgrade - we use anything found in steps 1 and 2 to create a comprehensive plan detailing what items will be covered and addressed during the production upgrade. Anything not mentioned is considered out of scope. Kind of a long winded answer but it gives insight into how we operate. During steps 1 and 2, we work with the MAS or Accpac partner to do a trial upgrade and client review of the accounting software at the same time (if it's necessary). One question I have for you: why are they going to EES 1.4 at this point? Why not move to MAS 4.5? It's more modular in nature and should provide a smoother upgrade process for future releases. I'm guessing they have an add-on that's not released yet for 4.5???

Thanks Peter, sounds like you do a similar process with CRM that we do with MAS. They are going to 1.4 first because the 4.5 Partner FAQ's (#7) state that EES clients need to be at 1.4 before upgrading to 4.5.

If they are ultimately going to 4.5 right away, I would upgrade them to 1.4 and then 4.5 in the trial upgrade (step 1) and then have them test and then in the production upgrade, do the same - 1.4 and then 4.5. (not sure if that's clear - re-reading it, I've confused myself)

I understand - shall I explain it to you? :-) Good idea - I'll consider that.