One of the many challenges with migration is that the source data is dynamic and continuous. It is hard to control data from changing unless a protocol is setup to block modifications of content into the source system. This approach is great for migration but bad for business because it creates downtime and/or work overhead. Users cannot use the platform to publish and create new content when the system is blocked, so he must either wait for the system to return to normal, downtime, or draft the new content into a temporary format, then copy and paste the content into the publishing format and then massage the content to fix any formatting issues. If the content requires provisioning, then the user must also tweak the correct settings for the content. These all add to the work overhead and downtime because he has to copy and paste and reformat content and he has to wait for the content to be in the platform before he can change the correct settings.
This is a new post!
Learn how to use PowerShell to incrementally migrate only new posts.
Welcome to WordPress blog about WordPress to SharePoint synchronization! After you read this, you should delete and write your own post, with a new title above. Or hit Add New on the left (of the admin dashboard) to start a fresh post.
Here are some suggestions for your first post.
- You can find new ideas for what to blog about by reading the Daily Post.
- Add PressThis to your browser. It creates a new blog post for you about any interesting page you read on the web.
- Make some changes to this page, and then hit preview on the right. You can always preview any post or edit it before you share it to the world.