List of Obstacles and Hindrances for Migrating from QM2007 or QWin to Quicken for Mac

  • 1
  • 15
  • Idea
  • Updated 4 weeks ago
  • (Edited)
The following list captures the features missing from current versions of Quicken for Mac that are obstacles and hindrances, preventing users of QM2007 or QWin from migrating to the latest versions of Quicken for Mac. If these areas are resolved, it would open up the path for these users to finally make a move.

To be clear, obstacles defined here refer to situations that are a complete block to migrating to Quicken for Mac, whereas hindrances are limitations that have work-arounds, though they may be far from desirable or even practical.


Links to any request for a missing feature that is an obstacle or hindrance and has been posted as an IDEA have been captured here, so you can continue to add your vote to those requests to help increase their visibility to the developers.

(Unfortunately, if missing features are not posted or are posted as problems or questions in the forum, they are not captured here as their can be multiples and therefore harder to gather (maybe that will change).)


Obstacles from QM2007 - Show-stoppers preventing migration (due to severe loss of functionality or data with no suitable work-arounds):

- In particular, these 3 report formats and related features (if designed properly, like in QM2007, these are the basis for creating most other outstanding reports missing in Quicken for Mac).

(You can read about the overaching report design here: Request for Customizable Reporting Engine)

Unsure as to whether the following are show-stoppers or hindrances
  • investment stats?

Hindrances From QM2007 - not obstacles but definitely lead to data loss
(therefore may still be a limitation to migration, even though some of which can be reconstructed)

Obstacles from QWin - show-stoppers on top of the ones listed for QM2007 (not including H&B and RPM)
For those wanting to migrate from QWin H&B, you may want to add your vote to Will there be a Quicken Home and Business for Mac in the future?

Hindrances From QWin - not obstacles but definitely lead to data loss (therefore may still be a limitation to migration, even though some of which can be reconstructed)

There are other losses of functionality that are not show-stoppers, which makes things more clumsy, but there are work-arounds; yet too many of these at the same time becomes frustrating
 and less efficient and slower to work with.

Other considerations - Being able to move data in and out of Quicken for Mac.

Though these are not obstacles to migrating to Quicken for Mac per se, they relate to to managing the risk factor of migrating to Quicken for Mac. Having the ability to move data out can give users a level of comfort and confidence that they are not locked in should something not work out after a period of usage. For these, consider the following:

BTW, if you see any other obstacles or hindrances that have not been mentioned, please add your comments below. But focus your comments on items that absolutely prevent you from migrating or a suitable work-around is not very practical.


If an incentive is required to focus on addressing these needs, Quicken should consider the untapped revenue that can help fund this effort:
  • one time new revenue from QWin migrators
  • ongoing new revenue from QM2007 migrators entering new upgrade cycles
  • ongoing new license and support revenue from FIs/Banks for Mac support (from my limited understanding on Quicken licensing and support)

The hope is that, regardless of votes these feature requests/IDEAS garner in this forum or elsewhere, the need to address these requests and the benefit to Quicken will be recognized.

If you have not already voted on the above requests, be sure to click on the each link above to go therethen click VOTE at the top of THAT page, so your vote will count for THAT feature and increase its visibility to the developers.


If you find this post helpful, please be sure to click "VOTE" above to promote this post and therefore its visibility to other users (to encourage them to vote) and to the developers.

Click "Follow" at the top if you want to receive notifications of any updates to this thread. 


Photo of smayer97

smayer97, SuperUser

  • 197,126 Points 100k badge 2x thumb

Posted 11 months ago

  • 1
  • 15
Photo of Snoopy FC

Snoopy FC

  • 5,992 Points 5k badge 2x thumb
Thanks for that summary.  I finally made the move from QM2007 when Quicken implemented 12 month budgets and haven't looked back.  I'm hoping and trusting that Quicken keeps advancing this program.  I like what I've seen so far, but there are things I still miss from QM2007 and features that I'd like to have.  Hopefully more people will make the jump and Marcus and his team keep improving this program.  
Photo of smayer97

smayer97, SuperUser

  • 197,020 Points 100k badge 2x thumb
Glad it has worked out for you. For me, coming from QM2007, my obstacles are:
  1. reports (HUGE problem) - too many types and features lacking
  2. reports carry over (I have so many...rebuilding from scratch would be painful, but they have to have equivalent capabilities first (see 1.)
  3. subclasses, and mostly the ability to batch edit newly created tags efficiently (too many in splits) to fit my needs
  4. Investment Lots management (lower problem but I would lose data moving forward)
Sure there is other functionality still missing but those are not show-stoppers. BUT I CAN'T migrate even if I want to until the 1st and 3rd are dealt with. At that point, I will have to decide how to handle 2 and 4 if they are not addressed. So for me, there is still a long way to go.
Photo of Larry Rogers

Larry Rogers

  • 248 Points 100 badge 2x thumb
Nicely summed up, I've been a Quicken for Mac user since v4, October 1991 forward. I have upgraded my wife's macbook and I'm willing to purchase QM 2017 to play and encourage future development but can not migrate until reporting is functional for our needs.
Photo of smayer97

smayer97, SuperUser

  • 197,126 Points 100k badge 2x thumb
Just to be clear on the list above, ALL show-stoppers and hindrances for QM2007 are ALSO such for QWin migrators. QWin users simply have additional show-stoppers and hindrances, as noted above.
Photo of julian

julian

  • 208 Points 100 badge 2x thumb
Correct. At least for me, having the transfer transactions between accounts in different currencies imported with the values they had in windows (not with changed values as QM17 does) would be enough for now. Anyhow I assume most of the users do not expect the wonders an automated handling anytime soon (given the different rates, fees etc.) and in any case do not expect the with transactions in the past.
Photo of julian

julian

  • 208 Points 100 badge 2x thumb
Also since my major file is the one with mixed currencies - if I don's see a fix within the 6-7 weeks I will give up this year again (I am trying for the third year in a row) and ask for my money back.
Photo of smayer97

smayer97, SuperUser

  • 197,126 Points 100k badge 2x thumb
Implementing full multi-currency support is not a small task as it touches so many areas of the program. Based on the chatter so far, I can assure you this is not something that will be addressed in such a short time. And unfortunately, Quicken rarely pre-announces features they are releasing, so there is no telling when this might be implemented.

(If you find this reply helpful, please be sure to click "Like", so others will know, thanks.)
Photo of julian

julian

  • 208 Points 100 badge 2x thumb
Importing from Qw transactions as they where entered is definitely not a big deal (I have a hard time understanding why they did what they did in QM17). The transaction and the values in every currency are already in QW. 
Photo of smayer97

smayer97, SuperUser

  • 197,126 Points 100k badge 2x thumb
True enough. This could be a good first step in to at least bring over the data until such time as they develop full multi-currency.
Photo of smayer97

smayer97, SuperUser

  • 197,126 Points 100k badge 2x thumb
Also, to my bullet about new Revenue for Quicken:
  • one time new revenue from QWin migrators
This may or may not be significant because many QWin users wanting to migrate to QMac may time it such that instead of buying their upgrade for the next version of QWin, will instead purchase the newest version of QMac. The result will be a decrease in QWin sales and an increase of QMac sales, so the net benefit may be diminished.
(Edited)
Photo of Dave in SF

Dave in SF

  • 142 Points 100 badge 2x thumb
I finally moved to Quicken for Mac 2017 last month (from QFM 2007) but it has not been a smooth transition and I continue to have problems, primarily with Quicken Bill Pay.

I had to set up a new Quicken Bill Pay account (for reasons I don't completely understand.)  But when I go to make a payment to a previously-established payee from QFM17, the application creates that payee in the new QBP account, BUT IT DOES NOT INSERT THE CORRECT ACCOUNT NUMBER, instead substituting what seems to be nonsense numbers.  If I had not gone to the QBP website and reviewed each payee, I would not have known this was happening, and all of my QBP payments would have gone astray, creating a huge mess with recipients receiving payments with no way to know where to credit them.  THIS IS A MAJOR BUG!

And I cannot find ANY way in QFM17 to view or edit the payee information, so I have to do this complicated dance, where I sent them payment, QFM creates erroneous payee information in QBP and transmits my payment.  Then I have to go log in to QBP on the web, delete the payment which was sent, edit the payee to correct the account number, then manually add the payment that I was forced to delete.

The whole interface in QFM relating to bill payment is really unfriendly and not transparent, in my opinion.  I'm glad to finally have the functionality there, but I am wishing I had not migrated from Quicken 2007.  I think QFM is still not ready for prime time.
Photo of julian

julian

  • 208 Points 100 badge 2x thumb
Importing from Qw transactions as they where entered is definitely not a big deal (I have a hard time understanding why they did what they did in )
Photo of smayer97

smayer97, SuperUser

  • 197,126 Points 100k badge 2x thumb
Need to clarify one item:
Unless the current Quicken for Mac makes changes to the way Sub-Classes from QM2007 are converted to Tags, 
Batch Editing to include changing Split transactions
should be classified as a showstopper for users like myself that will need to clean up LOTS of transactions using such things as  tags, since the new Quicken for Mac does not currently preserve sub-Classes used in QM2007 in the same way. 

(If you find this reply helpful, please be sure to click "Like", so others will know, thanks.)
Photo of JOSE L URENA

JOSE L URENA

  • 1,364 Points 1k badge 2x thumb
When I installed Quicken for Mac, the migration tool from Quicken Windows 2015 gave me terrible errors.  Account balances and share balances were way off.  Not a little, but a lot off.  Truly unusable.  Not to mention the lack of being able to transfer attachments.  I could live without attachments, but major balance errors during migration is a critical and fatal flaw.  I had to stay with the Windows version, using CrossOver, a less than satisfactory solution.  Completely unacceptable.
Photo of smayer97

smayer97, SuperUser

  • 192,934 Points 100k badge 2x thumb
Yes, as per the link above, you can add your VOTE for the Ability to link accounts to brokerage accounts.

First, click on the underlined link above to go there, then click VOTE at the top of THAT page, so your will vote count for THIS feature and increase its visibility to the developers.

While you are at it, you may want to add your VOTE to related IDEAS found on the List of Requests for Downloading Data into Quicken. Click on the underlined link, then follow the instructions to add your vote to more related ideas. 

As for placeholder entries, if they exist in your QWin data file, then presumably they have been reconciled, so would be valid and should be carried over as is. I was only speaking of NEW placeholders that may get created during migration, so it sounds on the surface that these should not be an issue.

(If you find this reply helpful, please be sure to click "Like", so others will know, thanks.)
Photo of JOSE L URENA

JOSE L URENA

  • 1,364 Points 1k badge 2x thumb
I think that the issue of migrating data from Qw with linked accounts merits its own entry among the "Obstacles".  As I said, I can live without linked accounts, but I cannot use Qm if I cannot migrate many, many years worth of Qw transaction data, because of fatal data errors. That is a critical and fatal issue for me, and I suspect, for many potential Qm users.  Thanks.
Photo of smayer97

smayer97, SuperUser

  • 192,934 Points 100k badge 2x thumb
Not sure what you mean...the IDEA request above IS the solution, as far as I understand it...to be able to bring over the linked data there needs to be the same functionality...unless you are suggesting that Quicken convert that data to eliminate linked data...(BUT that would not satisfy all migrators). Is that what you mean?
Photo of smayer97

smayer97, SuperUser

  • 192,934 Points 100k badge 2x thumb
Ok, just read your comment on the IDEA thread. So if that is what you mean, then I understand the need to explicitly point this out, though it has been Quicken's pattern (though not a guarantee) to add the data mapping to the conversion/migration tool once the functionality exists in QMac.
Photo of Bob1581

Bob1581

  • 200 Points 100 badge 2x thumb
It would also help if I knew what data was being downloaded from the investment account. What is the format for the data? Does QM17 use the same format as QW? It's hard to ask the right questions when communicating with the investment account support.
Photo of smayer97

smayer97, SuperUser

  • 197,126 Points 100k badge 2x thumb
Discovered another obstacle. So the following item needs to be added to the first list above: 
Obstacles from QM2007 - Show-stoppers preventing migration (which affects QWin users too)

Consider adding your VOTE to Add ability to handle Buy/Sell of investments and Transfer effectively.

And remember to add your votes to any of the other obstacles listed above.

First, click on the underlined link above to go there, then click VOTE at the top of THAT page, so your will vote count for THIS feature and increase its visibility to the developers by seeking to have the features you need or desire end up in the latest version.

While you are at it, you may want to add your VOTE to related IDEAS found on the List of Requests Related to Investments and/or the List of Requests for Data Entry and Usability Options and Features. Click on each underlined link, then follow the instructions to add your vote to more related ideas. Your VOTES matter!

(If you find this reply helpful, please be sure to click "Like", so others will know, thanks.)
(Edited)