You can find the Gray Settings group in the WikiTraccs Transformation Settings dialog, on the Migration tab, below a label that reads Gray Settings.
What is a “Gray Setting”?
A gray setting is a setting that activates behavior WikiTraccs cannot fully guarantee will keep working over time. The behavior depends on a mechanism that is not officially documented as supported by Microsoft or Atlassian. It works today, but a future change to SharePoint, Microsoft 365, Confluence, or the underlying editors could break it.
Current Gray Settings
Migrate whiteboards as image [Cloud]
Confluence Cloud whiteboards are migrated as a static image embedded in the SharePoint page. The image is generated by WikiTraccs by interacting with Confluence in an automated browser session.
This is gray because the export relies on automated clicking through the Confluence Cloud whiteboard UI rather than on a stable public API. Any change Atlassian makes to that UI can break the automation.
For details, see Migrating Confluence Cloud Whiteboards.
Migrate whiteboards to draw.io file [Cloud, best effort]
Confluence Cloud whiteboards are migrated to a draw.io diagram file that is added to the SharePoint page as a page attachment, preserving the underlying shapes and connectors as far as practical. The file is not editable inside SharePoint, but it can be downloaded and edited in an external draw.io editor.
This is gray because the conversion is best effort. Whiteboards can use shapes, layouts, and content for which no clean draw.io equivalent exists, so the migrated file may need manual cleanup. It is also subject to the same Cloud-mechanism caveat as the image export above.
For how to download a draw.io attachment from a SharePoint page and open it in the draw.io editor (app.diagrams.net), see Converting Gliffy and draw.io to SVG. For insights into how Confluence whiteboards work internally, and why a structured draw.io export is non-trivial, see Inside Confluence Whiteboards.
Use non-standard table transformation
When checked, WikiTraccs preserves table features that the SharePoint Text web part stores correctly but does not always expose as toolbar buttons in the browser-based page editor. As of 2026, this primarily affects nested tables: a <table> inside a table cell is kept in place rather than being de-nested into a separate area below.
This is gray because, although SharePoint stores and renders the resulting tables, end users cannot create the same structures by clicking buttons in the editor toolbar. A future change to the editor could in theory remove or alter how such tables are handled. In practice this has been working reliably and is on by default.
For background and history, see Making SharePoint Tables Look Pretty.