Copy link to clipboard
Copied
We are recently migrating to cold fusion 2016. We were running an old CF 2004 server believe it or not. We invested in a new dedicated server running cold fusion 2016 to transfer all of our data over.
The main question is:
1) How can you tell that your data center is using the CF 2016 edition of the server we now own? bought and paid for. We know builtwith.com is a good tool to cross check technologies but is there a sure way to identify that the server is running cold fusion 2016.? What is the best way to get proof?
In the process, we talked with 2 CF based companies to do the transfer both said it would take approximately 2 weeks to complete - stand up the server and migrate our software platform , websites and data over which we provided the original instructional database of how the software works in CF. We decided to keep our long relationship current vendor 14 years. We paid in full October 1st which included hosting up to 14 months, they said upfront they could not start this project until November 1st which was ok with us.
Questions:
1) How long typically should this take just to stand up the 2016 server fully running by itself?
2) Software transfer and websites. This is a tricky one without understanding the scope of work but an estimate of copying data over CF 2004 to CF 2016? We understand you may need more detail but standard MySQL and Navicat databases.
We appreciate any positive feedback. Thanks.
Copy link to clipboard
Copied
You can set up a test page and CFDUMP the #CGI# scope. That should tell you which version of CF is running on the server.
Just remember to REMOVE the page when you are ready to launch, if it's a public page. You do NOT want that information made freely available.
HTH,
^ _ ^
Copy link to clipboard
Copied
ColdFusionCop wrote
CF 2004 to CF 2016?
CF 2004? As far as I know, there has never been a CF 2004. The recent versions of ColdFusion before 2016 are 11, 10, 9, 8 and 7(which came out in 2005).
Copy link to clipboard
Copied
Regardless, there are a lot of things that have been deprecated since 2005, so this will NOT be an easy transition. Not to mention all the security that has been added, including oWasp ESAPI, and everything else. I do not envy the OP.
V/r,
^ _ ^
Copy link to clipboard
Copied
7 2005 Correct
Copy link to clipboard
Copied
1) Treat this as a project and follow the usual steps in a project plan.
2) Provided all the relevant information is available, it should take an experienced developer 2 working days to set ColdFusion 2016 up.
3) Transferring from CF MX7 to CF 2016, testing and rolling out to production should take between 5 and 10 days for 2 Engineers.