Transfer Process for Database to New Hosting Site
Transfer Process for Database to New Hosting Site
Hello everyone, I have a significant challenge ahead. Our organization needs to move hundreds of Windows 2012 servers onto newer 2019/2022 systems. A key concern is easing the transition for users who are unsure about moving their software. We already have several migration options, but we're also exploring third-party tools that can handle server-to-server app transfers. Since I'm still getting familiar with app migration, I'd like to clarify what I mean: moving all or selected applications from the old servers to the new ones—ideally through a network connection, as our infrastructure uses virtual machines. This means fully installing the apps on the new servers so they function just like before. I suspect some features might not work perfectly and will require manual setup. Potential issues include apps relying on host machine names, license settings tied to hardware identifiers, or tricky registry entries that can't be copied correctly. Certain applications are likely to fail or need special handling. I'm not confident a perfect solution exists, but I'm looking for recommendations or tools that could simplify this process. Any suggestions or experiences you have would be greatly appreciated. Thanks in advance.
I plan to perform an in-place upgrade from 2012 to 2022. First, take a snapshot—it usually works well and is the smoothest method. If that doesn’t fit, reach out to app vendors for assistance, as it seems to be the most reliable path. If neither is possible, use the installer you have or copy the existing files. You can also track what programs read by monitoring registry keys and transfer those to the new system.
Hi, thank you for sharing this. Essentially, our business interacts with a wide variety of suppliers. The sheer number makes it difficult to reach out to each one individually for the migration strategy. Our team is small while the user base is large. Senior engineers have voiced concerns about implementing an in-place upgrade, particularly transitioning from 2012(r2) to newer versions like 2019 or 2022. They seem to have encountered similar challenges before. This could be our final option, but I’m exploring third-party solutions that might offer a more reliable alternative. One of our other backup plans is to force users to reinstall their apps manually, though this isn’t ideal given the size of our organization and the fact many older applications are no longer supported. Note: I’m referring to specialized or custom tools rather than standard commercial software like Adobe or office suites. Some applications are niche or tailored for specific needs. Appreciate your feedback and any additional details that could help shape this effort.
1: UAT is required before moving forward. Do nothing in production until the upgrade has been verified in UAT first. This project demands thorough checks and oversight to confirm all goals are met, including risk management strategies.
2. It’s a large undertaking—don’t rush. A simple press of a few buttons won’t suffice. From a technical standpoint, it might seem straightforward, but corporate initiatives require careful evaluation, safeguards, and monitoring to meet defined objectives and manage potential risks.
3. Always keep backups ready. If the system is critical, ensure you have a reliable recovery plan. Whether restoring from a snapshot or backup, having a clear strategy is essential.
4. User concerns are normal, but they shouldn’t halt progress. I’ve seen firsthand how ignoring user feedback can stall progress significantly. Securing management support is crucial; once they’re on board, the rest will follow or at least remain silent.
5. The advice from @sweaton is spot on. Proceed step by step, and don’t rely solely on one app at a time. Vendors often aren’t reliable partners for seamless transitions—be ready to handle support costs or depend on your own expertise.
6. Before making any changes in production, go through the exact procedure in writing. The “LIVE” phase should follow a predefined checklist, executed confidently without hesitation.
7. Involve someone else during the live process who is fully informed of the steps. This ensures continuity and accuracy, preventing accidental mistakes like mistakenly deleting critical files.
8. Upgrading directly is usually the safest option. If third-party software resists this change, consider installing it from the ground up. Migrating legacy systems—especially those using proprietary code—is extremely challenging and can lead to unexpected issues. The only secure path is a complete reinstall aligned with vendor guidelines.