How to Import and Preserve Excel Fields in Microsoft Project
Question details
The user wants to import an Excel template into Microsoft Project while preserving custom field names, reusing mappings, automatically adding columns, and synchronizing future updates.

- Product
- Microsoft Project, Microsoft Excel
- Device & OS
- not provided
- Scenario
- Importing project data and custom fields from an Excel spreadsheet into Microsoft Project for advanced scheduling.
- Observed behavior
- Custom Excel fields are imported as default system fields (e.g., Number1, Text1) instead of retaining their original Excel header names, requiring inefficient manual renaming and column insertion.
Ensure your Excel data is cleaned and organized into a flat table before importing. Avoid importing calculated Start and Finish dates, as Microsoft Project's scheduling engine should calculate these based on task durations and dependencies.
Use the Import Wizard and Rename Fields Manually
Map Excel columns to Microsoft Project's built-in placeholder fields and rename them manually for your display views.
Microsoft Project uses a fixed database structure. It cannot dynamically generate new internal fields. Therefore, imported custom data from Excel must be assigned to Project-defined fields such as Text1, Number1, or Cost1. While their internal names remain unchanged, you can rename their display labels.
In Microsoft Project, navigate to File > Open. Change the file type to 'Excel Workbook (*.xlsx)', select your Excel file, and click Open to launch the Import Wizard.
Follow the wizard prompts and choose 'New map' (or a previously saved map). In the mapping stage, match your Excel column headers (e.g., Sponsor, Gen ID) to the available MS Project fields (e.g., Text1, Text2, Number1).
Before finishing, click 'Save Map' so you can reuse this exact mapping configuration for future Excel imports.
After importing, right-click on the column headers in your Gantt Chart view, select 'Insert Column', and choose your mapped fields (e.g., Text1). Right-click the column again, choose 'Field Settings', and change the Title to match your original Excel field name.

Automate Import and Field Renaming with VBA
Use a VBA macro to fully automate the import, mapping, column insertion, and renaming process for repeated workflows.
Manage Project Data Seamlessly with WPS Office
While Microsoft Project utilizes strict internal field structures for complex scheduling, you can easily track and manage your project data, custom fields, and task lists directly in WPS Spreadsheet without running into rigid mapping restrictions or needing complex VBA macros.
- 1. Open WPS Spreadsheet: Launch WPS Office and open WPS Spreadsheet to create a new project tracker or open your existing Excel (.xlsx) file.
- 2. Define Custom Project Fields: Type your desired field names (e.g., Task Type, Gen ID, Sponsor) directly into the top row to instantly create your custom columns.
- 3. Collaborate and Share: Save your work seamlessly in .xlsx format to ensure full compatibility with colleagues using Microsoft Office.

Frequently Asked Questions
Why do my Excel columns change to Text1 or Number1 in MS Project?
Microsoft Project relies on a rigid database architecture. It cannot dynamically create new internal fields. Therefore, any imported custom data must be mapped to existing built-in placeholder fields, which range from Text1 to Text30, Number1 to Number20, etc.
Can I save my field mapping for future imports?
Yes. During the Import Wizard process, you have the option to save your mapping. You can reuse this saved map for future imports to skip the manual mapping step, although you may still need to insert and rename the columns manually in your view.
Should I import Start and Finish dates from Excel into Project?
It is highly recommended to avoid importing calculated Start and Finish dates. Instead, import task durations and dependencies, allowing Microsoft Project's scheduling engine to accurately calculate the dates based on your project calendar.




