Tracking Transactions During a QuickBooks Data Conversion Window

New activity entered in your source system while a conversion is underway will not appear in the delivered file unless you track and re-enter it manually.

When we convert your accounting data into QuickBooks, we work from a snapshot taken at a specific point in time. The conversion process is not a live sync. Any transaction you enter, edit, or delete in your source system after that snapshot is captured will not appear in the converted QuickBooks file. To avoid losing activity, you need a reliable method for tracking everything that happens during the conversion window and re-entering it once the converted file is delivered.

Establish a Cutoff Point

The conversion window begins on the date we extract or receive your source data. Record this date precisely. Every transaction dated on or after that cutoff must be tracked for re-entry. Communicate the cutoff to anyone in your organization who enters data into the source system, including bookkeepers, accounts payable staff, and sales personnel. If your team continues using the source system for daily operations during the conversion, they must understand that none of their new entries will carry over automatically.

Track New Activity

The simplest approach is to maintain a separate spreadsheet or log for the duration of the conversion window. For each transaction, capture the date, vendor or customer name, account affected, amount, memo, and document number. If you process payroll, include pay period end dates, check numbers, and gross-to-net details. If you manage inventory, record item quantities, costs, and the receiving or adjustment references.

Some source systems let you filter transactions by entry date rather than transaction date. If yours does, run a report filtered to the entry-date cutoff at least weekly during the conversion. This catches transactions back-dated to a prior period, which are easy to miss when tracking by transaction date alone.

If your source system supports it, printing or exporting a transaction detail report at the cutoff gives you a baseline. Running the same report at delivery lets you diff the two and identify exactly what was added in between.

What to Re-enter in the Converted File

Once we deliver the converted QuickBooks file, compare your tracking log against the file before resuming normal entry. Re-enter each tracked transaction in date order. Common categories include:

• Invoices and sales receipts — verify customer balances match the source system after entry.
• Bills and bill payments — confirm accounts payable aging agrees.
• Deposits and customer payments — reconcile against bank activity to avoid duplicate entries.
• Payroll — re-enter each pay run with the same check numbers and earnings details.
• Inventory adjustments — post quantity and value adjustments so item costs and on-hand counts are accurate.
• Journal entries — re-enter any manual adjustments, including depreciation, accruals, and period-end allocations.

After re-entering, run a trial balance and compare it to the source system's trial balance as of the same date. Any difference points to a missed or duplicated transaction.

When the Problem Runs Deeper

If the conversion window spans a month-end or year-end close, the volume of re-entry can be substantial, and the risk of error grows. Payroll adds complexity because tax liability accounts, year-to-date wage totals, and individual paycheck details must all reconcile precisely. If your source system uses multiple currencies or subsidiaries, the re-entry process requires careful attention to exchange rates and entity-level reporting.

In cases where the conversion window stretches beyond a few weeks, or where transaction volume is high, the tracking log can become difficult to manage. A disciplined approach — daily entry into the log, weekly reconciliation against the source system, and a final review before the converted file goes live — is what prevents gaps. For guidance on a specific conversion path, our engineers can review the source system and flag the data that needs the most attention during the window.