Amanda

Excellent news. That's sounds like you'll be embarking on a migration more epic than that of the Monarch butterflies. Your local support team should have access to the past installs. But if they don't then I suggest contacting [email protected] and they should be able to advise further.

Good luck!

You can upgrade to v6.2 from v6.1 sp1

SageCRM 6.2 System Administrator Guide.pdf

Upgrade Previous Version of CRM: This option allows you to upgrade from

version 6.1 SP1. To upgrade from 6.0, you must first upgrade to 6.1 using the 6.1

SP1 install. Versions older than 6.0 are not supported. As with all upgrades, it is

recommended that you make a full backup of your data prior to upgrading. For

more details on carrying out an upgrade, please refer to the Upgrade Guide.

Jeff

Michele Gaw and I are thrilled to be working on this. No sarcasm there at all. I'm not sure who on my local support team could help or who my local support team would be. I'll email sagecrmteam today. Any suggestions for how you would handle this migration/upgrade? Cliff notes version.

We were planning to first migrate the old instance to the new, powerful server and then starting to upgrade on the new server. My fear is the old version won't open or run in the new environment (due to the the versions of the supporting software) so we will start out "broken". We won't know what is "breaking" as we move it up a version.

Amanda

I went through an epic upgrade from an unpatched 6.0 through to 7.3 and it was a nightmare. Sorry to give you some bad news on that. I have copies of CRM dating back to 5.7 and pretty much all the patches that go with it.

Getting 6.1 up and running, you can do that on a 2008 machine. It *might* accept a SQL 2008 install, but it could need SQL 2005. Depending on how big the database is you can find copies of SQL Management Studio to install with the Express install that you can put onto the machine quite easily.

There are a number of problems that you will hit. The first is the schema change with phone numbers and email addresses. I think this happened between 6.2 and 7.0 or maybe 7.0 to 7.1, I can't recall without looking through my archives. That causes a lot of headaches and the fix is somewhat manual and if there are a lot of duplications, then it's a long process.

The biggest problem you'll hit will be around 7.0 to 7.1 or 7.1 to 7.2 where you will find that you can't upgrade because the new version won't run on the version of Windows you currently have, and the old version won't install on the target system for you to do the upgrade. It's a slightly broken upgrade path. That's not to say it isn't possible. If you're going for CRM v2018 then I would suggest that you'd bill for 5 days of work and start by creating a couple of 2008 VMs and then a 2012 VM. You'll need SQL 2008 (possibly 2005), 2012 and maybe 2016 as well.

Concentrate on getting the upgrade through to the point where you get view errors. The process is manual to fix those. All custom fields in system views will need to be readded to the new views, the old views dropped and replaced with the new views. Once they're out the way, read the support matrixes because you will find one of the upgrades requires you to upgrade to (I think) 7.2 but on a system that isn't supported. Then you can install 7.2 on a supported environment, move the database, and then make the DB changes to tell CRM of the new server name. I wouldn't worry about your customisations in the system. You will need time to fix those once you get to your target system to the latest version.

It's a tricky process, but not impossible. Sadly, I didn't get a lot of help from support as the versions I was dealing with were well out of support, and also, the support team members didn't have experience of the older systems and their "quirks".

Lee