Mainly, you have to migrate the customizations which should not require an
awful lot, usually with the exception of the data modeling.
6.0 supports all the old codebase, so if you followed reasonable commerce
conventions, your code should migrate fairly flawlessly. You need to
recreate Entity Beans and in some cases touch Session Beans but most of the
rest should be pretty straight forward.
A day per bean would be extremely generous for someone with decent
experience with WSAD5 or RAD6 (although there are definitely significant
differences between the two environments in terms of layout and such with
WAS 6 profiles)
If you added new tabs for your accelerator customizations rather than
changing the standard pages extensively you should be able to overlay those
quickly. Depends on how your customizations were done, as to hours.
I believe your main issue will be migrating the data, since you cannot
migrate automagically between those two models, you will have to remap the
data to duplicate the linked catalog architecture used for Extended Sites vs
Hosted. This will be dozens if not hundreds of hours of work.
Additionally, by using a migrated 5.5 codebase, rather than recreating your
flow on the new commands you dont take full advantage of V6.
Post by m***@sark.comI am in the process of putting together some estimates for migrating our
5.5 Business Edition (Hosted Model) site to 6.0 Enterprise (Extended Site
Model). We have significent customizations to Accelerator and the
check-out flow. As we have hundreds of stores we have a large number of
servers deployed to support the site. I am looking for any insight from
folks who have done a migration to V6 as to what steps they went through
and how long it took. I can put together estimates for reviewing our
customizations without to much trouble, it is the rest of the tasks that I
could use the advice on.
I have already read the V6 Migration Guide so please no links to that.
Thanks