Proconnect destination
Lacerte to ProConnect, same vendor, same re-keying
Moving inside Intuit's own family does not spare you the fixed assets. ProConnect imports depreciation from its own spreadsheet template, and what you have from Lacerte is a printout.
Print the detailed schedule
Lacerte's summary variant combines prior §179 and prior bonus into a single prior figure. We will not split a combined number apart — a 0 written into those components breaks recapture on the first disposal — so we report them missing and flag the rows instead. The detailed print avoids all of it.
ProConnect's template is narrower than Lacerte's schedule
Seventeen columns, and only the first worksheet imports. Descriptions cap at 25 characters, so we truncate them predictably rather than letting the import silently reject a row. Five of the columns do not apply to a 1041, which is why we ask which return you are preparing.
The totals gate the file
Cost, prior depreciation and current depreciation summed from the rows have to equal the totals printed on your Lacerte schedule, per activity and in grand total, before anything downloads. It is the one check that catches a dropped row, and a dropped asset is invisible in a spreadsheet you did not type.
Questions
- Does ProConnect take the same file as Lacerte?
- No. Lacerte's Fixed Asset Import reads .CSV and .XLS but not .XLSX; ProConnect uses Intuit's 17-column depreciation template as a workbook. We build whichever one you picked.
- What about state prior depreciation?
- Neither Intuit import has a field for it. We carry it in the file we hold and show it on screen, but you will be entering it in the destination by hand — worth knowing before you plan the week.