The conversion log reports what could not be converted to Sage 50
Sage 50 finished importing your data but skipped records it could not map, and the log lists each item that did not make it across.
When Sage 50 tells you that “The conversion log reports what could not be converted to Sage 50,” it is letting you know that the import or migration process has completed but that certain records, transactions, or list entries were left behind. The conversion did not fail outright — it ran to completion and produced a log file detailing everything that could not be brought across. The message itself is essentially a pointer to that log so you can review the gaps.
What the log typically contains
The conversion log is a plain-text record of every item the converter could not map into a Sage 50 equivalent. Common entries include transactions with fields Sage 50 has no counterpart for, list entries (customers, vendors, employees, inventory items) that violate a Sage 50 naming or structure rule, records referencing accounts or classes that do not exist in the destination, and dated transactions that fall outside the accepted range. Each line usually identifies the record type and a short reason.
Review the log and assess the gaps
Open the conversion log and read through the skipped items. In many cases the omissions are minor — a handful of old transactions or a few inactive customers — and you can enter them manually or decide they are not needed. If the log is short and the missing records are identifiable, manual re-entry may be the fastest path forward. Make note of any patterns, such as all skipped items sharing the same account reference, because that can point to a fixable mapping problem you can correct and then re-run the conversion.
Re-run the conversion after correcting the source data
If the log reveals a systematic issue — account names that do not match, unsupported transaction types, or formatting problems in the source file — you may be able to clean up the original data and attempt the conversion again. This is only practical when the source file is still accessible and the number of corrections is manageable. If the source is a Sage 50 or Simply Accounting file being moved between versions, or a Peachtree file being upgraded, the conversion path and what can be fixed will depend on the specific file involved.
When the skipped data is too large or too important to lose
If the log is long, or if it includes critical history such as open invoices, payroll records, or inventory valuation, manual re-entry is rarely a safe option. Missing transaction history means your beginning balances and reports will not tie out, and reconstructing that data by hand introduces the risk of accounting errors. In that situation the file needs professional conversion help to recover the skipped records and get them properly mapped.
We regularly work with Sage 50, Peachtree, and Simply Accounting files where the built-in converter has dropped data. Our engineers can evaluate your conversion log and source file to determine what was lost and whether those records can be recovered. Send us the log and the original file for a free evaluation and we will tell you what is recoverable.