• From: Apia, Samoa
  • Registered: 04/21/2015
  • Posts: 14

Topic: Sensible 2.4 Migration Plan?

Our client is using 2.3.24 now and needs the upcoming monthly close feature in 2.4.x. Below is our migration plan. Is it sensible? Any recommendations to make it better?

- financial year is 1 Jul 2014 - 30 Jun 2015
- client will continue to use their manual system to finish this year
- we're re-entering past transactions into FA, so not having a monthly close feature is not hurting us
- we use FA in parallel with old system for new transactions
- we update FA to 2.4 when available
- we use this time to skill-up the team on FA, do a nice yearly close, and move into the next year clean
- FA 2.4.x becomes official system of record for this next financial year (1 Jul 2015 - 30 Jun 2016)

Note: The entry of past transactions and parallel operation is something the client feels strongly about to give them confidence that FA can handle their workload... which looks great so far.

genebarker's Website

  • From: Singapore, India, Chennai
  • Registered: 05/02/2009
  • Posts: 6,160

Re: Sensible 2.4 Migration Plan?

Sounds great. Regular Backups with a manual computing journal of activities and comparison of the backups will help during the skilling-up phase. How do you handle wrong entries - using new contra entries or just making changes in the raw db tables?

Making the FA period just 1 month instead of a full fiscal year or a dummy accounting year shifting one month forwards each month on restoration will help simulate closing month by closing dummy year.

The devs can put out a list of new features in FA 2.4 that will help users in deciding if and when to update.

apmuthu's Website