SharePointforAll
This is the best place to find out everything that Quest is doing around SharePoint, plus where we will give guidance on all things SharePoint
Quest SharePoint Experts Mirror » All Tags » Migration projects (RSS)

Browse by Tags

  • Ten Ways SharePoint 2010 Will Impact Your Notes Migration

    Here is a link to my new white paper, hot off the presses: [ link ] Abstract: Many organizations are moving from Lotus Notes/Domino environments to Microsoft Exchange Server, SharePoint and Office. However, applications that are migrated from Notes to SharePoint may need to be rebuilt – typically an expensive and time consuming process. Even then, the new applications may not function as well as the legacy ones. But with the release of Microsoft SharePoint Server 2010 and SharePoint Foundation 2010, things have changed. This paper discusses 10 ways that SharePoint 2010 will change the game for enterprises of all sizes who want SharePoint to replace or enhance their Notes environments. You will learn about major platform and functionality improvements and discover how SharePoint 2010 simplifies...

  • All Database View/Report Columns

    With each new release of Notes Migrator for SharePoint , we add new functionality and this usually means new database properties that you can view in the Migration Console. For example, our new “Blocked / Oversized File Detection” feature gives you four new columns that you can add to any database view or report: With version 5.3, we are now up to 172 columns that you can display for each Notes database in your environment. These columns are set in a variety of ways: Discovery Data Analysis Design Analysis Usage Analysis Automatic Classification Automation via Class Rules Manual Triage Performing Migrations While we document all the available database columns in the appendices of our User Guide, it still can be difficult to understand what columns are available to solve a particular problem...

  • Automatically provisioning lists that use the qDiscussion web part

    A few months ago I shared my excitement about the new Discussion web part from Quest [ link ]. To recap, customers switching from the Notes discussions (in the Discussion template, QuickPlaces, Team Rooms, or custom applications) to the SharePoint’s standard Discussion Board template have a few nasty problems: The user interface is quite different: No twistees, No threaded tree-view, like you had in Notes. Instead you view the parent documents in a flat view and then you open a page that shows the entire thread. Only the top-level documents have subject lines. If your Notes users entered unique subjects on the response documents (I know I always did – in many cases I typed my entire thought in the subject line and left the body blank), then you have data loss! Quest’s qDiscussion web part solves...

  • Cool stuff in SharePoint 2010 that Notes customers will love: InfoPath everywhere

    One of the biggest barriers to moving large numbers of Notes applications to SharePoint is the cost of rebuilding the complex applications. As covered previously [ link ] this cost is often overstated and can be mitigated by a good understanding of how to leverage out-of-box SharePoint features and code reuse, but it is still a very real issue. SharePoint 2010 contains many advances that will dramatically reduce the cost of application development and (even better) will allow tools such as Notes Migrator for SharePoint to do a lot more of the work for you. We will cover things such as improvements in declarative workflow, dynamic scalable views, ASPX pages and offline capabilities in other posts. But first I want to talk about InfoPath. InfoPath is, of course, Microsoft’s primary solution for...

  • Cool stuff in SharePoint 2010 that Notes customers will love: Go Offline

    I remember the SharePoint Conference three years ago where SharePoint 2007 was announced. I was in the Proposion Software booth (we had not been acquired by Quest yet) and had a chance to talk to a lot of Notes customers who were adopting (or at least looking at) SharePoint. There was a great deal of excitement there as most people were seeing SharePoint 2007 for the first time and they were very happy with what they saw. At the time, the two biggest reasons that people felt they could not move their Notes applications to SharePoint were (1) the lack of document level security and (2) the inability to implement even simple workflow logic. That week, the consensus was that Microsoft nailed both of these in a big way with SharePoint 2007. Sure enough, the next few years saw a new wave of Notes...

  • Understanding DEI and other complexity metrics

    The analysis component of Notes Migrator for SharePoint calculates several complexity metrics for each database, including Microsoft’s Design Element Index (DEI) method. These are described at a high level in the documentation, but we sure do get a lot of questions about exactly how those numbers are computed. I will attempt to give an answer here, and then at the end of the article I will describe why you should NOT take these numbers too seriously. Microsoft’s DEI method is really simple. (As I have said many times, it is currently TOO simple.) We just count up each type of each element and decide which DEI column it goes into, according to Microsoft’s guidance. switch (Type) { case "Form" : if (Net < 2) return 1; if (Net < 5) return 2; if (Net < 11) return 3; if (Net <...

  • Automated provisioning of custom templates that use Quest Web Parts for SharePoint

    Notes Migrator for SharePoint is great at provisioning lists, libraries or even entire SharePoint sites from your custom templates. This is incredibly useful when migrating lots of custom Notes applications that are based on the same Notes template (or at least share a common design). For example, I have one customer who has 10,000 team sites based on a completely customized Notes template and is migrating them to 10,000 SharePoint sites based on a highly customized site template. Now that’s code reuse! Quest’s Web Parts for SharePoint product is one great way to build those custom application templates. As described previously [ link ] this tool has been very popular for companies wanting to “replatform” their custom Notes applications because the web parts help to reproduce much of the functionality...

  • Migrating Notes workflows that implement “dynamic” document security

    We have discussed various issues about workflow in the past [ link ]. To make a long story short, there is no way to press a button and magically translate Notes code-based workflows to SharePoint declarative workflows, but Notes Migrator for SharePoint does an excellent job at migrating your workflow state. Recently we have been getting a few questions about how people should handle workflows that automatically change the security of the document as it moves through various workflow stages. For example, imagine a Notes application that lets an “Author” add or update travel requests until they are ready to submit it. Once the request is submitted, however, the Author can no longer make changes and it us up to her “Manager” to approve it, reject it, or make further changes. Real-world Notes...

  • Migrating workflow state and approval processes

    As described previously, when migrating Notes workflows to SharePoint workflows you are really switching from code-based workflows (logic encoded in button events, agents, etc.) to declarative workflows. And using Notes Migrator for SharePoint, you can migrate your workflow state so you can preserve in-progress workflows between the two systems. To achieve this, simply migrate the (status fields, next review, due date, whatever) as data columns in your list items, InfoPath documents, Word documents, etc. Depending on how you designed your workflow, you may be done at that point, or you may need to customize it. The relevant part is that when the workflow starts up for newly written list items, it should be designed to examine these columns and “advance” to the right state. For example, the...

  • Upcoming webcast: Streamline Your Migration of Complex Notes Applications

    I just finished the last rehearsal of this upcoming web event on migrating complex applications. This looks to be a really good one for people who have a lot of non-trivial Notes applications they want to migrate. The focus is on maximizing what you can accomplish without writing code, by simply learning how to truly leverage the awesome power of SharePoint and related tools. The emphasis, of course, is on those features that will come in particularly handy for someone intent on re-platforming Notes applications. Co-presenting with me will be Dan Galant from Summit 7 (sister company to MindSharp) who delivers consulting and professional services around the Microsoft platform. Get this on your calendar now by registering here: http://www.quest.com/events/listdetails.aspx?contentid=10249 . Read...

  • Migrating Lotus Notes Applications to Microsoft SharePoint: Understanding Application Complexity and the Value of Consolidation and Automation

    Here is a new white paper by yours truly: http://www.quest.com/documents/landing.aspx?id=9746&prod=352 . In some ways, this paper is a direct challenge to the four-quadrant system and Design Element Index (DEI) algorithms that have been floating around recently for understanding the complexity of Notes applications. Even though Notes Migrator for SharePoint implements some of these methodologies, I have a strong belief that such complexity calculations do not adequately address the practical question of which applications are going to be easy to migrate and which ones are going to be difficult. What organizations really need is a way to rank applications according to how much effort will be required to migrate them to SharePoint and to recognize the rare cases where SharePoint may not be...

  • Using the new Link Tracking Service Finalizer/Updater

    As described in yesterday's post [ link ], the Link Tracking Service allows Notes DocLinks to be migrated as "Dynamic Links" instead of Direct Links. As users click on Dynamic Links they are automatically redirected to the current location of the target document, whether or not it has been migrated yet and regardless of whether the linked-from or link-to document was migrated first. When we describe this feature to customers, two important questions often come up: What happens if I move my content, change the external host name of my SharePoint farm, etc? Will the Link Tracking Service still send users to the right place? What happens when I am done migrating? The Link Tracking Service is cool, but am I stuck with it forever? Notes Migrator for SharePoint version 5.2 [ link ]...

  • Link Tracking Service recap

    Before diving into the new ways we have to manage your links in Notes Migrator for SharePoint 5.2 (tomorrow's post), let's do a quick review of how Quest's Link Tracking Service works. Notes documents can contain DocLinks, which are links to other Notes documents. These links can be represented as "traditional" little yellow icons or "modern" text hotspots, as shown below: If you were to migrate this document to SharePoint, you would want to make sure that your document links continued to work in all of the following cases: The documents that your links point to are still in Notes - When a users clicks on a link, they should be connected to the document in the Notes client. The documents that your links point to have been migrated to SharePoint - When users clicks...

  • Thirteen ways to migrate a document to SharePoint

    Wow! With two new options being introduced by Notes Migrator for SharePoint 5.2, we now have 13 distinct choices for migrating a Notes document. This gives us a fun way to convey one of the dimensions of our tool's value (the unparalleled breadth of target options) in screen shots. Rich text document in Notes (the "before" version") 1. Migrate to Standard Lists (Discussion, etc.) 2. Migrate to Custom Lists 3. Migrate to Content Types (also note the support of SharePoint's out-of-the-box approval process and version history) 4. Migrate Attachments only (with metadata) 5. Format as HTML files 6. Format as MIME files 7. Generate Basic pages 8. Generate Wiki pages 9. Generate Web Part pages (set any web part property from your Notes data) 10. Generate MOSS Publishing Pages...

  • Mapping Notes Groups to SharePoint Groups

    Notes Migrator for SharePoint has always had a number of capabilities for migrating the security of your Notes applications to the equivalent security constructs in SharePoint. In particular we have had two distinct "group mapping" options: Map Domino Directory Groups in your application's ACL to Domain Groups (usually AD groups) Generate SharePoint Groups (with members) from Roles in your application's ACL In both of the above cases, the tool sets the permissions correctly for the site, list, or document you are provisioning. With Notes Migrator for SharePoint 5.2, we now support a third option: Generate SharePoint Groups (with members) from Domino Directory Groups in your application's ACL In other words, as indicated in the dotted line below, we are now crossing the...
1 2 Next >
(c) 1987-2010 Quest Software Inc.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems