nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can we go back to the old Fidelity Connection?

jystickman

Can you make the option to go back to the old Fidelity Connection available for us? Given the current connection is unusable for 401(k) downloads (everything transaction downloads as a cash transaction and no securities info comes across) can we be allowed to go back until Fidelity and Quicken sort out this mess?

Find more posts tagged with

Online Banking

Mac

Accepted answers

Quicken Anja

Hello @jystickman,

Thanks for reaching out, and I completely understand the frustration, especially with the current issues.

Unfortunately, once an institution has been migrated to the new connection method, it’s not possible to revert back to the previous one. The old connection type is no longer available once the switch has been made.

Please know that our teams are actively working to resolve the current issues with the new connection, and we appreciate your patience in the meantime.

Thank you!

All comments

Quicken Anja

Hello @jystickman,

Thanks for reaching out, and I completely understand the frustration, especially with the current issues.

Please know that our teams are actively working to resolve the current issues with the new connection, and we appreciate your patience in the meantime.

Thank you!

jystickman

@Quicken Anja - thank you for your response and explanation. This particular rollout, which clearly has a lot of issues based on the comments, is really leaving a bad impression on me. Quicken had made a lot of improvements in the last few years but my last couple of interactions, including with a support agent who told me my solution was I had to enter in all those transaction details manually, is making me rethink renewing my subscription. You folks are leaving the impression of going downhill quickly.

jacobs

You folks are leaving the impression of going downhill quickly.

@jystickman It bears keeping in mind that Fidelity instigated this switch, the timing of it, and is likely responsible for all or most of what's not working correctly. (Quicken will never throw a financial institution under the bus and publicly blame them, because Quicken depend's on financial insituitions' cooperation to make things work.)

jystickman

Quicken Support saying that the solution was to enter all the transactions in manually was not at all reasonable, and I do think that both parties have a hand in doing testing, which does not seem to have been very thorough. Quicken certainly has the ability to influence, if not outright control release of changes that affect their product if it's not of good quality.

Quicken Support was excellent for several years. This exchange over my phone support ticket was extremely disappointing.

jacobs

Quicken certainly has the ability to influence, if not outright control release of changes that affect their product if it's not of good quality.

I don't know if that's the case in this instance, but I know for certain that it's often not the case. Financial institutions make changes without letting Quicken or Intuit know in some cases, and in other cases like this one, they set a date and stick to it even when Quicken may be telling them things aren't working right. And Quicken has limited testing opportunity with real-world financial accounts; financial institutions may provide a test server or test accounts but those environments often don't contain all the complexities found in real-world accounts.

I'm not saying Quicken gets a free pass here; I have no inside knowledge of what exactly transpired in this case. But often, Quicken is at the mercy of large financial institutions and can only react to what is dumped in their lap.

jystickman

I agree that your statement is very true.

And I have, by the way, complained to Fidelity about this too because it absolutely is their feed.

Chris_QPW

I find it interesting that for Quicken Mac you can’t go back, because that is exactly what people have don in Quicken Windows.

And the migration has been frozen until they work it out.

I do notice less complaints on the Mac side though.

Note Fidelity isn’t the first financial institution to go through this conversion. And it seems like all of them have had this period of a lot of problems before things have been worked out.

And as for “assigning blame”, the connection method isn’t some kind of “screen scraping”, each field that needs to be filled out is defined in a standard. The connection between Quicken to the Quicken server doesn’t change, and the connection between the Quicken server and Intuit shouldn’t have to change (provided that there isn’t anything new in the Fidelity data that the other financial institutions have already sent). So, that pretty much pins it down to Fidelity not understanding what each field should be, and getting the right data in them.

Quicken Anja

https://community.quicken.com/discussion/comment/20505036#Comment_20505036

@jystickman Thank you for the honest feedback—I completely understand how disappointing this experience has been, and I’m really sorry that your recent interactions have left a negative impression. We truly appreciate you taking the time to share this.

Regarding the interaction you had with the support agent, I’d like to have that reviewed further so the appropriate coaching can take place. If you have the ticket number (or can provide an approximate date of the interaction), I can locate it and forward it to the agent’s management team for follow-up.

Please know that resolving the Fidelity connection issues remains a top priority, and we’re actively working with Fidelity to get this corrected as quickly as possible.

Thank you again for your patience!

MURF56

Has Quicken & Fidelity stated that they will not force user to use the new method before the current problems have been resolved? The forced cutover date was suppose to be TODAY 8/20/25.

Chris_QPW

https://community.quicken.com/discussion/comment/20505322#Comment_20505322

It has been stated here that the forced cutover will not start today (look at the last comment):

https://community.quicken.com/discussion/7964580/updated-8-19-25-fidelity-cut-over-migration

jystickman

https://community.quicken.com/discussion/comment/20505125#Comment_20505125

@Quicken Anja - the ticket was 11891950. To be fair I escalated to the manager and got a much more sane response. I appreciate that coordinating efforts between two companies is not the easiest, and there will always be issues. Just really feel like the transaction downloading for 401(k) that I and others are experiencing was really a big miss. Thanks for following up.

Quicken Anja

https://community.quicken.com/discussion/comment/20505416#Comment_20505416

@jystickman Thank you for sharing those details—I’ve noted ticket 11891950 and will make sure it’s pulled for review and passed along to the appropriate team. I’m also glad to hear that the manager you spoke with was able to provide a clearer response.

You’re absolutely right that coordinating between companies can sometimes introduce extra hurdles, but feedback like yours helps us stay on top of where the pain points are and ensure they’re given the right visibility.

We really appreciate your patience and the thoughtful way you’ve approached this.

Thank you again for working with us on this!