1,126
edits
Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"
Jump to navigation
Jump to search
m
Migrating From Filenet to Content Manager OnDemand (view source)
Revision as of 11:40, 3 November 2015
, 11:40, 3 November 2015Added the warning.
m (Added empty directories bit.) |
m (Added the warning.) |
||
| Line 3: | Line 3: | ||
These are some recommendations and tips from my experiences migrating Filenet data to Content Manager OnDemand - since I'm not a Filenet admin, Filenet is outside the scope of this article -- this only deals with the OnDemand-specific tips and tricks to make your migration easier. | These are some recommendations and tips from my experiences migrating Filenet data to Content Manager OnDemand - since I'm not a Filenet admin, Filenet is outside the scope of this article -- this only deals with the OnDemand-specific tips and tricks to make your migration easier. | ||
=== A Warning === | |||
Large migration projects are always painful. They take more time than anticipated (or more importantly, budgeted) because of one simple, honest truth: You are re-living all of the mistakes, problems, errors, and until-now undiscovered issues with potentially '''decades''' of information. A lot of the 'institutional knowledge' surrounding specific data, reports, or use-cases is long gone. Especially frustrating are the questions that end in "So, why did you think they did ''THAT'' ?!?!?", because it's not always obvious what the situation was when critical decisions were made. | |||
Patience is a virtue, and any sufficiently large migration project will test your determination, and at times, your sanity. The advice below comes from one of the largest migration projects I've ever participated in. | |||
== Nomenclature == | == Nomenclature == | ||