Our site go lives have historically been either Q4 or Q1. Its best to time it between financial month end closes so not necessarily on the 1st of the month.

For a customer of ours, we plan to go live on 1st of February. This due to busy schedule at finance department with the year end closing (calendar year is followed). Only one additional month of financial transactions to push through after balances are loaded.

We never advise to go live on another day then first of… This as mid month transactions are more complex to migrate/enter in new system.

We don't have legacy systems that are turned off on a certain date, but this could interfere with your planned date.

We don't intend to have a big bang, so legacy will ‘die’ slowly. Legacy system will remain open for read only/historic purposes.

Complicated factor is that there is only limited time during a weekend somewhere in the year to go live. Either you have to take the Friday or Monday in addition to the two weekend days to get everything established and checked. A detailed go live plan is a must. Each team member should know up front what to do and expect during the go live (I notice I'm drifting from the subject).

Going live first of the year may result of less users available due to holidays (depends on your location of course).

Good luck

Usually driven by Financial considerations - month end/year end/quarter end/avoid audit is always better but if you’re a seasonal business avoid busy seasons as well

If you’re choosing Jan 1 - consider the staff who may have to be working doing the cutover Post-Mince Pies/pre New Year champagne - or whatever seasonal celebrations apply. But you can also use those long weekend/Public Holidays to your advantage when the business would normally be closed and give the days back to the staff who have worked or pay overtime.  

Decide the date early and communicate to the entire business early - give an opportunity to discuss/debate but then have key parties agree the date

Build in a number of days contingency - no better positive start than announcing you’re going live early when you didn’t need the contingency.  One upgrade we did we were scheduled for 2 Jan but missed the deadline so had to put it back a week.  It wasn’t greeted with open arms but it was a better choice than the alternative of going live without key data/workflow in place. 

Regular meetings between key personnel/partners/consultants to make sure you’re on track

One person in control of the Master ‘To Do’ list/project plan

But mostly, whatever date you choose, accept the fact you will not please all of the people all of the time

Good luck! 

Looks like you’ve already received some great, thorough responses here from folks who are very active in the Community. 

I would say ultimately there is no real “best” date.  It truthfully will depend on your organization and the amount of preparation work that has transpired thus far to identify if your go live is “successful”. 

Timing can definitely lessen the challenge, but I wouldn’t say it’s the only critical factor.

If your teams (and leadership) have vetted the solution and are ready for the mountain of change that will occur post go-live, they will be able to overcome any timing hurdles. 

Good luck!

Hi,

The go-live date is generally determined by the accounting department.

My advice to you is that if you have an old ERP software, you should abandon it completely and use IFS.

If you keep both software together for a while, you will have a hard time.

In addition, the full support and patience of bosses is essential during the transition to life.
It will be inevitable to experience shipping, invoicing and collection delays during the go-live process.

I wish you ease and success in your IFS journey.