Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"

Migrating From Filenet to Content Manager OnDemand (view source)

Revision as of 12:35, 25 November 2015

104 bytes added , 12:35, 25 November 2015

m

Added quote, tweaked text.

Jderrick

Bureaucrats, Administrators

1,126

edits

@@ Line 5: / Line 5: @@
 === 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.
+<blockquote>
+"Abandon all hope, ye who enter here"
+  -- Dante's Inferno
+</blockquote>
+Large migration projects are always painful.  They take more time & money than anticipated (or more importantly, budgeted) because of one simple, honest truth:  You are re-living all of the mistakes, problems, errors, and previously 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 conversations 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.