Migration time for migration from SC3 to SC5 ?

[gbalas]

Hi all !!

I have a migration planned in a few days but I have no idea of the time it will take ....

This migration is planned with the use of the peregrine migration tool. The customisation are very few. The database is on Oracle.

Could anybody give me some indications about the time it will take ?

Thanks a lot.

Guillaume

[outlance]

Hi,

it depends on your skills in ServiceCenter Tailoring.

I would do it in about 10 days (external costs - including
complete upgrade documentation). It would take
about minimum 8 weeks, because of the testing you have to perform.

I could do it in 5 or 6 days, but then the risk of finding a lot
of bugs after bringing into production is rising extremely.

If you just migrate data and customizings manually - without upgrade tool-
, maybe it takes 3 or 4 days, but the risk of forgetting something is rising.

In the past I have performed about 10 upgrades - always using the
upgrade tool - and what I have to say, quality of upgrade tool and
documentation has increased.

Regards from Germany,

Lars

[gbalas]

Thanks for your answer !!

Actually i'm certified on SC and very used to implementing and customizing SC.
But I've never done migrations ...

After having read the Peregrine PDF, it looks like you're right about the 10 days ....
Except the testing what could be the difficulties of migration (??) knowing that the environment we'll migrate has a ridiculous level of customisation but we have a lot of volumetry :
44000 Calls
28000 Incidents
7000 Assets

[outlance]

OK, just talking about my own experience,
when I did my first upgrade 3 years ago:

The first time it took me 4 or 5 tries only to
run the upgrade tool from beginning to the
end without error messages. The new tool
is a little bit better.

Suggestion:

Run the upgrade tool once and stop after
dbdict conflicts. Then alter the data types
of the fields with the conflict on new copy
of your production system and then restart.

Then this should work and then you can
proceed with conflict resolution.

1. compare each object that has conflicts (links, formatcrl)
therefore you need: original 3.0, original 5.0 and customized 3.0
Then find out what has been changed between 3.0 and 5.0, and 3.0 and
3.0 customized. Bring in your customizings into 5.0 object or throw 5.0
away and put in new features of 5.0 into your customized 3.0
Example: Virtual Joins can be displayed in table objects. Therefore you
have to change the format properties of subformat.
2. displayoptions conflict resolution is hard to understand if you do it the
first time. Look at file upgradedisplayoption and compare your
upgraded 3.0 with original 5.0 and original 3.0. It's important that you
have modified user condition, otherwise, your changes will get lost.
If you look at displayoptions of your upgraded system, then you will
find out, that some of them have to be deleted in your upgraded
system. Delete them, but after creating the custom upgrade and
upgrading with this custom upgrade, you will find out, that it looks the same as after
upgrading the test system. So I would reset displayopion file and load
the file from conflict resolution from commandline (scenter file.load do.unl NULL NULL winnt from RUN-directory)

3. Extensively test. Look at the issues I found while upgrading from 4.0
maybe you will find more in your upgrade (3.0 to 5.0)
4. There's more to care than the objects found by upgrade tool, because
if you created own forms (for ex. xyz.cc.incquick.g) you have to
change it too. Therefore you can look at the application profiles, which
forms are used. Or menus, maybe you have to use different
applications in your XYZ MENU........

But.... the time you spend is worth it, because you learn a lot about
internals of ServiceCenter.

Lars