WikiTraccs 1.16.0

  • new: supporting Brikit Theme Press migration to SharePoint Online modern pages
  • new: detection of Confluence attachment hard links and translation to proper SharePoint links
  • improved: transformation of nested ordered lists, where the nesting can be reduced
  • improved: WikiTraccs.GUI nowshows notifications on start-up when appsettings.json or cookies.txt are used do modify authentification behavior
  • fix: configurations via appsettings.json are not applied to WikiTraccs.GUI connection test
  • fix: the combination of cookies.txt, appsettings.json, and anonymous authentication is broken

WikiTraccs 1.14.13

  • improved: connection check for Confluence now also checks that space information can be retrieved to discover issues faster
  • improved: logging now includes Confluence version, to faster diagnose version-specific issues
  • fix: interactive login (cookie based) broken for Confluence Cloud

WikiTraccs 1.14.10

The LinkTransformationMode introduced in the last release now covers more cases of hard links to pages and spaces. (Hard links are pure “text links” without any Confluence magic.) Note that hard link transformation is (and so far has been) supported for pages and spaces, not attachments. So attachment hard links are always migrated as-is.

WikiTraccs 1.14.6

  • fix: on-prem Confluence groups are not always added to Confluence User and Groups list

WikiTraccs 1.14.8

This release introduces a setting to disable link transformation for unmapped entries in the Space Inventory.

Background: So far, all Confluence links (page links, space links, attachment links) are transformed to SharePoint links. If there are entries in the Space Inventory where the target SharePoint site address is empty, the link will be mapped to the default target site (the address entered in the blue WikiTraccs.GUI window, in step 4).

Now there is a setting to restrict link transformation to only those entries in the Space Inventory that explicitly have a target SharePoint site address set. Other links will point to Confluence.

The setting is available via appsettings.json:

{
    "CustomSettings": {
        "Features": {
            "LinkTransformationMode": "needexplicittargetsite"
        }
    }
}

Note: Hard links to Confluence spaces are not covered, yet. This is a known limitation and will be added in a future release.

Furthermore

  • fix: on-prem Confluence groups are not always added to Confluence User and Groups list (a regression introduced with the previous release 1.14.2)
  • fix: hard links to Confluence attachments were transformed to page links

WikiTraccs 1.14.2

More Authentication Methods

Adding Personal Access Token as authentication method for Confluence, as well as Device Login for SharePoint Online.

Using Personal Access Tokens with Confluence makes the browser automation obsolete, that WikiTraccs so far relied on. This is available as of Confluence 7.9 and makes the authentication experience smoother. We are not dependent on the Chrome browser anymore. This also works with Confluence Cloud (where they are called API tokens).

With Device Login for SharePoint you can authenticate on a different workstation than the one WikiTraccs is running on. There are cases where M365 authentication causes challenges in certain environments and Device Login allows logging in on another workstation.

Performance Improvements

  • improved: page creation speed
  • fix: memory leak causing memory consumption to increase when running for days

There have been adjustments to the page creation logic, as now, while one page is being created, the next page is already being prepared in SharePoint. This can improve page creation speed (the raw page without attachments) up to about 25%. It is currently being monitored if this leads to increased throttling by Microsoft, as we are moving faster than before.

Confluence Cloud Compatibility Push

This release contains a major change regarding how users and groups are identified internally. So far, WikiTraccs used user keys and group names to identify users and groups. The cloud abandons the use of those and rather uses IDs everywhere. WikiTraccs can now handle those as well.

You’ll see a change in user- and group-related fields in the User and Group Mapping list, the Page Transations list, and the Site Pages list. Fields that used to contain user keys like abc123def now contain an identifier like user:key:atlassian:|onprem|abc123def (for users) or group:id:atlassian:|cloud|123456789 (for groups). Those identifiers explicitly specify the type, source, and (of course) value, which is vital for WikiTraccs when looking up and working with users and groups.

This change is backward-compatible. Identifiers that aren’t following the new format are assumed to be on-prem user keys or on-prem group names, respectively.

This change closes two issues which were open on the road to full Confluence Cloud compatibility:

The following issues are addressed at least partially:

The releases also gradually starts using Atlassian’s v2 API in the cloud.

Other Changes

  • change: SharePoint page comments are not disabled anymore for newly created pages, as this speeds up page creation; if you want to disable comments, please use this PowerShell script from the library: ToggleCommentsForPages.ps1
  • fix: path configuration via appsettings.json of WikiTraccs.GUI did not carry over to WikiTraccs.Console (attachment registry path, temp folder path)
  • fix: a current directory that differs from the WikiTraccs.GUI.exe folder could screw things up (appsettings.json not found, logs folder created somewhere else); now the current directory of WikiTraccs.GUI is forced to be the exe location
  • fix: a vertical tab character in a page’s title could prevent another page that link to that page from being created

WikiTraccs 1.13.1

  • fixed: certain empty tables could prevent pages from being transformed; those are now removed from the page

WikiTraccs 1.13.0

  • new: downloading of external images (like: not stored in Confluence) can be disabled in the settings; if disabled, those images will be transformed to links

image

  • fix: some progress bars went missing in the prerelease; those are back
  • fix: fixed a rare race condition when choosing migration target sites

⚠️ You should update to this release to minimize risk of running into the race condition issue.

WikiTraccs 1.12.29

  • new: adding SharePoint page modification time to “25” progress log file
  • improved: page migration speed
  • improvement: working around time zone issues that can affect the “25” progress log file, marking up-to-date pages as changed; differences that can be attributed to time zones being off are now detected and ignored
  • improvement: adding consistency check to check for large file uploads that were interrupted by Microsoft throttling
  • improvement: consolidating local file storage locations; those are now documented here in detail: File Storage
  • fixed: when page restrictions are narrowed down in the hierarchy of pages, dropped users and groups were not removed from the child pages

WikiTraccs 1.12.16

  • new: signed WikiTraccs binaries
  • new: checksum file in release package
  • improvement: adding additional logging to permission migration to better diagnose edge cases
  • fix: WikiTraccs could stop scheduling migration targets when accessing one target site fails; scheduling will now continue

WikiTraccs 1.12.6 (Prerelease)

Permission Migration Improvements

More cases are covered where WikiTraccs would previously give up, mainly in complex permission hierarchies.

WikiTraccs 1.12.5

Google Endpoint Fix

Time for Google’s once a year change of endpoints. WikiTraccs has been adjusted to handle those.

Permission Migration Improvements

  • new: in a hierarchy of restricted pages, when the principals of a parent page are not all mapped, the principals that are mapped will be inherited by the child pages (within narrow boundaries)
  • improvement: hardened permission retrieval against connection losses
  • improvement: when permissions cannot (fully) be applied to a SharePoint page (e.g. due to missing user mapping) permission inheritance for the SharePoint page will be broken nevertheless
  • improvement: better indication when being throttled by Microsoft (in the console and log file)
  • fix: reverted connection timeout back and increased to 600 seconds as it otherwise interferes with throttled requests

Verification Mode

This release introduces the mode Verify page contents.

image

When running in verification mode WikiTraccs will go over all migrated SharePoint pages, pull the corresponding original pages from Confluence, and compare contents. This creates updated progress log files.

WikiTraccs will check the following things:

  • check each code snippet web part for invalid characters in the backing CanvasContent1 list item field
  • check if the Confluence page contains words that are missing in the SharePoint page

The results will be stored in the “25” progress log file.

In the progress log file, each page entry will get an additional state indicator that is one of the following values:

  • skippedverify - did not check a page; this is the state for the progress log file that is created when starting the verification run
  • verified - checked a page and found nothing of interest
  • worddiff - the Confluence page contains words that are not present in the SharePoint page
  • invalidcodesnippetchars - a code snippet web part contains invalid characters in the CanvasContent1 field of the page list item

image

But why?

The reason for the introduction of the verification mode is an incident where pages seemed broken due to invalid characters in the backing field of the page. Note that several weeks had passed since the migration.

The content of a SharePoint page is stored in a list item field called CanvasContent1, in the Site Pages library. It is HTML which needs to adhere to certain rules. One rule is, that special characters like < and > need to be encoded properly. WikiTraccs does this since its inception in 2022. Nevertheless, something changed this content for some pages with HTML code snippet web parts to contain raw < and >. That made page rendering stop there.

The verification run checks for invalid characters in the backing CanvasContent1 field and highlights the affected pages in the progress log files. An easy solution is to delete and remigrate them.

Before recognizing that page content is simply not shown we assumed that page content had gone missing, which would be a blocker (and at the same time nearly impossible, since WikiTraccs already verifies the character count of transformed pages at the time of migration). It turned out that all page content was there, it was just not being displayed. But this initial assumption resulted in the verification run to also check for missing words. Note that updates to either the Confluence or the SharePoint page can also cause this check to be triggered.

In the future, the verification run might be extended with further checks or statistics collection.

Logging Improvements

Since the number of transformation modes is growing, WikiTraccs now shows the mode it is running in:

image

The log file and console also show the mode:

image

Possible values are:

  • MIG - Content migration
  • PRINCIPALS - Update ‘Created by’ & ‘Modified by’, as well as the dates
  • VERIFY - Verify page contents
  • PERM - Permission migration

WikiTraccs.GUI also contains several improvements for its progress bars.

WikiTraccs v1.11.16

  • adjustment: default timeout for connections to SharePoint has been decreased from 100 seconds to 40 seconds - NOTE: this change exacerbated a concurrency issue that showed when being throttled by Microsoft, that will be solved in the next release
  • fix: memory leaks that lead to high RAM usage

Please report back if you see RAM usage that increases over a period of multiple hours and reaches amounts of > 10 GB. Note that WikiTraccs needs at least as much RAM as the largest file that will be uploaded to SharePoint.

WikiTraccs v1.11.12 (Prerelease)

Jira Integration Improvements

So far, there were two assumptions baked into WikiTraccs: Jira can be reached to resolve issue links and issue tables, and WikiTraccs will wait for 60 seconds for Jira to respond. This is now more flexible.

  • the maximum wait time for reaching out to Jira can now be configured via the appsettings.json -> WiggleRoom.JiraMaxWaitTimeSec setting; this wait time is applied each time the the Jira-related Confluence endpoint is called
  • set WiggleRoom.JiraMaxWaitTimeSec to -1 to disable reaching out to Jira while migrating pages from Confluence to SharePoint; this is handy when the Jira application link is no longer functional
  • and a bug has been fixed: issue tables that showed the fixVersion always ran into a timeout when being migrated

WikiTraccs v1.11.9 (Prerelease)

Page Label Migration

Finally page labels are migrated as well. With this release WikiTraccs creates a new field Confluence: Labels (WikiTraccs) for the SharePoint Site Pages Library, that is of type Multiple lines of text, that will contain the labels for each page.

Why not migrate to managed metadata instead of text? Because it complicates things. Migrating as managed metadata would introduce dependencies to the term store, which might pull in additional stakeholders with regard to permissions, administration, and knowledge management. And what if you want to use a choice field instead? Those are decisions specific to each migration effort.

The current migration approach for page labels is to put them all into the Confluence: Labels (WikiTraccs) field, separated by the space character (which cannot occur in a label). All labels have a prefix. Valid prefixes in Confluence are “global”, “team”, and “my”.

So, for a page that has two labels foo and bar, the Site Pages library field Confluence: Labels (WikiTraccs) will have this content: global:foo global:bar.

You can use a PowerShell script to copy those values to another field of type managed metadata. And maybe clean them up a bit in the process.

Other Changes

  • improvement: Confluence code macro titles are now migrated as well, becoming code comments in the SharePoint Code Snippet web part

WikiTraccs v1.11.6 (Prerelease)

Changes

  • new: setting to switch off attachment sections on pages (via appsettings.json)
  • improved: link transformation now creates much shorter HTML for transformed links; this can help with large pages that previously ran into the platform limit of 2 MB per page
  • improved: cross-site attachment handling
  • improved: Confluence connection handling for better performance
  • fix: images linking to pages could lose the link
  • fix: file access issue in Selenium proxy
  • fix: attachment file names that are invalid on Windows could prevent pages from being migrated

Image transformation adjustments

TL;DR: Just for information, nothing to do.

Adjacent images are now transformed to a column of centered images in SharePoint. Adjacent image placement kind of worked for the old text web part that was used by SharePoint pages up until fall of 2023. The new text web part that Microsoft introduced cannot display adjacent images anymore, at all. No chance. So the default image transformation now shows the ugly truth and makes those images appear centered, one by one. I really hope that the SharePoint pages story evolves in the future to support adjacent images.

Converting adjacent images to single centered images is the new default behavior.

Note: You can get the old behavior back via appsettings.json:

"CustomSettings": {
  "Features": {
    "UseCkEditorv5Mode": false
  }
}

Using above setting will continue to create pages that display adjacent images until you edit a page for the first time. SharePoint’s page auto-upgrade will then re-arrange the images.

Note: A future release of WikiTraccs will introduce the option to convert adjacent images to image gallery web parts.

WikiTraccs v1.11.1

Improvements

  • new: you can set an optional Confluence authentication address so that the browser opens this address instead of the Confluence base URL
    • can be used to enter an SSO opt-out URL to authenticate with a different than the current Windows user account image
  • improved: error handling when running WikiTraccs under different Windows user accounts at the same time

WikiTraccs v1.10.24 (Preview)

Adding alternative mode to authenticate with Confluence, to work around authentication issues. See for details: Experimental alternative to obtain cookies.

In addition:

  • fix: update check detects updates when version is already up-to-date
  • fix: Jira issue table macro not transformed if macro has no column definition
  • fix: settings dialog shows leftover characters when switching tabs
  • improved: relaxing the connection check to succeed for on-prem 401/403 results
  • improved: adding sanity check for config file to detect invalid source authentication modes

WikiTraccs v1.10.12

Improvements

  • new: WikiTraccs checks for new releases
    • WikiTraccs shows when a new release is available (by checking this very GitHub release page)
    • the check is on by default but can be switched off in the settings
  • improved: the license key check is now more forgiving with regard to formatting errors and additional text in the license.txt file
  • fixed: code macros that need to be moved out of lists were not labeled and had their order reversed; the are now properly labeled and much easier to identify
  • fixed: character count metric for pages with Jira issue lists could show wrong value, despite the transformation being successful

WikiTraccs v1.10.9

Jira issue table snapshots - part 3

  • improved: links to the Jira issue list are now also added where Confluence normally omits those links (small number of issues)
  • improved: handling of issue lists when access is denied

Content transformation improvements

  • improved: bullet point lists and numbered lists don’t stick together anymore
  • improved: the yellow star emoji from Confluence is converted to a star instead of a circle
  • improved: handling of nested lists and adjacent breaks
  • improved: markers for de-nested tables are more descriptive

WikiTraccs v1.10.8 (Preview)

Jira issue table snapshots - part 2

The last preview release of WikiTraccs did not consider all Jira issue tables for transformation. This has been extended.

@-mention issues - part 2

There was a lingering user cache corruption issue that affected user mentions and could be triggered when switching WikiTraccs releases. This would make user mentions to be displayed as “User {{ID}}” instead of the user name.

I could finally identify and fix the root cause. Thank you Kees for providing me with valuable information. This is self-healing. Broken cache entries will be identified and purged.

Changes to inline images in lists

Microsoft is currently upgrading the technological basis of the text editor web part and breaks certain layouts in the process, but only when you edit pages.

Read about the background here:

With this release WikiTraccs changes the way bullet point lists and numbered lists with images are transformed.

Assume a page that has this content:

1. first point 2. second point with image    <image> 3. third point

Now when editing such a page SharePoint’s auto-upgrade kicks in and modifies the content to look like this:

1. first point <image> 1. second point with image                  2. third point

See how the layout and list numbering is screwed up?

Since I don’t expect Microsoft to do anything about this WikiTraccs now separates the text content and the images, like so:

🚧 Note: Some images were moved beneath the list as SharePoint does not support images in lists 1. first point 2. second point with image    🚧 See image 1.1 3. third point

<image> 🚧 Image 1.1 (moved)

This seemed like the only possible thing to do that doesn’t look too bad. Please let me know if you have better ideas. I just want to emphasize that SharePoint does not allow images to be placed in lists anymore. This is a regression in my books, but maybe it will be possible again in some future.

This change is active as of this release and affects newly migrated pages.

WikiTraccs v1.10.4 (Preview)

Jira issue table snapshots

WikiTraccs now takes a snapshot of Jira issue tables and puts this snapshot into the SharePoint page. The snapshot shows the content you would see when opening the page in Confluence. If the table cannot show all issues of the underlying query, a “show more link” will be added below the table. This follows the logic of Confluence.

Note: So far WikiTraccs already handled links to single Jira issues. Those were converted to hyperlinks pointing to the issue in Jira.

This is a first shot and I’m open for feedback. Does it make sense and where can it be improved? At least it seams better than a plain placeholder text, although the placeholder contained the JQL query. Should the JQL query go back into the pages? Let me know in the discussions.

@-mention issues

I got isolated reports about @-mentions not being transformed to the users’s display name, but to the Confluence user key (like “User {{long-user-key-here}}”). So far I have not been able to reproduce this, but this release contains some caching improvements that might help.

WikiTraccs v1.9.0

Storing the raw Confluence page contents in SharePoint

The raw storage format XML (background) of migrated Confluence pages is now being stored in a SharePoint document library Confluence Content Snapshots (WikiTraccs). You can find this library in the WikiTraccs site, it will be automatically created with your next migration.

The raw page content can help adjusting pages later on, e.g. when new SharePoint web parts become available, and allow the development of client add-ons that conduct additional tasks.

Refer to this sample PowerShell script on how to get the storage format XML for a migrated page: get-confluence-snapshots.

Comments migration

Footer comments can now be migrated and will become content of the migrated page (in case of multiple migrated translations, they will be added to the main page). This is the first approach to tackle #15 (please chime in if you have ideas or feedback).

Notes regarding comments migration:

  • opt-in; you can enable comment migration in the settings, default is off image
  • for now this covers footer comments, not inline comments
  • the raw storage format XML for comments is stored with the page’s in the Confluence Content Snapshots (WikiTraccs) list; this also includes inline comments, including resolved ones; you might access those comments there, if you need
  • migrating comments could bring pages to the maximum size of ~2MB (technical limitation of SharePoint); switch comment migration off if you experience errors

Other changes

  • new: adding a button to quickly jump to the WikiTraccs.GUI config file folder (to back it up or reset it) image
  • improved: the WikiTraccs.GUI settings now properly initialize with the WikiTraccs.Console default migration settings, when being opened for the first time (e.g. blog post migration is on by default)
  • improved: adding hidden excerpt macros to the default Macro Ignore List image
  • improved: the result of the Show Config as Text option is now more compatible with the appsettings.json format, that is used to configure WikiTraccs.Console

WikiTraccs v1.8.6

Increased visual feedback and improvements

  • new: buttons to quickly jump to log and update folders, directly from the blue WikiTraccs.GUI window
  • improved: more environment checks (log folder writable, WikiTraccs.Console blocked, connectivity for new endpoints)
  • improved: more visual feedback about what WikiTraccs.GUI is doing (connection check, logins, etc.)
  • fix: permission migration is prematurely interrupted by auto-shutdown if no content needs to be migrated
  • fix: progress bars for permission migration did not finish after all pages have been handled

WikiTraccs v1.8.4 (Preview Release)

Confluence Query Language (CQL) and Speed

  • new: select source pages via CQL query - see the updated documentation: Confluence Space Inventory
  • improved: cross-page linking to spaces, pages, and attachments has some edge-cases removed
  • improved: page creation and file upload speed increased up to 42%

Enabling CQL queries required changes to the page selection logic. This Preview Release lacks polishing with regard to:

  • labels/logs reading “space” instead of “CQL selector”
  • documentation needs to be updated to reflect that CQL selectors are an alternative to whole-space selectors

Actual page content migration should be unaffected. Please report any other issues you encounter.

WikiTraccs v1.7.6

Transformation improvements

  • improved: code macro transformation maps macro properties to available settings of SharePoint code web part (language, line number toggle, theme)

Furthermore, the license key format has been unified with WikiPakk, enabling future bundling options. Soon, issued WikiTraccs license keys will need this WikiTraccs release or newer.

WikiTraccs v1.7.4

Transformation improvements

  • new: WikiTraccs.Console will now auto-close after having migrated all scheduled pages
  • new: handling auibutton macros, converting them to links
  • improved: marking expand macro content with horizontal rule elements improves readability
  • improved: nested expand macros and panels don’t produce (de)nested tables anymore
  • improved: nested, invisible bullet point lists are now reduced to a single list, improving readability

WikiTraccs v1.7.1 (Update Mode Preview)

New Feature: Update Mode a.k.a. Delta Migrations

With this release it is possible to update previously migrated and now outdated pages in SharePoint. Updating outdated pages might be necessary when users keep editing pages in Confluence that have already been migrated to SharePoint.

You can read everything about this new feature here: Updating previously migrated pages.

WikiTraccs already detects outdated SharePoint pages and logs them to one of its progress log files. With this release you can mark pages you want to update and feed the file right back to WikiTraccs. WikiTraccs will then migrate the marked pages again, overwriting the stale SharePoint pages.

BREAKING CHANGE: This release changes the format of the 25- progress log file. See Monitoring Confluence to SharePoint Page Migration Progress for documentation of the progress log files.

There are some caveats when it comes to renaming already migrated pages in Confluence, that are highlighted in the documentation as well.

Please give it a try and leave feedback whether this is useful for you or not, and which adjustments you would like to see.

WikiTraccs v1.6.35

WikiTraccs.GUI usability improvements

Based on observations how folks use WikiTraccs.GUI some adjustments were made in the user interface. More stringent top-to-bottom flow, added links to the documentation, and more helpful button states.

Furthermore:

  • fix: Confluence Cloud connection check may fail, but shouldn’t

WikiTraccs v1.6.32

  • fix: attachment links to other pages sometimes couldn’t be properly transformed to SharePoint

WikiTraccs v1.6.31

  • fix: Confluence login for Chrome version 115 and up (#73).

WikiTraccs v1.6.29

  • improvement: hardening against connection errors
    • page creation is now retried several times, with increasing delays
    • space page retrieval and site preparation is retried as well
  • improvement: adding logging for throttling; when the app is throttled by Microsoft this is now visible as log message in the console while it previously could sit and wait for minutes without saying anything
  • improvement: lock busting for site preparation locks; when there was an issue during site preparation the stale lock is now undone after a couple of minutes; this should unblock the most common scenarios where provisioning gets stuck at this point
  • improvement: creating a new log file with every start of the application; this allows for easier log analysis
  • improvement: displaying the version number in WikiTraccs.GUI
  • fix: space processing stops when mapped to an inaccessible SharePoint site; this is now skipped and logged
  • fix: enabling/disabling of minor library versions when migrating to multiple new sites

Note: When running on an AWS EC2 instance, in a private subnet, behind a NAT gateway WikiTraccs’ connections to SharePoint are terminated frequently. This seems to be a known issue in said environment when apps use connection pooling. This release should allow migrating nevertheless as it adds retry loops for certain operations. The migration time thus will be increased in such an AWS environment.

WikiTraccs v1.6.11

Highlighting not-anymore merged table cells

Since SharePoint Online does not support merged table cells WikiTraccs cannot transform tables 1:1 to SharePoint. This release adds markers for table cells that once were merged.

For more details about table transformations and merged table cells refer to this blog post: How to migrate rich Confluence tables to limited SharePoint tables?

:grey_exclamation:Marking merged table cells is the new default.:grey_exclamation:

Note: If you want to revert to the former behavior of not marking merged table cells you can use appsettings.json. This page has the snippet needed to configure this: Sample Configurations

Furthermore:

  • fixed a bug that prevented Confluence blog posts from being migrated to SharePoint when a blog post had the same title as a page

WikiTraccs v1.6.8

Better scheduling for large spaces, and Confluence Cloud login fix

So far WikiTraccs first got the list of pages for a space and then started migrating those pages.

Unfortunately, with increasing page count, Confluence gets slower in providing the page list (see #63). This meant so far that you had to wait quite some time until WikiTraccs started migrating a large space.

This has been changed. After retrieving the first pages for a space WikiTraccs already starts migrating those. This should save some time when migrating large spaces (> 15000 pages).

Getting the pages is done in batches, so a list of 15000 pages is not retrieved at once, but in smaller batches. The batch size so far was 100, this has been increased to 200, which seems to be a maximum. Please open a support ticket if this does not work in your environment.

Two issues around Confluence Cloud have been resolved as well, namely #28 and #65, which prevented successful login detection.

Note: This is marked as a pre-release for now because the scheduling logic changed quite a bit and will be monitored until the next release.

WikiTraccs v1.6.6

This release has two additions to features added in the last releases.

Blog posts that have been migrated from Confluence to SharePoint are now promoted to news posts in SharePoint, so they appear in news web parts.

Hard links on Confluence pages that were detected by WikiTraccs but could not be transformed to page links in SharePoint now increase the “Inaccessible pages” and “Inaccessible links” counter that is available as field in the Site Pages library.

WikiTraccs v1.6.4

Confluence kind of monitors links between pages. When updating the title of a page Confluence takes care of updating incoming links to this page. Those links are called soft links and should be the majority of links. When migrating Confluence pages to SharePoint WikiTraccs takes care of transforming soft links to SharePoint page links.

There is another kind of link - the hard link. Those links are plain old HTML links that Confluence is oblivious of. Technically, they appear like any other text content. And also technically, they lack important metadata that is needed to locate the target page (page ID, space key). Sometimes those links make it into a page. And as long as the target page does not change much this works, until it doesn’t and they break.

With this release WikiTraccs looks out for hard links and tries to figure out the target page. If that is successful the hard link is transformed to a proper page link in SharePoint.

There are some limits to this hard link transformation: it works only for links to pages, not attachments. And it only works for links pointing to the current page version. Hard links to older page versions cannot be converted since older page versions are not present in SharePoint. Also, the link text stays as it is - so a link might look like still pointing to the source Confluence system, yet properly links to the migrated SharePoint page.

This addition should reduce the manual post-migration labor a bit. Feedback is appreciated, either as feature proposal or discussion.

WikiTraccs v1.5.0

Migrating blog posts!

So far the focus has been on migrating Confluence pages to SharePoint with blog posts getting not much demand. But this is something of the past.

WikiTraccs now supports migrating blog posts to SharePoint as well.

Blog post migration can be turned on in the settings dialog that is available in the main menu bar of WikiTraccs.GUI via Settings > Configure Transformation. There, choose Migrate blog posts. WikiTraccs then will pick up blog posts in your next migration.

This setting is turned off by default.

WikiTraccs 1.4.6

Bugfixes and more status info in WikiTraccs.GUI

This release fixes a timezone-related bug that could mark all pages as outdated in the progress log files. Note that this only affects the log files and not page metadata.

Furthermore the progress bars showing space migration progress should now behave and properly reach their end after migrating all Confluence pages of a space to SharePoint.

WikiTraccs.GUI got a small log text field highlighting important information like “X outdated pages were found” or “All done”. This information is also available in the live console window and the log files, but it’s friendlier and quicker to have it right in the GUI.

The behavior of the space migration progress bars has been slightly changed. They will reach 100% even if outdated pages were found and subsequently skipped. But the new log text window will highlight the fact that there were outdated pages. The progress log files then provide a detailed list of those pages.

WikiTraccs 1.4.2

Additional Language Migration Mode

This release adds the first additional language migration mode: migrate all languages of a Confluence page to one target SharePoint page.

This is the new default setting.

image

This is relevant for Confluence pages that have been translated using Scroll Translations. WikiTraccs detects those languages and migrates them all, one after another, into one target SharePoint page.

If you want the old default behavior - migrate only the language with most content - you can switch it back in the settings dialog of WikiTraccs.GUI.

This release also increases the default timeout for Confluence API calls to 5 minutes, up from 30 seconds to better cope with slow responses.

WikiTraccs 1.3.14

More Sanity Checks when using WikiTraccs.GUI

There is a list of nuisances that got smaller with this release:

  • the Confluence connection test now also checks if the API can be reached; so far this only happened when starting the migration, creating a confusing state where the connection test succeeded, but starting the migration might still fail
  • the SharePoint connection test now checks that the SharePoint site addresses point to a site root (subsites are not supported)
  • small formatting fix for the video links introduced in v1.3.13

WikiTraccs 1.3.13

Solving very specific Issues

This release solves two issues that cropped up in migrations.

The first issue is #51 that needs support for handling Confluence images that are in fact… videos. WikiTraccs should now detect those and apply the current default handling for videos: adding a link to the page that points to the video file in the attachments.

The second issue is #46 where it surfaced that Confluence can return duplicate page IDs when being asked for a space’s pages. WikiTraccs now de-duplicates the list of pages that it receives from Confluence which hopefully solves this issue (via #52).

Note: Of tremendous help while diagnosing those issues were WikiTraccs log files. There’s a page dedicated to those log files, where to find them, and how they help: Troubleshooting Strategies. It’s best to always send them over as described on the page.

WikiTraccs 1.3.8

This release fixes an issue where preparing a target SharePoint site failed when running WikiTraccs on a non-English system for a site with non-English default language, with a user that has English set as default language.

WikiTraccs 1.3.7

Reliability and Traceability Improvements

This release improves handling of Confluence user accounts that cannot be found in SharePoint. This sometimes caused WikiTraccs to create an empty placeholder page in SharePoint. This has been tuned down.

WikiTraccs will from now on log the missing account names to the Transaction Log field for affected pages and set the Check Principal Mapping flag. This allows to update editors and authors later, after configuring a proper account mapping.

Furthermore the logging of handled pages has been extended. The number and list of page IDs WikiTraccs got for each space can now be seen in the console and log. This can be used to diagnose missing pages and whether this might be due to permission configuration, or some other reason.

WikiTraccs 1.2.2

Macro Ignore List to exclude macros from the migration

This release of WikiTraccs introduces the Macro Ignore List.

Use the Macro Ignore List to remove certain macros from the Confluence migration to SharePoint. This is useful for macros that are only visible when editing a page in Confluence, but are visible on the SharePoint page after migration.

Read all the details in this blog post: Ignoring macros when migrating pages from Confluence to SharePoint

WikiTraccs 1.1.1

More Migration Progress Insights

With this release WikiTraccs will generate progress log files giving more detailed insights into the migration progress.

Which pages have been migrated from Confluence to SharePoint? Which pages are left? Which pages need an update (in preparation of the update feature to come…)?

Those questions can now be answered. Have a look at the documentation on where to find the files and how to interpret them: Monitoring Confluence to SharePoint Migration Progress

GitHub Releases

Releases are available for download on GitHub.