Sage Conversion Questions
Sage Conversion Questions
Short, direct answers to the questions we're asked most about Sage to QuickBooks conversions and Sage 50 Quantum downgrades.
Contains serialized items that were not serialized when the transaction was entered
Sage 50 is blocking an adjustment because serial tracking was turned on after the transaction was recorded, not because of a data error.
Sage 50Cannot void this transaction" with serialized items in Sage 50
Sage 50 blocks the void because the items were not serialized when the transaction was posted, so the history no longer matches.
Sage 50Another user has it open in the previous release" Sage 50 conversion error
Sage 50 is refusing to convert your company file because someone, or a stuck session, still has it open in the older version.
Sage 50An 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.
Sage 50Your computer firewall is blocking one of those, or all, required processes" Sage 50
Sage 50 cannot reach your company data across the network because the firewall is blocking its connection, not because the file is damaged.
Sage 50You cannot change the status of some of these transactions to Cleared" in Sage 50
Sage 50 is refusing to mark some reconciliation items as cleared, usually because of a date, balance, or data problem.
Sage 50Will my Sage 50 jobs and phases convert to QuickBooks projects?
Yes, Sage 50 jobs and phases usually map to QuickBooks Customer:Job structure, though the exact mapping depends on your file.
Sage 50Unable to open company at this time due to Sage Drive lock conflict" explained
The message means another session or device is holding the Sage Drive copy of your company, so yours cannot open it.
Sage 50Transactions posted to the general ledger in a closed year cannot be accessed or edited
Sage 50 is telling you the transaction lives in a fiscal year you already closed, so it is locked against changes.
Sage 50This invoice voids another invoice and cannot be voided" in Sage 50
Sage 50 refuses to void an invoice because that invoice is itself the voiding entry for another invoice.
Sage 50The newly inserted object could not be assigned a key by the data source" in Sage 50
Sage 50 cannot generate an internal ID for the record you just saved, which usually points to database damage.
Sage 50Sage 50 message: "This invoice has payments applied to it and cannot be voided
Sage 50 refuses to void an invoice because customer payments are linked to it; unlink or reverse them first, or adjust differently.