Recreating User Accounts After a QuickBooks Desktop Version Downgrade

User credentials do not survive a version-year downgrade; learn which accounts disappear, why, and how to rebuild them in the converted file.

When a QuickBooks Desktop company file is downgraded to an earlier version year — whether to escape a discontinued subscription, return to a perpetual licence, or move from Enterprise to Premier or Pro — the converted file arrives with a significant gap: every user account created in the newer version is stripped out. The Admin account survives, but all secondary users, their roles, and their passwords are gone. This is not a conversion error; it is how the downgrade process handles the credential structure when moving a file backward across version years.

What Breaks and Why

QuickBooks stores user credentials in a security framework that is tightly coupled to the version-year database schema. When a file is upgraded to a newer version, the credential store is migrated forward and enriched with any new role definitions that the newer version supports. When that same file is pushed back to an older version, the older schema has no way to interpret the newer credential records. Rather than risk corruption or partial role mappings, the downgrade process discards the newer user-account records entirely and leaves only the built-in Administrator account intact.

The result is predictable: the first time you open the downgraded file, only the Admin login works. Every other user who previously had access — bookkeepers, accountants, warehouse staff, payroll clerks — is locked out. Their usernames do not appear in the User List, and there is no way to recover them from within the older version.

What to Capture Before the Downgrade

Before initiating any version downgrade, document the full user roster so it can be recreated methodically afterward.

1. Open the company file in the current (newer) version and sign in as Admin.
2. Go to Company > Set Up Users and Passwords > Set Up Users.
3. For each user in the list, record:
   • The exact username (character-for-character, including spaces and capitalisation).
   • The assigned role or permission set (Full Access, Selective Access, External Accountant, or a custom role).
   • The specific area restrictions if the user has Selective Access — for example, no access to Banking, view-only access to Sales, full access to Purchasing.
4. Note whether any user has the External Accountant role, since this role has its own permission profile.
5. If you do not already know the current Admin password, confirm it now — you will need it to create accounts in the downgraded file.

Store this information securely. It is the only record of your user structure once the downgrade is complete.

Recreating User Accounts in the Downgraded File

After the downgrade is finished and the file opens cleanly in the older version:

1. Sign in as Admin in single-user mode.
2. Go to Company > Set Up Users and Passwords > Set Up Users.
3. If prompted, confirm or set the Admin challenge question.
4. Click Add User.
5. Enter the username and a temporary password. Use the exact username from your pre-downgrade roster so that historical audit-trail entries remain consistent.
6. Select the role or permission level that matches what the user had before. Walk through each permission screen and replicate the area-by-area access settings you documented.
7. Repeat for each user.
8. After all users are created, instruct each person to sign in and change their temporary password immediately.

Role Differences Across Versions

Older QuickBooks versions may not offer the same role templates or granular permissions as the version you are leaving. If a user had a customised role in the newer version that does not map cleanly to the older version's role options, you will need to approximate the closest fit using Selective Access and manual area restrictions. Document any deviations so your internal access policy stays accurate.

Verifying the Rebuilt User List

Once every account is recreated, run a final check:

• Confirm the user count matches your pre-downgrade roster.
• Have each user log in at least once to validate credentials.
• Run Reports > Accountant & Taxes > Audit Trail and filter by a current date range to confirm that transactions are being attributed to the correct usernames.

Preparing for the Downgrade Itself

If you have not yet started the downgrade, run Verify Data in single-user mode on the current file first. A clean verification ensures the file is structurally sound before conversion begins. If Verify reports errors, run Rebuild Data and re-verify until clean. A corrupted file that goes into a downgrade will come out corrupted — and the user-account rebuild will be the least of your problems.