Migrating your existing data into the Geodatabase

While I was at the user conference earlier this year I was getting a lot of questions about migrating to the geodatabase from other data formats. I talked it over with Derek Law and he thought he’d make a podcast about it (we’ll link to that podcast when it hits the net). After seeing the script for his podcast I decided that some introductory style posts would also be a good way to get the info out to our users.

So this is the first in a series of posts that will be addressing how to migrate to the geodatabase. We’ll discuss migration strategies for five common GIS data formats:

ArcCatalog is the ArcGIS Desktop application that allows you to manage and access GIS data. Within ArcCatalog, there are two general workflows to migrate GIS data into the geodatabase:

Importing data into the geodatabase – in the Catalog tree, select the geodatabase you want to place your GIS data into, right-click and select Import from the context menu, then choose the appropriate data import tool.

Exporting data into the geodatabase – In the Catalog tree, browse to and select the GIS dataset that you want to put into the geodatabase, right-click and select export from the context menu, then choose the appropriate data export tool

Both approaches use the same geoprocessing (GP) tools that are readily available directly within ArcToolbox, specifically in the Conversion Tools toolbox, in the To Geodatabase toolset.

Since the To Geodatabase toolset migration tools are GP tools, you can leverage them within the ArcGIS geoprocessing framework.

This means that you can execute the migration tools in several different ways:

For more detailed information on the different ways to execute a GP tool in ArcGIS, look in the Geoprocessing help book, in the ArcGIS Desktop help.

Migrating Shapefiles into a Geodatabase

So first, let’s look at migrating shapefiles into the geodatabase. A shapefile is the native data format for ArcView GIS 3.x technology. It is a type of feature class and therefore directly maps to the geodatabase as a single feature class when you migrate it to the geodatabase.

There are two key GP tools for migrating your shapefiles into the geodatabase:

The Feature Class to Feature Class tool works on a single shapefile.

You will need to specify the following:

There are also 3 optional input parameters:

For the Field Map parameter, we recommended that you drop the FID, shape_length, and shape_area attribute fields, because these will be replaced by new fields when the shapefile becomes a feature class in the geodatabase.

The Feature Class to Geodatabase tool works on multiple shapefiles. Idealy you would use this tool over the Feature Class to Feature Class tool if you had many shape files to migrate to a Geodatabase. To use this tool you specify one or more shapefiles to convert and the output geodatabase location. By default, the shapefiles will have the same names as the original shapefiles when they are migrated into the geodatabase.

Using GP tools makes the task of migrating shapefile data into a geodatabase quick and painless. As mentioned before, GP tools can be used in a number of different ways including initiating the tools through ArcCatalog, using them directly from the toolbox, or scripting the tool execution in python.

About the author

Jonathan Murphy

Product Owner, UX Designer and Content Strategist on the Geodatabase team at Esri. Writer, musician, cockatiel whisperer and prolific world traveler.

Next Article

Use Arcade geometry functions with FeatureSets to provide spatial context

Read this article