If you're like many of my clients, you're implementing SharePoint along with one or more existing ECM solutions.  In some cases, clients want all of their content in the ECM engine either to take advantage of their existing records management programs or simply for consistency.  Others want to use the document libraries in SharePoint for all of their collaboration and project efforts, migrating records later when needed.  Every company is different so how SharePoint is ultimately linked to the ECM system depends upon the requirements of the client, but here are a few things to think about as you get started:

1. A consistent user experience:  SharePoint sites are very easy to create.  As a result, just about anybody can and does create unique sites.  If you want consistency in how sites are created and where content resides, you will need to have in place a governance program for your SharePoint system.  That governance program should be an extension of the ECM governance program you already have.  Since most companies don't have a governance program, Microsoft publishes a number of templates to facilitate the whole thing.  The big win here is, you'll want to make sure that your content resides where you need it to, and it's classified the way it should be.  That may mean limiting who can create sites or how sites are created. 
2. Know the functionality of your Web Parts:  Most ECM companies now provide Web Parts for SharePoint that enable users to access content that resides within the ECM engine directly from SharePoint.  In most cases, this functionality is limited so I suggest you have a firm grasp on what does and doesn't work for you.  For those who want to ensure all content resides in the ECM, make sure you have the capability you need in the Web Part to accomplish that requirement.  In most cases, the capabilities of the Web Parts are very basic.  While you're at it, make sure you are fully aware of the SharePoint document library functionality you're giving up as well. 
3. Does content start in SharePoint and move to the ECM?  In most cases, the ECM vendors provide a method for content to be created in SharePoint and then pushed to the ECM engine at a later time.  That "push" process will often leave a pointer in the SharePoint system so that users can still access it from the SharePoint document library.  That's fine if SharePoint will always be your user interface, but in most cases, that isn't true.  Consider the following:
   • If you need to migrate content from file shares or other systems, that content is mostly likely going to be migrated directly to the ECM engine.  If the migration is not pushed through SharePoint, the SharePoint system will not likely have any awareness of the migrated content because it did not go through that push process.
   • Content that existed in the ECM engine prior to implementing SharePoint may not be visible from the SharePoint engine for that same reason.  That leads us to search or browse...
4. Is it a document or a list?  Some content in SharePoint is considered to be a "list" rather than a document.  Most ECM engines understand documents in SharePoint...but not lists.
5. What about search?  Where will your users be searching from?  Does your vendor provide a search Web Part for SharePoint?  Does that Web Part allow you to search both the ECM and the document libraries and return one result?  Separate results?  Can I search from the ECM interface and still find content in SharePoint document libraries?  Part of the answer lies in your search strategy, but you should also consider what your primary interface will be.  If users will use both the ECM interface and SharePoint, you'll need to determine if the search experience needs to be the same from both.
6. Are your information architectures consistent?  If you do push content from SharePoint to your ECM engine, are your information architectures and taxonomies in alignment?  Is the browse experience the same in SharePoint as the ECM engine?
7. Don't forget about Security:  One thing to consider is the alignment of the security models between SharePoint and the ECM system.  Are they the same?  Should they be? 

There are a lot of options when considering your combined SharePoint and ECM solution.  The good thing is that you have options.  It will require strong planning and a bit of communication with your ECM vendor to ensure the functionality you need from the SharePoint connectivity tools meets your needs.  While Microsoft provides nice templates to get you going with SharePoint governance, you'll need to ensure that your governance processes encompass both SharePoint and the ECM system. 

I hope this information helps

Michael

www.kestralgroup.com