- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hello,
As I was searching through the end-of-life database dump that we received, I found that one of the tables we were looking for was not included. From the research and queries I ran, it looks like they did not configure the source to replicate custom app tables, only platform tables. Is that common? Is there anything we can do to get the app tables?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi Buddy,
In a lot of cases, what’s called a “database dump” isn’t a full instance export. It’s usually coming from a replication or ETL setup that’s intentionally limited to platform tables only, with custom app tables excluded by default. Teams do this to control data volume, avoid schema changes breaking the pipeline, and because ownership of custom app data often sits outside the core platform team.
If your queries are showing that only platform tables were configured for replication, that’s a very reasonable explanation for what you’re seeing.
As for what you can do next, there are really only a few options:
Go back to the team that produced the dump and ask whether they can re-run it with custom tables included. The easiest ask is usually to include tables by prefix (for example x_ or u_) or by app scope.
Confirm exactly how the dump was created. If it wasn’t a true instance-level export, then the missing app tables were filtered out intentionally.
If the source ServiceNow instance still exists, see if you can extract the app tables directly using ServiceNow exports or the Table API for the specific tables you need.
Unfortunately I don't think there is a way to reconstruct missing custom app tables from platform data alone — they have to be pulled from the source.
@DeShanaB - Please mark as Solution Accepted and Thumbs Up if you find Helpful!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi Buddy,
In a lot of cases, what’s called a “database dump” isn’t a full instance export. It’s usually coming from a replication or ETL setup that’s intentionally limited to platform tables only, with custom app tables excluded by default. Teams do this to control data volume, avoid schema changes breaking the pipeline, and because ownership of custom app data often sits outside the core platform team.
If your queries are showing that only platform tables were configured for replication, that’s a very reasonable explanation for what you’re seeing.
As for what you can do next, there are really only a few options:
Go back to the team that produced the dump and ask whether they can re-run it with custom tables included. The easiest ask is usually to include tables by prefix (for example x_ or u_) or by app scope.
Confirm exactly how the dump was created. If it wasn’t a true instance-level export, then the missing app tables were filtered out intentionally.
If the source ServiceNow instance still exists, see if you can extract the app tables directly using ServiceNow exports or the Table API for the specific tables you need.
Unfortunately I don't think there is a way to reconstruct missing custom app tables from platform data alone — they have to be pulled from the source.
@DeShanaB - Please mark as Solution Accepted and Thumbs Up if you find Helpful!
