We are in the process of testing and customizing an AX installation. I was wondering if anyone has the knowledge of a comprehensive rollout plan that I could compare to ours? I would like to make sure that I am not forgetting anything as we approach Go Live. I realize every installation is different, but it would be nice to have some checklist to verify against.
Thank you.
Bump. This might be something interesting to lots of people that could warrant some discussion… [mention:2ad34ff1156d42a08f485895ed755b65:e9ed411860ed4f2ba0265705b8793d05], I’m looking at you!
I’m guessing that since this post was submitted over 8 years ago, that Merinaiti’s company has already gone live. Unless they’re implementing SAP, and still trying to make it… 
Nevertheless this is a great question. Many companies have their own go live checklist, and a lot of that content really depends on the type of implementation you’re on and the rollout plan agreed to by the team. Global rollouts will have a different check list for example with a template approaches than will single-instance single-company ones. Even across companies, you’ll have unique challenges based on user competency, training quality, customizations, data migration and on and on. Beyond industry or customer specifics those upgrading might have different lists from those migrating over from an older platform.
For upgrades, Microsoft offers some guidance within their SureStep methodology. I’ve attached a copy of that along with a copy of the latest upgrade manual for AX 2012. Since upgrades for AX7 aren’t allowed just yet, I can’t share anything, though I’m sure lots of discussion is on it’s way in the coming months once Microsoft releases more information.
A sample of the types of steps you’d expect to see are as follows:
Preparation for go-live:
- Finalize Microsoft Dynamics AX Solution setup.
- Make a hard copy backup of Microsoft Dynamics solution environment
- Export all of the Microsoft Dynamics solution setup files, if applicable.
- Create backup copies of the Microsoft Dynamics solution databases, if applicable.
- Perform test conversion/upgrade of data
- Complete all the steps mentioned in Microsoft Dynamics A upgrade guide
- Train end users
Conversion of financial data:
- Verify data in the legacy system
- Print applicable reports from the legacy system
- Extract data from the legacy system
Verification of financial data in Microsoft Dynamics:
-
Print financial reports in Microsoft Dynamics
- General ledger trial balance for each period and year
- AR Balances/Aging
- AP Balances/Aging
- Inventory Valuation report
- Open Sales Orders
- Open Purchase Orders
- Open Production Orders
-
Validate new system financial reports from AX 2012 against legacy system reports.
-
Verify other applicable data in the Microsoft Dynamics system
- Inventory Quantities
- Project Balances and Budgets
- Bill of Material structure.
- Human Resources (HR) benefits and deductions
- Etc…
Going live
-
Make a hard copy backup of the Microsoft Dynamics solution
-
Create a complete backup of the Microsoft Dynamics solution databases
-
Export all of the Microsoft Dynamics solution setup files, if applicable.
-
Verify adequacy of the Database Maintenance Plan
-
Validate replication functionality, if applicable.
-
Close General ledger
-
Complete final setup
This is in no way intended to be an exhaustive list. Just to get you thinking about the tasks you will need to schedule and track. But one tip is you can never start this planning too soon! Go live is a hectic time, so laying out a detailed plan always helps. Also remember that even though you might be a seasoned expert on ERP go lives, chances are the rest of your team isn’t. Communication of what to expect is the biggest benefit of this deliverable and should be at the top of any list. But I’m curious to hear what others have used. Are there any other major tasks that every go live checklist should have?
Point one on my go-live planning check list is “successfully exit UAT” and by this I mean all users to have tested all defined business processes (including customizations, integrations, output documentation printing, security and report running etc.) on migrated data and have signed off that the business can perform with the system, data and users at the current levels. I have never ever been at the point where I would mark that one as complete but I live in hope 
The rest is then detail off a skeletal plan.
You’re absolutely right Adam. If that box is checked, it’s smooth sailing. But having UAT perfectly signed off as prescribed is more rare than an omelet made from Fabergé eggs.
I think it’s hard because users (rightfully) say they need to see their full system working until they can sign off. If customization or integration work is still lingering into UAT time, usually reports can’t be signed off yet or data migration might even be incomplete. It tends to have a trickle down effect and each piece is waiting on another till truly complete.
However, I live in hope too. It’s a lonely little town where maybe just the two of us reside, though I’m always pushing for a signed and sealed UAT before kicking off go live tasks.
Thanks for the comment! Anyone else have a tip or two?