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.
Sage 50 "This account cannot be deleted because it is used for General Ledger Defaults
Sage 50 is blocking deletion because the account is wired into your company-wide default settings and must be unlinked first.
Sage 50Sage 50 "These accounts cannot be merged because they do not meet the merge conditions
Sage 50 is refusing to combine two accounts because their type, structure, or history conflicts with what the merge tool requires.
Sage 50Sage 50 "The file you are trying to save is a read-only file
Sage 50 cannot write changes because the company file is marked read-only at the Windows level, blocking all saves.
Sage 50Sage 50 "limit for the number of transactions to display has been reached
Sage 50 is refusing to show a batch of transactions because the company file has grown too large for the display buffer to load them.
Sage 50Sage 50 "ledger cannot leave History Mode" because General Ledger is incomplete
Sage 50 is blocking you from closing History Mode because required historical General Ledger data is missing or damaged.
Sage 50Sage 50 "invalid inventory item reference" on a transaction
Sage 50 is pointing to an inventory item that is missing, deleted, or corrupted inside the company file, blocking the transaction.
Sage 50Sage 50 "duplicate reference number" error when saving a transaction
Sage 50 is blocking your save because the reference field matches a transaction already in the file, even when the two are unrelated.
Sage 50Sage 50 "costing method cannot be changed once inventory items have been converted
Sage 50 locks your inventory costing method after any item is converted, preventing a switch between FIFO, average, or LIFO.
Sage 50Referenced Customer or Vendor cannot be changed" — Sage 50 error
Sage 50 blocks you from changing a customer or vendor name on a transaction that is already linked to other posted entries.
Sage 50Phase record number of the transaction line is not valid" (Sage 50)
Sage 50 is reporting internal data corruption in a transaction line, usually meaning the file has structural damage needing repair.
Sage 50Not a Sage 50 form, or it may have been corrupted" error explained
Sage 50 cannot read the form file you selected, usually because the format is wrong or the file is damaged.
Sage 50Master stock item can not be used on a transaction" — Sage 50 error
Sage 50 blocks a master or template stock item from being placed directly on an invoice, PO, or other transaction because it is not a sellable item.