# Archive existing records **URL:** \ **Category:** Get Help\ **Created:** [August 20, 2025, 12:52pm UTC](https://community.fibery.io/t/archive-existing-records/9429 "2025-08-20T12:52:27Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [August 20, 2025, 12:52pm UTC](https://community.fibery.io/t/archive-existing-records/9429/1 "2025-08-20T12:52:27Z")
Hello guys, is that possible to archive records somehow? Example: we have a database with 35k+ records. The problem is that when we do a report, the system is slowly loading all records. We want to archive (but do not delete) old records to speed-up the reporting flow. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [August 20, 2025, 1:04pm UTC](https://community.fibery.io/t/archive-existing-records/9429/2 "2025-08-20T13:04:37Z")
You could go the route of having a checkbox field “Archived?” then filtering in the report to only take entities where Archived = False. Then some kind of automation logic to auto mark things as archived when something happens, or a button to “Archive”, also possible. ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [August 20, 2025, 1:08pm UTC](https://community.fibery.io/t/archive-existing-records/9429/3 "2025-08-20T13:08:52Z")
Do you mean a custom checkbox field? If yes, how does it help when we create a report? The system collects data from all records as I understand. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [August 20, 2025, 1:30pm UTC](https://community.fibery.io/t/archive-existing-records/9429/4 "2025-08-20T13:30:31Z")
This has all the info :)) > **[Reports](https://the.fibery.io/@public/User_Guide/Guide/Reports-346/anchor=Filtering-the-source-data--5ab22756-b03b-483b-aaec-5caff317367e)** Edit, it actually doesn’t show where it is… ![Screenshot 2025-08-20 at 14.31.25](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a30e6b0334c854bd9b9a8ce53cb5b58f0a1cdcb0.png) This filter button will limit the entities that get put into the report. Then there’s the filtering you can do on the data after that, but as you mentioned, that wouldn’t make it run faster. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [August 20, 2025, 2:51pm UTC](https://community.fibery.io/t/archive-existing-records/9429/5 "2025-08-20T14:51:42Z")
For purely archival needs, one solution is to export the entities - this could be relatively easy using the API. However if you need to maintain all references/links to other entities, or be able to resurrect “archived” entities, this approach might not be practical. ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [August 21, 2025, 6:01am UTC](https://community.fibery.io/t/archive-existing-records/9429/6 "2025-08-21T06:01:09Z")
It works for us, thank you! ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [August 21, 2025, 6:04am UTC](https://community.fibery.io/t/archive-existing-records/9429/7 "2025-08-21T06:04:13Z")
Yes, that’s what we were thinking as well. Ideally, it should serve as a mechanism to cache unchanged records in order to speed up the reporting process.