An error occurred while moving current year's data to last year" in Sage 50
This Sage 50 message means the year-end close failed partway through, usually because the company data is damaged or inconsistent.
The message “An error occurred while moving current year’s data to last year.” appears during a Sage 50 year-end close. It means the software tried to roll your current-year figures into the prior year and stopped partway. The close did not finish. In plain terms, Sage 50 could not complete the year-end transition, and the data it was moving is often left in an uncertain state.
What the message actually means
Sage 50 closes a fiscal year by shifting summarized current-year balances into the prior year, clearing income and expense accounts, and preparing the new year for entries. When it hits an inconsistency mid-move, it aborts rather than write a half-closed year. The message is generic: it tells you the move failed, not why. The underlying cause is usually damaged or internally inconsistent data somewhere in the company file, and the close is simply the operation that trips over it.
Why it happens
A few patterns account for most cases we see. The company file may already be damaged from an earlier crash, a network interruption, or a bad restore. Transactions may be internally inconsistent, for example unbalanced journal entries or broken links between modules. Very large or old files with years of accumulated history can also fail the close simply because of the volume of data being rewritten. Which of these applies depends entirely on your file, and we cannot say without looking at it.
What to do first
Do not keep retrying the close. Each attempt rewrites data, and a repeated failure can leave the file in worse shape than before. Make a fresh backup copy of the company data right now, before anything else, and store it somewhere safe. Then check whether the file shows other symptoms: slow opening, odd report totals, or errors during data verification. Those signs point to damage that the year-end close exposed rather than caused.
Can the close be completed safely?
Sometimes the file is healthy enough that a repair of the underlying data lets the year-end close run through cleanly afterward. Our engineers handle this regularly: we examine the file, repair the damage, and confirm the close completes with correct opening balances for the new year. If the file is too far gone, recovery of the underlying data is still usually possible, and the books can be rebuilt or converted. If you are also considering moving to QuickBooks, a Sage 50 to QuickBooks conversion can often be done straight from the data you have now, without finishing the close first.
A useful next step
Stop retrying the close and get the file looked at. We offer a free evaluation of damaged Sage 50 and Simply Accounting databases: send us the file, and our engineers will tell you what is wrong, whether the year-end close can be completed, and what the repair would involve. There is no cost and no obligation for the assessment, and pricing or timing can only be quoted once we have seen the data. You can start with our Sage 50 database repair service page.