web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

D365FO - Archive data to history tables but not to dataverse

(3) ShareShare
ReportReport
Posted on by 6,597 Super User 2026 Season 1
Dear all,
 
I trying to figure out how data archiving is working. I ve checked out the following ressources, however, there is still a major question open:
 
How can I move data to history tables, but NOT to dataverse. Dataverse space is quite expensive, so for now we should be fine to move data first to history table.
 
As far as I see it here, I can only select long term retention job.
 
 
 
my ressources:
 
 
 
Thanks in advance, Adis
Categories:
I have the same question (0)
  • Verified answer
    Saif Ali Sabri Profile Picture
    2,354 Moderator on at
    In Dynamics 365 Finance and Operations (D365FO), the standard Archive with Dataverse long-term retention feature is designed to move data to Dataverse. However, if you want to archive data only to history tables and not Dataverse, you will need to use custom archiving methods. Here’s what you can do:
    Solution:
    1. Use SQL-based Archiving (if allowed)
      • Create custom archive tables in the D365FO database.
      • Use Batch Jobs or Data Management Framework (DMF) to move older records to these tables.
      • Ensure these tables are excluded from standard transactional processing.
    2. Leverage Standard Purge & Archive Features
      • Some modules have built-in data cleanup routines (e.g., Sales Order history).
      • Configure these to move data to history tables without enabling Dataverse retention.
    3. Develop a Custom Archive Solution via X++
      • Create a custom archiving process using X++ that moves old records to a history table.
      • Schedule a batch job to automate data movement.
    Since Dataverse space is costly, this approach allows you to archive data without consuming extra Dataverse storage. If Microsoft releases a built-in option to disable Dataverse retention in the future, that would be the best alternative.
  • Adis Profile Picture
    6,597 Super User 2026 Season 1 on at
    Alright, thanks for your answer. I was afraid to receive that feedback.
     
    Kind regards, Adis
  • Suggested answer
    Saif Ali Sabri Profile Picture
    2,354 Moderator on at
    I get it—it's not the ideal answer, but unfortunately, Microsoft hasn't provided a native way to use history tables without Dataverse in the standard archiving framework. If you're mainly concerned about storage costs, a custom archiving strategy is your best bet for now.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 658

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 468 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 333 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans