Home Quicken for Windows File Conversion and Backup (Windows)
Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO

Exported QXF file from MAC imported it on Windows and all transactions are 100X larger

Hi, I am moving from Mac to Windows Quicken. I exported all my data from Mac to a QXF file and then imported it on Windows. However all transactions on Windows are 100X larger than its original value. Simply 00 (two zeros) have been added to all transactions. Does anyone know how I can get this fixed. I still have the Mac data file so I can do new extractions if needed. Thank you.

Answers

  • Quicken AnjaQuicken Anja Moderator mod
    Hello @g.cerqueira,

    Thank you for reaching out to the Community about your issue, though I'm sorry to hear that you are experiencing this.

    First, could you please provide which version release of Quicken Windows and Quicken Mac you currently have running?
    • WindowsHelp > About Quicken
    • MacQuicken > About Quicken
    To start with, I do recommend that you export a new QXF file as you said and import it into a new Windows data file to see if it will come through correctly. 

    Let us know how it goes!
    -Quicken Anja
  • Hello 👋 Anja. Thanks for reaching out. Both versions are the cloud subscription version, for Mac and Windows. This means I am always using the latest version of both, through my cloud subscription of Quicken. I ran the migration two times now and received the same 100X results. I hope you can help me?
  • q_lurkerq_lurker SuperUser ✭✭✭✭✭
    Just a W.A.G. since I know so little -- are both files Windows and Mac files set up using USDollars?
  • Hello 👋 the target Windows data file is a new one. I create it brand new then I import the QIX data file extracted from Mac Quicken. Therefore I would expect the new file to inherit all currency config of the original file. I have accounts in CHF, EUR and BRL. All of them are correct after import, with the exception that the transactional values are all multiplied by 100. This is clearly a formatting issue faced during the export/import process. Is there a way I can run a script to divide all transactional data by 100? This would solve the problem.
  • Quicken AnjaQuicken Anja Moderator mod
    Thank you for the update, though I apologize that you have not yet received a follow-up response.

    If you haven't already, I suggest you try is to validate your data file by following the steps below--
    1. First Save a backup of your data file (just in case) 
    2. Go to File
    3. File Operations
    4. Validate and Repair
    5. Validate File
    6. Ok
    7. Close the data log that will pop-up after the validation has completed
    8. Close Quicken
    9. Wait at least 5 seconds
    10. Reopen Quicken
    11. Try again to see if the issue reoccurs/remains the same or gets corrected
    You can also try super validating which are the same steps as above except that you will hold Ctrl and Shift on your keyboard when clicking on Validate and Repair in order to get the option for Super Validate.

    Let us know how it goes!
    -Quicken Anja
  • g.cerqueirag.cerqueira Member
    edited October 2020
    Solved the issue myself. In Mac the decimals separator was "," and in windows it was "." simple as that. The quicken agent in the live chat support told me quicken was not design to accept "," as decimals separator. I asked him "how come" since in my Mac it was exactly like that. He replied that the chat support I was logged on to was for windows not for mac! I asked him what he would advise me as a next step and he promptly answered: "go back to work on Mac", [removed-disruptive] unbelievable!
  • Quicken AnjaQuicken Anja Moderator mod
    @g.cerqueira, thank you for following up and providing an update.

    I'm happy to hear that you were able to resolve this, though I sincerely apologize for the unpleasant experience with support! Were you given a ticket number by chance? I would like to review the interaction and forward it to the proper channel so we can provide the agent with appropriate coaching to avoid this from happening in the future.

    Thank you!
    -Quicken Anja
  • q_lurkerq_lurker SuperUser ✭✭✭✭✭
    Solved the issue myself. In Mac the decimals separator was "," and in windows it was "." simple as that. ...
    I believe on the WIndows side, Quicken uses the Windows setting for regional preferences to manage the comma versus period designation.  How are those set on your Win OS?  You might be able to change that setting, make the import, then change it back.

    Or you would need to change the Mac setup to use the period delimiter, make the QXF for import into Q-Windows, then change it back.    
  • Chris_QPWChris_QPW Member ✭✭✭✭
    I asked him "how come" since in my Mac it was exactly like that.
    But it isn't like that on all Macs.  Quicken Mac takes these settings from what regional settings you have on your machine.

    q_lurker said:
    I believe on the WIndows side, Quicken uses the Windows setting for regional preferences to manage the comma versus period designation.  How are those set on your Win OS?  You might be able to change that setting, make the import, then change it back.
    In Quicken Windows doesn't use the Windows regional settings for this.
    Instead it uses the sDecimal and sThousand settings in:
    C:\ProgramData\Quicken\Config\Quicken.ini

    This definitely a bug that needs to be fixed in the QXF export/import.  They should have used a standardized format in the QXF instead of it taking on the format of what the machine is set to.  Of course this now leads to a mess where they have QXF files out there with different formats for this.
    (I'm using the latest Quicken subscription version)
  • QuickStudyQuickStudy Member ✭✭
    I was able to convert my Mac to Windows without having the 100x issue with transactions that QFW flagged as a pure bond transaction. I had to use the QIF file export and QIF (mac) file import on the QFWindows. Here's my success story on the Mac to Win conversion - years in the making.

    I was able to convert from QFM2007 to QFW subscription - but had to use the QIF file export on the Mac side in QFM 2007. Here's my successful saga:

    I was able successfully upgrade my Quicken for Mac 2007 (QFM2007) data file to Quicken for Windows (QFW) subscription (Quicken 2018 deluxe E30.10 build 27.1.30.10) running in Windows 7 SP2. I did this using many tips from other posts and boards. Overall conversion process and errors found in QFW are shown below. This conversion process will take 12-19 hours for a Quicken account with 3 bank accounts and 27 investment accounts (YMMV). - QuickStudy

    Conversion process:
    1. QFM2007 side
    a. Update the QFM2007 file with all of your securities (shares up-to-date)
    b. Update the security (share) price by syncing with the Quicken server in QFM2007
    c. Backup this file
    d. Export the updated QFM2007 file using the QIF file format export feature (for safety sake I used a filename format of 8 characters with .qif file extension; example: johndoeQ.qif)
    i. My Account and QIF file contained 3 bank accounts and 27 investment accounts
    2. QFW side
    a. Transfer a copy of the QIF file to Windows to a folder of your choice
    b. Download the QIF file fixer program CLEANQIF from http://www.quicknperlwiz.com (at http://www.quicknperlwiz.com/cleanqif.html)
    c. Fix the Mac QIF file for known date formatting issues
    i. Drop the QIF file onto the CLEANQIF.exe application to create a new date-fixed QIF file with the correct Windows date formatting within that QIF file
    ii. Save the new QIF file
    iii. (If you do not fix the QIF file dates – all QFW side converted transactions will be in year 19xx dating (example: a transaction occurring in QFM2007 on 3/26/2009 will be shown in QFW as 3/26/1909 and therefore the IRR/NPV and all other time-based investment performance calculations are wrong in QFW with the incorrect dating. Y2K)
    d. Create a backup copy of this fixed QIF file
    e. Launch QFW and create a New Account
    f. Import the date-corrected QIF file
    i. Select Yes for each sub account in the QIF file to import all accounts (bank and investment accounts)
    g. Review and compare each account in QFW with the original QFM2007 account
    h. Adjust cash balances to your original QFM2007 account using the appropriate transaction
    i. (I used Misc. transaction in QFW to make a deposit or payment to a fictitious payee in order to get the QFW cash balance to = QFM2007 cash balance in each sub-account)
    i. Save a copy of this new QFW file (quicken data file format .QDF file extension) in File Explorer to your backup drive
    j. Have QFW make a backup of this Quicken data file (QDF file)
    k. Review all (sub) accounts for share amount, account designation (retirement/IRA, taxable/non-taxable, and the like).
    Issues found on the QFW-side after the conversion process:
    1. Cash balances in each investment (sub) account were VERY different than each QFM2007 (sub) account
    a. In most examples there was a $0.00 cash balance in the QFM2007 account and the QFW account had negative or positive cash balances
    i. (QFW accounts had about ~4-9 % of the account value as a different cash balance in QFW as compared to the QFM2007 account)
    2. Cash balances in the bank accounts was closer but did not match the same QFM2007 bank account balance
    3. Stock tickers were missing on all (each) security in QFW and had to be manually added back.
    a. Click on the security in QFW
    b. Update the ticker symbol
    c. Check the Asset Allocation box so that the allocation amounts sync
    d. Update the security historical prices (syncs historical prices and allocation)
    e. (Oddly the QFM Subscription version 5.18.2 build 518.35919.100 imported QIF file running on a separate Mac (2014-era operating OS X El Capitan 10.11) was pristine match for QFM2007 file cash and share balances and working ticker symbols)
    4. Account gains and investment performances were slightly different in QFW than the QFM2007 (and QFM subscription converted files).
    a. Not sure how to get QFW to equal the performance metrics from QFM2007
    5. Account designations were not correct in QFW (retirement/IRA)
    a. (Oddly the QFM Subscription version 5.18.2 build 518.35919.100 imported QIF file running on a separate Mac (2014-era operating OS X El Capitan 10.11) was pristine match for account designations like Retirement)
    References:
    • https://www.quicken.com/support/converting-your-data-quicken-mac
    • https://community.quicken.com/discussion/7869495/qif-file-import-dates-in-wrong-century-1917-vs-2017
    • https://community.quicken.com/discussion/comment/20132379#Comment_20132379
    • Me - https://community.quicken.com/profile/QuickStudy
    /// passionate about saving for life and the future ///
  • Chris_QPWChris_QPW Member ✭✭✭✭
    @QuickStudy Please note that the newer versions of Quicken Mac don't export QIF files, so you method would only apply to people using Quicken Mac 2007 or below.

    But thanks for posting this procedure that worked for you.
    (I'm using the latest Quicken subscription version)
Sign In or Register to comment.