SharePoint Document Issues

Fix SharePoint Custom Columns Missing from Microsoft Project Sync

Bushra ParveenBushra Parveen Nov 4, 2026 869 views

Question details

The user is experiencing an issue where custom columns added to a SharePoint task list fail to appear or synchronize correctly.

Fix SharePoint Custom Columns Missing from Microsoft Project Sync
Product
Microsoft Project 2016 and SharePoint
Device & OS
not provided
Scenario
Synchronizing a SharePoint task list with a Microsoft Project 2016 file.
Observed behavior
Custom columns added to the SharePoint task list do not appear or synchronize when the list is opened in Microsoft Project 2016.
Before you start

Ensure you have administrative or edit permissions for both the SharePoint task list and the Microsoft Project file, and that your internet connection is stable before attempting to force a manual sync.

Solution 1Recommended

Map Custom Data to Supported Project Fields

Since Microsoft Project does not natively support all custom SharePoint field types during synchronization, map your data using supported default Project fields instead.

Microsoft Project 2016 has specific limitations when syncing with SharePoint task lists. Certain custom column types created in SharePoint (such as Lookups, Choice arrays, or specific calculated columns) are not supported by the synchronization engine. To resolve this, you must use supported data fields to ensure the information passes between the two applications without dropping.

1
Identify Unsupported Fields

Check your SharePoint task list for custom field types like lookups, choice fields, or calculated columns that are known to be incompatible with Microsoft Project sync.

2
Create Supported Text Fields in Project

Open your file in Microsoft Project. Right-click an existing column header, select 'Insert Column', and choose a standard custom field (e.g., Text1, Text2, Number1) to hold the specific data.

3
Map Fields Manually

Navigate to 'File' > 'Info' > 'Map Fields' (or 'Manage Accounts' depending on your Project setup) to manually link the newly created Text fields in Project to the corresponding SharePoint list columns.

4
Re-synchronize the List

Click 'Save' or force a manual sync between Microsoft Project and SharePoint. Verify in SharePoint that the data from the mapped fields has updated correctly.

Map Custom Data to Supported Project Fields
Field Compatibility Limit: Always refer to the official Microsoft documentation for the exact list of supported and unsupported field types between Microsoft Project and SharePoint task lists.
Free Microsoft Office alternative

Streamline Your Project Document Management with WPS Office

While Microsoft Project and SharePoint handle complex enterprise synchronization, many teams find them overly complicated for standard document and task management. WPS Office offers a free, lightweight, and highly compatible alternative for creating, managing, and collaborating on project documents, spreadsheets, and presentations without frustrating sync limitations.

Fully compatible with Microsoft Excel (.xlsx), Word (.docx), and PowerPoint (.pptx) formats.Lightweight application that runs smoothly on Windows, Mac, Linux, and mobile devices.Built-in cloud tools for real-time team collaboration on project tracking spreadsheets.Free to download and incredibly easy to deploy without complex server sync issues.
QA img-9

Frequently Asked Questions

Why are my SharePoint task list columns not showing up in Microsoft Project?

This usually happens because the custom column type created in SharePoint (such as Choice, Lookup, or Person/Group) is not supported by Microsoft Project's synchronization engine. Only specific standard data types are successfully synced.

Can I force Microsoft Project to sync unsupported SharePoint columns?

No, unsupported column types cannot be forced to sync natively. You must use compatible text, number, or date fields in Microsoft Project and map them to standard SharePoint columns.

Does this sync issue affect newer versions of Microsoft Project?

Yes, while Microsoft Project 2016 is commonly affected, newer versions and Project Online also maintain strict field mapping rules and limitations when integrating directly with classic SharePoint task lists.