Most people treat exporting an attribute table to Excel like it’s a manual data transfer job. They open ArcGIS or QGIS, right-click, select 'Open Attribute Table', then highlight rows, Ctrl+C, switch to Excel, and pray the columns line up. That’s not exporting — that’s data hostage negotiation.
The Problem
You’re in ArcGIS Pro, reviewing parcel data for the Shenzhen Urban Planning Office. You need to share the latest land-use attributes with finance for valuation modeling. But when you try to copy the attribute table (right-click → Copy), Excel pastes it into A1… and everything collapses:
| FID | Parcel_ID | Owner_Name | Zoning | Area_m2 | Last_Inspected |
|---|---|---|---|---|---|
| 0 | SZ-PL-7721 | Liu Wei | R-3 | 124.7 | 2024-03-15 |
| 1 | SZ-PL-7722 | Acme Corp | C-2 | 892.1 | 2024-02-28 |
| 2 | SZ-PL-7723 | Sarah Chen | M-1 | 317.4 | 2024-01-10 |
| 3 | SZ-PL-7724 | Guangdong Holdings | PUD | 1,205.9 | 2023-12-05 |
| 4 | SZ-PL-7725 | Yao Lin & Assoc. | R-1 | 88.3 | 2024-04-02 |
That looks fine — until you check column B in Excel. The ‘Parcel_ID’ values are now left-aligned as text, but Excel thinks they’re numbers because of the leading zeros (e.g., ‘SZ-PL-0077’ becomes ‘SZ-PL-77’). Column F? Dates paste as plain text — not serial numbers — so you can’t sort or calculate age. And don’t even ask about special characters: ‘Zoning’ values with hyphens and slashes break CSV imports later.
The Solution
You don’t need third-party add-ins or Python scripts. ArcGIS Pro (v3.0+) and QGIS (3.28+) let you export attribute tables directly to .xlsx — preserving data types, field order, and even domain descriptions. Here’s how it actually works:
| Step | Action | Result | Shortcut |
|---|---|---|---|
| 1 | In ArcGIS Pro, right-click the layer → Export → Export Attribute Table | Opens Export dialog with field list, output path, and format options | None |
| 2 | Under Output Location, browse to your folder. Set Output Type to .xlsx (not .csv) | Excel file created with proper date/number formatting; no text conversion loss | Alt+T → E → X (in Export dialog) |
| 3 | Check ‘Use Field Aliases’ and ‘Include Domain Descriptions’ if available | Column headers show ‘Parcel ID’, not ‘Parcel_ID’. ‘Zoning’ displays ‘Residential-3’, not ‘R-3’ | Alt+U, Alt+D |
| 4 | Click OK. Open the file in Excel. Confirm B2:C10 contains clean strings, D2:D10 is numeric, and F2:F10 is formatted as Date | A1:F6 matches the clean table below — ready for formulas or PivotTables | Ctrl+O |
| FID | Parcel ID | Owner Name | Zoning | Area (m²) | Last Inspected |
|---|---|---|---|---|---|
| 0 | SZ-PL-7721 | Liu Wei | Residential-3 | 124.7 | 15-Mar-2024 |
| 1 | SZ-PL-7722 | Acme Corp | Commercial-2 | 892.1 | 28-Feb-2024 |
| 2 | SZ-PL-7723 | Sarah Chen | Manufacturing-1 | 317.4 | 10-Jan-2024 |
Surprising tip: If your GIS layer has joined tables, *uncheck* ‘Export only selected features’ before exporting — otherwise Excel gets blank rows where joins failed. Also: never use .csv unless you’ve confirmed all fields are ASCII-only. I once lost Chinese characters in ‘Owner Name’ because someone insisted on CSV.
Going Further
You can automate this in batch. In ArcGIS Pro, open the Geoprocessing pane → search ‘Table To Excel’. Drag your layer in, set output path, and run. It accepts multiple layers at once — great for weekly parcel + building + utility exports.
In QGIS, go to Layer → Export → Save Features As…, then choose ‘Microsoft Excel’ under Format. Check ‘Skip attribute creation’ if you want raw field names (not aliases) — useful for scripting downstream.
For legacy systems still using Excel 2003 (.xls), export to .xlsx first, then use Excel’s ‘Save As’ → ‘Excel 97-2003 Workbook’. Don’t export directly to .xls — it truncates field names to 255 chars and drops domains.
When NOT to Use This
Avoid direct export if your attribute table exceeds 1,048,576 rows. Excel will silently cut off data after row 1,048,576 — no warning. For large datasets (e.g., city-wide point clouds), use ‘Table To DBF’ first, then import into Excel via Power Query.
Don’t export if your GIS uses coded value domains with long descriptions. Excel won’t preserve the domain logic — just the displayed text. If you need traceability back to codes (e.g., ‘R-3’ → ‘Residential-3’), keep the original GDB or use a join table.
And skip this entirely if your organization uses SharePoint or Teams for collaboration. Upload the .gdb or .gpkg instead — colleagues can open it natively in ArcGIS Online or QGIS Cloud without risking formatting drift.
Keyboard Shortcuts
| Action | ArcGIS Pro Shortcut | QGIS Shortcut |
|---|---|---|
| Open Export Attribute Table dialog | Right-click layer → Export → Export Attribute Table | Right-click layer → Export → Save Features As… |
| Browse output location | Alt+L → navigate folders | Ctrl+Shift+S |
| Select .xlsx format | Alt+T → E → X | Alt+F → M → X |
| Toggle ‘Use Field Aliases’ | Alt+U | Not supported |
