PS: I can verify that backups have been created for some of the neo-*.xml files, e.g. for neo-datasource.xml, but there have not been been any changes to these files, so the settings from the files in the cf2016settings folder have not been applied.
Since the migration wizard did not work, I had to export the server settings from CF2016 as as CAR file (as described in the CF2025 Migration Guide).
When importing the CAR file in CF2025, I had to add a deploypath in pathfilter.json
{
"comments": "paths should be semi-colon seperated. To Allow a file: {path-of-file}; To Allow a directory & files in it: {path-to-directory}/*; To Allow a directory & sub-directories: {path-to-directory}/**; To Block a file: !{path-of-file}; To Block a directory & sub-directories: !{path-to-directory}/**; Precedence decreases from left to right. Suppose directory A has directory B & C inside it.To Allow B & Block C: !A/C/*;A/**;",
"bytecodeexecutionpaths": "",
"schedulerexecutionpaths": "",
"car": {
"deploypath": "C:\\ColdFusion2025\\cf2016settings.car",
"associatedfiles": ""
}
}
and disable popup blocker for the CF2025 administration site to make the import work.
AdChoices