<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[FrontAccounting forum — Sensible 2.4 Migration Plan?]]></title>
	<link rel="self" href="https://frontaccounting.com/punbb/extern.php?action=feed&amp;tid=5719&amp;type=atom" />
	<updated>2015-04-27T10:30:01Z</updated>
	<generator>PunBB</generator>
	<id>https://frontaccounting.com/punbb/viewtopic.php?id=5719</id>
		<entry>
			<title type="html"><![CDATA[Re: Sensible 2.4 Migration Plan?]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?pid=23367#p23367" />
			<content type="html"><![CDATA[<p>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?</p><p>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.</p><p>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.</p>]]></content>
			<author>
				<name><![CDATA[apmuthu]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=364</uri>
			</author>
			<updated>2015-04-27T10:30:01Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?pid=23367#p23367</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Sensible 2.4 Migration Plan?]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?pid=23365#p23365" />
			<content type="html"><![CDATA[<p>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?</p><p>- financial year is 1 Jul 2014 - 30 Jun 2015<br />- client will continue to use their manual system to finish this year<br />- we&#039;re re-entering past transactions into FA, so not having a monthly close feature is not hurting us<br />- we use FA in parallel with old system for new transactions<br />- we update FA to 2.4 when available<br />- we use this time to skill-up the team on FA, do a nice yearly close, and move into the next year clean<br />- FA 2.4.x becomes official system of record for this next financial year (1 Jul 2015 - 30 Jun 2016)</p><p>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.</p>]]></content>
			<author>
				<name><![CDATA[genebarker]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=20344</uri>
			</author>
			<updated>2015-04-26T21:23:56Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?pid=23365#p23365</id>
		</entry>
</feed>
