Somacon.com: Articles on websites & etc.

§ Home > Index > General Interest

Moving transactions between Quicken 2006 data files

This page describes a strategy for moving banking transactions between Quicken 2006 data files using QIF import/export via a dummy account.

Update Jan. 17, 2007: An alternative method for moving transactions is to add an "Account Header" to the exported QIF file by manually editing it. Then, it will import directly into the destination account. This method may be easier than the method described below. It is described further in this article: Import QIF Files in Quicken 2005, 2006, 2007

In Quicken 2006, Intuit has disabled QIF data import on checking, savings, credit card, 401(k), and all other brokerage accounts. They claim that QIF technology is old and the replacement technology, OFX, provides a better experience. This argument seems to be self-serving. HTML is also over a decade old, but people still use it design web pages. Intuit's real reason for disabling QIF import may be because they collect fees from financial institutions that switch to OFX technology.

Maybe the software could show a warning when using QIF, or Intuit could refuse to support customers on QIF. But my opinion is that there was no technical reason why QIF could not have been provided side-by-side with OFX. Technically savvy customers are able to work around the potential issues, such as duplicate or missing transactions.

QIF is still reliable and simple for basic functions, like moving checking, savings, and credit card transactions between data files. One can no longer directly the migrate the transactions, but there is still a way to do it, because QIF Import is still available for Cash, Asset, and Liability accounts. The procedure is described below. Warning: Intuit likely does not support this method of moving transaction data. Use it at your own risk.

  1. Make a fresh backup of the source and destination Quicken data files.
  2. Export the desired checking/savings/credit card transactions from the source data file to a QIF file.
  3. Open the destination data file, and create a new, liability account.
  4. Import the transactions from the QIF file into the liability account.
    • You can either create any new categories in advance, or let Quicken create them automatically.
    • If category names need to be mapped or altered, you can edit the QIF file before importing. Open the QIF file in any text editor like notepad or Textpad. Lines that begin with "L" are categories and "S" are categories for split transactions. All you have to do is find and replace all, e.g. replace "LBank Chrg" with "LBank Charge".
    • For transfers, make sure the transfer account exists, and uncheck the box "Special handling for transfers" so that Quicken will not skip them.
  5. Move the transactions from the temporary, liability account to the final, destination account.
  6. Double-check the balances and review the transactions to make sure everything was imported correctly.
  7. Once satisfied, you can delete the temporary, liability accounts from the destination Quicken data file.

You could also use a temporary liability or asset account to import checking, savings, or credit card transactions, where your financial institution only provides QIF export.

Links


Have you heard of the new, free Automated Feeds offered by Google Merchant Center? Learn more in Aten Software's latest blog post comparing them to traditional data feed files.
Created 2006-06-25, Last Modified 2015-09-07, © Shailesh N. Humbad
Disclaimer: This content is provided as-is. The information may be incorrect.