Welcome
Login

Conversion Limitations Sage Peachtree

We are aiming to cover all the possible scenarios of your source accounting system when converting it to the new system. However, the systems subtly vary on how they are handle accounting, and it is not always possible to convert everything and for all your accounting period. It is important you take your time to understand the limitations of our service.

Learn more about conversion limitations for all systems.

Apart from the limitations listed in the article linked above, Sage Peachtree also has the following limitations:

Cash refunds and cheque refunds will be posted as journals

Quickbooks Online does not support refunding a cash payment or cheque from a supplier. So these entries will be posted as regular journals with no link back to the customer or supplier.

Checking your conversion

To check your conversion, please use the dates provided by Peachtree for the end of the periods and compare them with Quickbooks Online. Suppose you want to compare period 1 to period 12, which ends at 2020/12/31, do not compare with dates like 2020/12/14 in Quickbooks Online. This has to do with Quickbooks reporting on dates and Sage Peachtree reporting on periods. In some cases Dataswitcher might merge certain inventory journals and post them on the first of a period. That means the overall period details will be correct, but on a day to day comparison there might be discrepancies. 

Reversed journals will not be posted

All reversed journals will not be posted.

Some accounts receivable and payables transactions, might not be posted as you expect

In Sage Peachtree, you are able to specify an accounts receivable (AR) or accounts payable (AP) account per transaction. This is not supported in Quickbooks Online. Furthermore, Quickbooks Online only supports the usage of a single system account for AP and AR. This can cause the following issues which need to be resolved post conversion:

  1. Dataswitcher will move money that has the non-standard accounts payable or receivable to the central AR or AP account in Quickbooks, for example you have used Petty Cash once for a single AR transaction, that transaction will be moved to the AR account, this will be logged in the conversion log so you can still verify the migration. Dataswitcher needs to do this to agree your AR report
  2. In Quickbooks Online using a customer or supplier on a AR or AP accounts is mandatory. If you have used the AR and AP accounts directly, this money will be used to zVendor or zCustomer, it might also remain on the old account from Sage Peachtree and has to be cleared post conversion
  3. Sage Peachtree does not verify the types of these AR and AP accounts per transaction. This means you can use:
    1. An liability account as an AR account
    2. An asset account as a AP account
    3. A profit and loss account as a AR or AP account
  4. If you have any of the scenarios mentioned under point 3, this might cause issues in your balance sheet because money can be moved between the sections of the balance sheet (but, unless you have scenario 3, your overall balance sheet should be correct, data just might have moved between sections). This will also be logged in the migration report. In such situations, Dataswitcher will always give precedence to giving you a correct AR or AP report. Because formally in some of these situations, either the signs need to be reversed in the balance sheet, or in the AR or AP report. 

In all these cases please refer back to the attached migration report which is under Vendors > Dataswitcher > Vendor Details > report.pdf. This holds a total count of all the money that has been moved. If you had no scenarios under 3. your overall balance sheet should still be correct.  

The main reason Dataswitcher chooses this approach is because it will save you a lot of time when you start to use Quickbooks Online. If we would use the original accounts you would periodically need to clear them by making manual journals. This is due to Quickbooks Online always posting to the default AR and AP accounts. In this case, sticking to the AR/AP approach that Peachtree uses would yield major extra work to get your old AR and AP accounts balanced.

If your file fails the Data Integrity Check in Sage Peachtree

If your file fails the Data Integrity check (Help > Support Utilities > Integrity Check) you might experience several issues during the conversion. Including but not limited to:

  • Balances on zCustomer or zVendor
  • Non-matching trial balances for several years

Overall, the end result of the migration should be ok, but there might be slight discrepancies in previous years.

Foreign data will be converted in home-currency

All foreign currency data, is converted in home-currency. The historical exchange rate in Sage Peachtree will be used to do the conversion.

Check your open equity account

In Sage Peachtree you can setup an opening balance for an account. In some cases, (especially when the file is relatively new - or you have never run a close of year before) Dataswitcher cannot reconstruct the account used for creating that opening balance (often it is retained earnings). That is why Dataswitcher will create the opening balance transaction, and will send the net result to the the open equity account in the destination system. This can also happen if your file had consistency issues (assets did not agree with liabilities and equity).

Items and stock

Dataswitcher does not post a lot of fields for items and stock. Only code, stock code, location, name and description are posted. Current stock and purchase and sales price are also posted. Income and asset accounts are not posted to Quickbooks. We can however deliver you a set of files (the database tables from Sage Peachtree) which you can import manually into Quickbooks Online.

Positions for COA numbers

Quickbooks does not support chart of account numbers that exceed the length of 7. If you have accounts in your chart of accounts which are 7 or longer, the migration will fail. If you are using a lot of linked accounts, the migration might also fail. 

Renaming of Sage Peachtree system accounts

We can support renaming of normal balance sheet accounts, but renaming the system accounts (Retained Earnings, Accounts Receivable, Accounts Payable, etc.) through the history can cause issues - suspense accounts showing up as zCustomers or Zvendors, after the conversion.

Information, if available in Sage Peachtree, that cannot be converted

  1. Bank Reconciliation (You will need to do a single bank reconciliation after the conversion. You should know how to do this.)
  2. Paychecks are converted as Journal Entries (Importing Paychecks is not supported by Quickbooks)
  3. Employee YTD information
  4. Employee Payroll setup data is not converted (Sick Pay, Vacation, Direct Deposit information, Pay rates, Tax setup including Withholdings, Deductions, etc.)
  5. Individual employee wage or deduction information
  6. Custom templates
  7. Jobs that are not attached to transactions
  8. Budgets
  9. Fixed Asset Items (This is only applicable if your Sage Peachtree data file is linked to Sage Peachtree Fixed Assets)
  10. Work Tickets
  11. Posting and Non-posting transactions after the current date are not converted
  12. Closed or partially closed Sales Orders, Purchase Orders, and Estimate
  13. Sales Tax items are converted to Quickbooks but Customer Sales Tax defaults are not assigned to customers.

You have to map every available field in Sage Peachtree to the corresponding field in Quickbooks. In some cases, fields are not compatible and are not transferred over. You will need to manually enter such fields after the conversion. Examples of such fields are vendor default account numbers, preferred vendors for inventory, multiple shipping addresses for customers, and default Customer Sales Tax settings.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.