Latest Update: 10-15-2026
When exporting your Planera project to P6 or MSP, certain characters are not supported by the destination platform and will cause the import to fail. This article covers naming restrictions for each platform, which characters to avoid, and how to resolve common errors.
Different platforms have different character restrictions
Special characters in project names, activity names, and calendar names are the most common cause of import failures
Preventative naming is easier than troubleshooting after export
Primavera P6 Export Issues
Characters to Avoid
P6's XER and XML formats have character restrictions. Avoid these characters in project names, activity names, calendar names, and configured field names:
|(pipe)<(less-than)>(greater-than)&(ampersand)
XER vs. XML Format
P6 offers two export formats: XER (native Oracle format) and XML.
XER format uses Windows-1252 encoding and has stricter character limitations. If your project contains special characters, XER export may fail.
XML format handles a broader range of characters. If XER export fails due to special characters, try exporting as XML instead.
Complete Import Failures
Special characters in the following fields will prevent P6 import from completing at all:
Configured field names
Code names
Before exporting, review your project structure to ensure these critical fields do not contain special characters.
Microsoft Project Export Issues
Calendar Name Length
MSP has a strict character limit for calendar names:
Calendar names must be 51 characters or fewer
Exceeding this limit causes an import error and the project will not open in MSP
This applies to the Standard Calendar and all custom resource calendars
Characters to Avoid in Names and Notes
While MSP is generally more permissive than P6, some characters are not supported in XML format:
TAB characters and line breaks in task names or notes fields will cause import failures
Use only alphanumeric characters, spaces, hyphens, and underscores in task names where possible
Remove or replace special characters before export
General MSP Import Guidance
Keep task and project names clear and simple
Avoid complex formatting or special symbols
Test exports with a small subset of your project first if you are using many custom fields or non-standard naming
How to Fix Export Errors
Before Exporting
Review all project, activity, and calendar names for the characters listed above
Check calendar name lengths (MSP only); rename any calendar longer than 51 characters
Audit configured field names and code names (P6 only) for special characters
Check task notes and descriptions for TAB characters or line breaks (MSP only)
After an Export Fails
Note the exact error message from P6 or MSP; it often indicates which field or record caused the failure
Go back to Planera and search for the problematic field or name using the error message
Rename the field or record to remove special characters
Re-export in the same format
Still Stuck
If you have removed all problematic characters and the export still fails, contact Planera support through the chat icon in the bottom right of Planera. We can help troubleshoot platform-specific import issues and identify any other restrictions that may apply to your version of P6 or MSP.
Frequently Asked Questions
Why did my P6 export fail when my project names look normal?
The issue is often in activity names, calendar names, or custom field names rather than the project name itself. Check all three and look for pipes, angle brackets, and ampersands. If you are using XER format, try XML instead.
My calendar name is only 40 characters, but MSP still won't import it. What's wrong?
Check for TAB characters or line breaks hidden in the calendar name or in task notes. These invisible characters count toward the limit and can cause import failures even if the visible character count is low.
Can I use hyphens and underscores in names for both P6 and MSP?
Yes, hyphens and underscores are safe for both platforms. Use them instead of spaces if you need to separate words in names.
Do I need to rename calendars every time I export, or can I create calendars with these restrictions from the start?
It is best practice to follow these naming restrictions from the start when creating any calendars or project structures you plan to export. For P6 exports, avoid special characters in calendar names; for MSP, keep calendar names under 51 characters. This prevents export failures down the road.
What if my organization requires special characters in project or activity names?
If special characters are non-negotiable, export to the least restrictive format available (XML for P6 rather than XER), and check the import documentation for the specific version of P6 or MSP you are using. Some newer versions may support additional characters. Contact Planera support if you need help working around organizational naming requirements.