topic Re: Export to File Geodatabase does not work in ArcGIS Online Questions

Export to File Geodatabase does not work

DaveBodak — Tue, 19 Apr 2022 12:55:39 GMT

I have several large feature layers (about 5,000 parcels in each) with attachments and related tables in some, but not all. I have realized that it has gotten the the point where I can't export my data as a File Geodatabase anymore in AGOL. It will just show a loading screen and default back to the screen with the original selection (shown below) and does not create anything from this data.

I have done some research and noticed this was a problem in 2018, I was hoping it would be solved by now and that I was experiencing a different issue. As we continue to locate more assets without having backup files saved in AGOL, there comes a bigger risk with losing significant amounts of data if something were to happen.

Here is that article I found: https://support.esri.com/en/technical-article/000015786

The only issue with this method is that it does not preserve everything within the feature layer and is more time consuming to go through.

Thanks for your help!

Re: Export to File Geodatabase does not work

Katie_Clark — Tue, 19 Apr 2022 13:02:15 GMT

Have you only tried exporting from the Item Details page (like your screenshot shows) and not the REST Endpoint? That's the method I always have to use, especially for large datasets. These two articles might help.

https://support.esri.com/en/technical-article/000012232

https://support.esri.com/en/technical-article/000014156

Good luck!

Re: Export to File Geodatabase does not work

ScottKiley — Tue, 19 Apr 2022 13:27:36 GMT

I continue to have problems exporting hosted feature services to File Geodatabases. I have some services with lots of attachments, thus a large data storage footprint. At times when exporting those from the item details, it looks as though it's complete. It even creates a new item for the FGDB. Though, downloading it from that resulting item details page creates an invalid ZIP file.

I often find the case is the FGDB simply hasn't completed exporting, so I try again and let it sit on the exporting page, even though it shows complete, then open the resulting item on another window and leave the original until I have a valid ZIP file.

I say this often works, because (like everything ArcGIS) it doesn't ALWAYS work.

If you find this to be the case, I suggest trying to run a feature class to feature class on the feature data in ArcMap or ArcGIS Pro. This works surprisingly well for me.

You can also try using the instructions in the Technical Support below:

Problem: Exporting a hosted feature service as a file geodatabase in ArcGIS Online returns a corrupted ZIP file (esri.com)

Re: Export to File Geodatabase does not work

DaveBodak — Tue, 19 Apr 2022 13:55:10 GMT

Yes, that was the method I have primarily used. I went through the article and it doesn't seem to bring the related table and attachments with it when I export it, is there something here that I am missing?

This did move in the right direction though, thanks!

Re: Export to File Geodatabase does not work

DaveBodak — Tue, 19 Apr 2022 13:56:30 GMT

Thank you for the recommendation, I will try the method of just letting it sit for a while to see what happens. In the meantime, I will try the feature class to feature class method in AGIS Pro. Thanks!

Re: Export to File Geodatabase does not work

Katie_Clark — Tue, 19 Apr 2022 14:53:11 GMT

Hmmm, it should have the related tables in the file geodatabase output. Are you making sure to reference all layers in the service when you export?

Re: Export to File Geodatabase does not work

DougBrowning — Tue, 19 Apr 2022 18:11:34 GMT

It is not just you I get this all the time for the last few years now. Anything over 10 GB and it starts to not work a lot. I usually have to create a replica instead at that point.

Re: Export to File Geodatabase does not work

DaveBodak — Fri, 22 Apr 2022 19:28:48 GMT

When I export I have multiple layers shown in that section, I will upload a screenshot of my setup:

You may notice, that across the bottom is says layerid: 1 is not valid. It seems like this may be part of my issue for my two related tables to be exporting within the FGDB.

Re: Export to File Geodatabase does not work

Katie_Clark — Fri, 22 Apr 2022 19:33:21 GMT

Oh, interesting. What type of layer is layerID1? Can you also share a screenshot of what the REST endpoint looks like for the feature service?

Re: Export to File Geodatabase does not work

DaveBodak — Fri, 22 Apr 2022 19:40:12 GMT

I am thinking that since there is only one layer, it may now know what to reference. Here are the tables contained within this feature dataset. The multiple GBD_ServiceItems are from previous FGDB exports when the data was smaller and it worked through this screen.

Are you able to navigate me to the REST endpoint section? Thanks!

Re: Export to File Geodatabase does not work

DaveBodak — Fri, 22 Apr 2022 19:43:51 GMT

Scratch that, I got it to work!

When I was sending the screenshots of my layers I realized what the IDs actually were, and it worked once I fixed them. Thanks for your help!

Re: Export to File Geodatabase does not work

Katie_Clark — Fri, 22 Apr 2022 19:46:23 GMT

Ok yup, that's exactly the info I wanted to see in your screenshot. Just needed to reference 0, 3, 5, 6, 10 instead of 0, 1, 2, 3

Glad you got it to work!

Re: Export to File Geodatabase does not work

SarahRijneke — Mon, 14 Jul 2025 12:59:25 GMT

Are there any downsides to creating a replica?

I am trying to download a few feature services from AGOL to a stand alone gdb. The services are point layers of survey results with photo attachments. They consume quite a few credits and contain old data so I would like to take them offline and put them in an archived database. I don't know too much about replicas. Is the replica the same size as the feature service? Can/should I delete it once I've downloaded it? I have no use for it other than to download my data.

I've tried bringing the feature into ArcPro and exporting/importing it into the gdb. It runs all day and when I log on the next day I can see that the program has crashed. Sometimes it results in a new, empty feature class in the gdb. I have tried to append the dataset into the new feature class with similar results. Nothing has been moved over and ArcPro has crashed.

I have to do this for 3 features services, all with 5000+ records. Are there any other suggestions for moving it to an offline geodatabase?