1 of 1 people found this helpful
It's a great question to ask, and it's good that you're thinking about it.
A few things to consider...
- The more work you put into developing your v11 environment.. the more work you'll need to put into developing your v12 environment. It's not an exact science, but it's generally the case.
- Especially if you are rolling out to customers, is it better to roll them out on v11, and then later have to re-train / re-show them how to use v12?
- Is your organization at a time where they are able and ready to review processes if needed?
-- Is your organization happy with the way the current processes and procedures are implemented?
Generally my recommendation is that unless there is a core critical feature from v11 you need that is not yet available in v12, there is no reason to wait any length of time. The longer you wait, the more you risk having the endeavour be more complicated or time consuming or costly (mostly, because of my first bullet above).
From your standpoint on v11, there are really 3 ways you can go to v12:
1) You can use the BMC AMIGO program and tools to migrate your environment from v11 to v12. There are caveats and pitfalls here. It is generally the quicker and cheaper way to do this, but AMIGO wont handle everything. It won't take full advantage of the new architecture of v12, and if you're at all un-happy with the way you do things in v11... it won't change in v12. Granted nothing prevents you from changing afterwards, but it's not super clean.
2) You can start fresh with v12, and build it up to your exacting specifications. This is generally the "ideal" way because it allows you to update your processes at the same time as designing your system specifically to you. The problem is, this is very time consuming (and therefore costly) and you likely may not have the knowledge or expertise to do it yourself. There are plenty of resources to help you, here on Communities, your Support Provider, and mostly, your Consulting Services Partner.
3) My generally preferred method of migrating to v12 is through our FootPrints Advanced Starter Template (FAST) offering. It's sort of a hybrid of the two approaches. It gives you a pre-built, pre-configured v12 environment with many ITIL aligned processes (and many others) included, but still allows you to configure the environment to your needs afterwards. Similar to using the pre-build ITSM Business Process within FootPrints that BMC provides, but FAST takes it 3 levels higher.
What it comes down to is this:
- How happy are you with your current setup?
- How important is it to improve/mature/change your current processes? (Because a product migration is really the best time to do this)
- How quickly or cheaply do you need this to be?
I can kind of think back to the old PC-building triangle. If you've never built your own PC at home, you might remember the old saying:
"Cheap, Fast, Reliable.... pick two"
You can build a reliable and fast PC, but it wont be cheap. You can build a cheap and fast PC, but it wont be reliable.
That sort of translates to product implementation as well.
Here are some other posts on the BMC community about the transition. I strongly encourage you to at least skim them to get yourself a better idea. Feel free to follow up with any questions you may have.
I am trying to find a document that shows the features of 11.6.04 versus newer versions of Footprints Service Core?
Has anyone upgraded Footprints from Version 11.5 to Version 12 and had a good experience?
Is V12 Really a free upgrade?
Which is better: Upgrade to or Clean Install of FPSC v12
What do you like most about FP12? What do you like least? Did you upgrade from a previous version? What was your experience?
Round Robin Assignment in FP12.1.01.001
Footprints v11 vs v12
Upgrade to v12 or Create CMDB: Which first?
Upgrade from FPSC 11.6 to 12.1
Migration path from FP 10.0.2 to v12
Ticket relationships not migrated to FP12
A few other links you can read up on:
As for your 11.6.10.002 support question, I don't think there's a formal answer to that yet. While BMC is developing and supporting the v12 branch of FootPrints, they are also still supporting (though not developing) the 11.6.x branch. BMC has not yet announced an EOL date for 11.x.
Thank you Nicolas, this is very helpful. It will certainly help our decision making process.
I suspect FP11 will remain "on support" for as long as FP12 does. It still has a fairly large installed base.
Hi Nicolas. I'm looking for the latest version of Migration11to12_ItemsNotMigrated.xls
Can you help?
From my experience footprints 11.6 has a lot of features not available in 12.x , so stay with 11.6 at least this period .
It's also true the other way around. There are a lot of features in post-12 that are not available in v11 and prior. The best way to view this - IMO - is to treat FootPrints pre-12 and FootPrints post-12 as separate products. You'll never have complete feature parity.