🚀 Community Feedback Request: Legacy Wheels Migration Tool I’m currently developing a migration tool aimed at helping teams upgrade legacy

Wheels

applications (1.x, 2.x, and 3.x) to newer versions with less manual effort and reduced risk. To make sure the tool solves

real-world

problems, I’d love feedback from developers and organizations currently maintaining older Wheels applications. As a thank you, anyone who participates and provides detailed feedback will receive free access to the migration tool once it’s ready. A few questions: 1. What version of Wheels are you currently running? 2. How old is your application? 3. What ColdFusion/Lucee version are you using? 4. Have you ever attempted a Wheels upgrade? If yes, what challenges did you encounter? 5. What are the biggest concerns preventing an upgrade today? • Breaking changes • Lack of time/resources • Third-party plugins • Legacy code complexity • Lack of testing • Deployment risk • Other 6. Approximately how large is your application? • Number of models • Number of controllers • Estimated LOC (if known) 7. Do you have automated tests in place? 8. Are you using Docker, CI/CD, or other deployment automation? 9. Which migration tasks would you most like to automate? 10. If a migration tool could solve one major pain point for your team, what would it be? My goal is to build tooling that helps identify upgrade blockers, automate repetitive migration tasks, and provide a safer upgrade path for legacy Wheels applications. Your feedback will directly influence the roadmap and features of the migration tool. Thank you for helping make legacy Wheels upgrades easier for the entire community!