An object on a custom form could not be converted" during Sage 50 conversion
Sage 50 could not carry over a layout element on a custom invoice, check, or form during a conversion or migration.
When Sage 50 reports that “During conversion, an object on a custom form could not be converted,” it means the conversion process hit a layout element on a custom form (an invoice, check, statement, or similar template) that it could not map to the destination format. The wording sounds alarming, but the core financial data, your accounts, customers, vendors, and transactions are usually fine. The problem is confined to the visual design layer of your custom forms.
What “object” means here
In Sage 50, a custom form is built from individual elements: text labels, logo images, data fields, lines, boxes, and column definitions. During a conversion, the software walks through each element on every custom layout and tries to recreate it in the target. An “object” is any one of those individual elements. When the converter encounters one it does not recognize or cannot place, it skips that element and posts this message.
Why it happens
The most common cause is a version or edition gap. A form designed in an older release of Sage 50, or in a higher tier (such as Quantum), may use features, field types, or layout controls that a different version or a different product (such as QuickBooks) simply does not have. The converter can read the object but has nowhere to put it. Structural corruption inside the form layout itself can also trigger the message: the object definition is present but internally inconsistent, so the converter abandons it rather than guessing where it belongs.
Rebuild the form in the destination
If only one or two custom forms are affected and the layouts are simple, the fastest path is to let the conversion finish and then recreate the forms manually in the destination program using its own form designer. Most custom forms are a logo, a return-address block, a few remittance lines, and column adjustments. Recreating those from scratch in the target product is often quicker than troubleshooting the conversion.
Check the source file for form corruption
If the message appears on many forms, or if the conversion also drops transactions or lists, the source file may have deeper structural damage that goes beyond the form layout. In that case, rebuilding forms in the destination will not help because the conversion itself is unreliable. The source database needs to be examined and repaired before another conversion attempt.
When professional help is the right call
When the conversion is large, the custom forms are complex, or the message appears alongside other errors, the safest route is to have our engineers evaluate the source file directly. We can determine whether the issue is isolated to form layouts or points to broader damage, and we can perform the Sage 50 to QuickBooks conversion or a Sage 50 database repair so that both the data and the form designs come through cleanly. The cost and turnaround depend entirely on what is inside your file, so we offer a free evaluation and quote before any work begins.