We are migrating away from a key production application, but I am wondering how to handle support for the remainder of the year?

We are migrating away from a key production application, but I am wondering how to handle support for the remainder of the year?

If you have done any major application migrations, how have you handled support on the legacy system?
- only break/fix support?
- no new reports?

What did you find as guidelines that worked for you?

* supportApplication ServersNetworking

Last Comment

masnrock

8/22/2022 - Mon

masnrock

4/6/2017

That is far too broad a question. Honestly, it depends on the application, whether it is still required after migration time is finished (for legacy data until no longer legally required to be retained, etc), and other factors. But break/fix would probably be a good guideline, proper maintenance (patches but no upgrades), and the like.

operationsIT

4/6/2017

ASKER

It is an ERP migration and it will no longer be used.
I want to eliminate what the team has to work on the existing ERP system to support the users and focus on system data cleanup and new system design. I am preparing a company memo to announce we will only be working break/fix and no custom design or programming.
I am wondering if I''m missing anything?

ASKER CERTIFIED SOLUTION

masnrock

4/6/2017

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

GET A PERSONALIZED SOLUTION

Ask your own question & get feedback from real experts

Find out why thousands trust the EE community with their toughest problems.

operationsIT