How to have clean pipeline and archive projects from previous year?

This is very frustrating! Viewing my calendar from the previous year gives me a visual to help plan for busy and slow dates for the upcoming year.

EXACTLY!!!  

Totally agree, I now have 900 projects just hanging out in the completed tab because I made that mistake a few years back

Have you found any good work arounds?

I created new stages in my pipeline for 2024 and 2025 clients and moved completed projects to the year when they occurred. It’s going to get annoying in future years (if I continue on Honeybook) bc there will be way too many extra stages, but it works for now.

That’s what I was thinking as well.  I started in 2025 with HB so I’m still “new”.  So I started to make that year a stage then I was like ummm then what...this can not sustain but a few years.  I also did as the AI suggested and marked it “do not track” but then I’m not seeing it show up anywhere.  I have to go to the contacts and pull the individual file that way.  I’m sure there may be an easier way but I don’t feel like we should have to do ALL these thangs.  Esp considering the AI and cost we are paying.  I’m super bummed, I otherwise like HB.  I left my last CRM because they also could not organize previous year files well either.  I have some clients that I work with consistently throughout the year.  So when I go to their file I would like each year to be in it’s own file. I thought this was a simple request but I guess not.  When I post this it FB group I was kinda shocked how many people think Archiving is only for projects that did not happen. When HB itself gives many reasons with completed being one. And most ppl in the FB group said they didn’t care or just let it sit.  I just wanna easily reconcile my files in a clean manner...sorry for the long rant! 

​@SouthernSweety - This really does become a problem when you’re managing a high volume of projects each year. I’d definitely recommend submitting this as a Feature Request in the Ideas section of the community, or upvoting an existing request if you find one that’s similar. I did a quick search and didn’t see this exact use case listed, so adding it could be really helpful. The more upvotes a request gets, the higher priority it tends to become for the developers.