Announcements
No record found.
Hi,
Today we had discussion if 3 months is a fast implementation? We have actually delayed with 1 month since data and organization was not ready yet. What is your experience?
J.
*This post is locked for comments
Hi Ulti,
3 months is quite quick, but also depends on the scope and complexity. Without knowing more details it is not really useful to judge on this. I have also joined complex inplementations which took over 2 years.
I would recommend with a non-fulltime core team a UAT phase of three months depending upon your schedule. So assuming you have analysis, design, process flow definition and modelling, development, data migration, training, UAT etc. I would suggest 3 months is quick. Possible but the customer has to be full time (my opinion) the processes well defined and they are using everything out of the box (even the output documentation). The moment you start to develop and have deployments it lengthens the time.
Possible, but if your question is 3 months fast for AX I would say yes. I would imagine the "average" implementation time for the "average" AX project with developments and say manufacturing is 18 months. I have also had them last 6 years because of the customer - and this is very important, it is the customers project, they need to be happy and make the decisions. The implementation partner can advise and be proactive and assist, but ultimately if the customer wants to go live in 3 months you make them aware of the risks and issues and then support them in their goal.
Last year my internal team blitzed an implementation in under 4 weeks, including data migration from a legacy system (Macola if memory serves). But, that company was especially excited and supportive, or it would not have been possible.
Edit: They were also a manufacturing company with Bills and Routes. Pure distribution companies are often much easier.
That is a fast one and I guess that the customer learnt a lot in the post go-live phase. The critical point for me is still the position, resources, goals and mindset of the customer.
With an Agile approach this can be done. The speed of the implementation is all about the resource commitment from the client and the implementation partner, necessity for customizations (or lack of) and sound project management to keep everyone aligned. We have completed recent implementations in this timeframe with lower overall cost and high customer satisfaction.
It totally depends on the project nature and its defined scope in addition with the customer resources, data and mental level.
Usually such kind of implementations would be like 3 months implementation and 2 years support program. :)
To me 3 month is a very tight schedule and depends on a scope and process complexity. In average classical AX project, if you start from scratch, it would take 3 month to make a pre-study and collect requirements, and approve it with the customer. Then preparing a Technical Design, again approving it, then developing and installations and setup, key user training, testing, making changes, user trainings, data migration scripts and testing, go-live and post go-live support... If customer is not prepared, it should take time.
However if you speak about a very straight-forward processes of the customer, that would magically fit into AX functionality, and applying Agile methods you can actually go-live with that in 3 months. But, it would anyway require additional implementation afterwards.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Joris dG 5
Andrew Jones a1x 2
GL-01081504-0 1
