QuickBooks Online Tag Retirement and the Move to Custom Fields
QuickBooks Online is retiring tags, and users who rely on them face migration deadlines and plan limits for custom fields.
QuickBooks Online is phasing out tags, the flexible labels many businesses used to track work outside the general ledger. Intuit’s published timeline starts in May 2025 and runs to May 2028, with custom fields as the replacement. Users who miss the migration window lose their tagged history for good.
We went through the accepted answer on the vendor’s support pages closely. The picture is mixed: the feature dies, the data can move, and the deadlines are firm. Where you land depends on the plan you pay for and how soon you act.
Why are tags going away?
Tags are light labels you attach to transactions to follow one corner of the business. A studio might tag invoices by campaign. A builder might tag purchases by job site. They sit outside the class and location structure, and they never touch the general ledger. Profit and loss reports stay clean unless you deliberately run the tag group version.
Intuit frames the retirement as consolidation rather than deletion. Custom fields gained broader reach on March 17, 2025, covering sales and expense forms across most plans. They offer text, number, and dropdown formats, with larger limits on values. The vendor wants one tracking tool in the product, not two.
The deadlines that matter
Four dates govern the process, and they split users into two camps: those who never used tags and those who did.
- May 16, 2025: new tag creation stops, and a migration option becomes available to convert existing tags into custom field values.
- May 19, 2025: accounts that never used tags no longer see the option anywhere in the product.
- May 15, 2028: the last day for viewing tags and running reports on tagged history.
- May 19, 2028: the stated end of tag use for customers who already rely on them.
After the viewing window closes, tags are removed and disappear from historical transactions. The window between the two 2028 dates is narrow, and the practical message is blunt. Once it shuts, tagged history is gone, and any report built on tag groups stops working.
Can custom fields replace tags?
Partly, and the built-in migration does the heavy lifting. The option can move up to 60 existing tags into the dropdown of a single custom field. Each field holds up to 100 values. For most small setups, one dropdown absorbs the whole tag collection.
Dropdowns are the format available wherever custom fields exist. Other formats vary by subscription level. The real gap is reporting. Tags had a dedicated profit and loss report by tag group, and nothing in the custom field set fully replaces it. Custom fields categorise transactions for review, but the old tag reports will not survive the cutoff. If those numbers matter to you, capture them well before 2028.
Plan limits shape the migration
Not every plan can hold the same volume of migrated data:
- Simple Start: one custom field per transaction.
- Essentials: four custom fields per transaction.
- Plus: four custom fields per transaction.
- Advanced: twelve custom fields per transaction.
A Simple Start subscriber gets one field, but that single field can still carry 100 values. Essentials and Plus subscribers get four dropdowns each. Advanced subscribers get twelve.
Ledger users face the sharpest edge of this change. Custom fields do not exist on that plan, so there is nowhere for migrated tags to land. Intuit’s stated remedy is an upgrade to a fuller QuickBooks Online plan. Tags used in Ledger will not carry over to another plan either, which turns the transition into a rebuild rather than a transfer.
What should you do before 2028?
Start with an audit of what your tags actually feed. Note every report that leans on tag groups, because those die with the feature. Run the migration, then check that each tag landed as a value in its dropdown. Compare your tag count against your plan limit. A business with 60 tags fits them into one dropdown on any plan that has custom fields. A business on Ledger has no dropdown waiting and needs a plan decision first.
The bottom line
Tags never touched your books, so the accounting itself does not change. What disappears is visibility: the labels, the groupings, and eventually the history. The migration path exists, it works within clear limits, and the deadline is firm. Users who act inside the window keep their tracking. Users who wait until 2028 will find the record blank.