Author Archives: Admin

Security is one of the most important aspects of any content migration. Security considerations impact migration in a number of ways, summarised simply below;

  • Understand the security in the source.
  • Securing the content during migration.
  • Appropriately applying security in the destination.

This article is concerned with securing the content during migration.

In delivering content migrations we do 4 key things to ensure security;

  • We Understand
  • We Plan
  • We Design
  • We Implement

We Understand

We understand that different organisations, jurisdictions, and content will be subject to differing legislation, regulation, and policy considerations. For example;

  • PCI
  • EU Model Clauses
  • General Data Protection Regulation
  • Australia Privacy Act
  • ISO
  • Data Residency
  • South Africa’s Protection of Personal Information (POPI) Act

We Plan

It is critical in all content migrations that data should be treated with respect. We work with our clients to agree an appropriate content migration security plan as part of any content migration.

Plans are normally specific to client, source, destination and the nature of the content.

We Design

We design our migration tooling with security at the forefront of considerations.

We design our client’s migration processes again with security at the forefront and reflective of the agreed content migration security plan.

We Implement

We implement security measures across our migration tooling and processes. These will be appropriate to each aspect of the migration, for example;

  • Extract
  • Transform
  • Load
  • Remote Access


Appropriately secure the extraction process. For example if the source is a cloud based system where https:// has been deemed appropriate for user access then this will likely be appropriate for the extract aspect of the content migration.


Appropriately secure the transformation process. This may be simple but important measures such as minimising or eliminating the amount of content which is written to any temporary location and ensuring it’s expedient removal.


Appropriately secure the load process. When loading to SharePoint Online for example we communicate to SharePoint using the https protocol and encrypt library content using the Advanced Encryption Standard (AES).

Remote Access

Appropriately secure remote access. If remote access to client systems is required then this will be secured in accordance to the agreed content migration security plan.

In Conclusion

Talk to us about how we can secure your content migration.




If you wish to export content from Xerox DocuShare there is a server based tool (DSExport) which will provide the contents and meta data of a collection; the latter in XML format.

We are frequently contacted by users who have tried to use this mechanism for the purposes of migrating large amounts of content to new content repository such as SharePoint and have found that it does not work well for large or complex migrations in which case we use our migration software to transfer the content directly from Xerox DocuShare into the destination platform in a single step with DSExport involved.

Examples using dsexport

dsexport -r -d \export Collection-141 — exports Collection-141 and all its contents to XML.

The following files are exported:



D:\export\Collection-141\documents\Rendition-11_2.29 other r.02.doc





D:\export\Collection-141\documents\Rendition-16_2.26 R02.doc


D:\export\Collection-141\documents\Rendition-18_2.29 imari r0.2.doc

D:\export\Collection-141\documents\Rendition-19_2.29 imari.doc

D:\export\Collection-141\documents\Rendition-20_2.19 R02.doc

To export specific files in a collection:

Suppose a Collection-X named, Strong test, contains a URL named e-HongKong site, a Collection-Y

named khong guan biscuit and a Document named test.

Example 1:

a.     Create a file named cond.txt, that contains title = .*ong.*

b.     In a command line, run dsexport – r -c cond.txt -r Collection-X.

This only exports the object whose title contains ong. So only the Strong test collection, e-

HongKong site URL and khong guan biscuit are exported.

The test document is not exported.

Example 2:

a.     Create a file named cond2.txt, that contains title = .*[h|H]ong.*

b.    In a command line, run dsexport –r -c cond.txt Collection-X.

This only exports the object whose title contains hong or Hong. So only the e-HongKong site

URL and khong guan biscuit are exported.

The test document and Strong Test collection are not exported.

Example 3:

a.     Create a file named cond.txt that contains create_date> DD/MM/YYYY

Example:          create_date > 1/19/2011

create_date <11/25/2011

b.    In a command line, run dsexport -r -c cond.txt Collection-X

This only exports the objects whose create date is between 1/19/2011 and 11/25/2011. 


A typical first step in many migration projects is to research, select and procure a migration tool.

Content Migration as a Service (CMaaS) changes this concept. CMaaS also delivers the outcome not just the means to achieve it.

Sometimes CMaaS is a better approach for your scenario.

We have put together some examples of how we find CMaaS has helped our clients which we hope will help you to make the correct choice for you scenario.

Delivery Accelerator

CMaaS typically accelerates migration delivery.

The team must understand the desired outcome so that the CMaaS partner can deliver. This moves decision making to the fore.

You will be working with a delivery partner who has delivered many migrations. Having an experienced partner brings speed, clarity and confidence to decision making. Migration projects can often be about difficult decisions that balance both advantages and disadvantages of a given approach so this can be a significant contribution.

Team Focus

Content migration is typically one part of a larger project.

Invariably the purpose of that overarching project will be to bring a significant improvement or efficiency to the organisation.

Arguably the project team wants to be focused on the creation and delivery of that future and the “one-time” content migration element can be a distraction.

CMaaS permits the team resources to focus whilst a partner delivers the “one-time” content migration element.

Align Perspectives

Different teams and personnel within your organisation will have different perspectives on any content migration project.

An experienced CMaaS partner will understand this landscape and work with your team to align this with the detail of the content migration.

To exemplify this we should consider that content migration is frequently not only concerned with moving content from A to B but also with ensuring that the content migration honours;

  • Use and Consumption, e.g.
    • Continued use and consumption post migration
    • Arrangements for use and consumption during migration
  • Governance, e.g.
    • Permissions
    • Security
    • Retention
    • Disposition
    • Compliance
  • Infrastructure, e.g.
    • Bandwidth
    • Storage

Responsibility for each of these areas is likely split between personnel. A good CMaaS partner will understand both this landscape and also drivers such as regulatory and legislative compliance.

Team Resources

A content migration project can place significant demand upon team resources.

CMaaS reduces this demand.

It is also the case that most content migration projects are a “one-time” deal. Without a migration partner it is likely your organisation will incur the additional learning curve costs of internal or contractor resources only for these skills to be redundant as soon as the project is delivered.

Small Content Migrations

The benefits of CMaaS becomes very acute for small migrations.

For a small migration the cost of the CMaaS engagement may well be similar to or less than the cost of the tooling. When this is set against the background of team resource costs and other factors a strong case is made, commercially, for CMaaS.


Every business we have ever worked with has content stored in multiple places.

Content consolidation is the act of distilling the number of such repositories down to the minimum and in each case the best for the content concerned.

Consolidation invariably entails migrating content out of and retiring legacy repositories.

We can migrate these repositories for you –

When we label a repository as legacy we should be careful to understand that this means legacy to your organisation. Put a different way a legacy repository may be supported by the manufacturer but your organisation has determined it no longer wants to maintain the system.

Consolidation is achieved by successful execution of one or more migration projects.

Successful consolidation would at least achieve these benefits.

1. Reduce Cost

Once all content has been migrated out of a legacy repository cost can be reduced:

  • Software manufacturer support and licences costs are eliminated.
  • Infrastructure (hardware, power) costs are eliminated.
  • Training costs for users are reduced.
  • Ownership costs such as internal IT costs are reduced.

2. Reduce Risk

With content migrated to a preferred platform risk is significant reduced:

  • Legacy platform risks such as failure, stability, security and data loss are circumvented.
  • Skills (expertise) risks are mitigated.

3. Increase Productivity

Content consolidation normally reflects a productively increase:

  • Single search – Ability to find all content in a single search.
  • Single knowledge set – The requirement to only learn and master a single electronic content management system.
  • Single administration point – Only a single system for which to set permissions and execute other administrative and governance activities.

We specialise in content migration with a specific focus on migration to SharePoint.

Put simply we help our customers to deliver their Migration Projects by building robust Content Migration Processes leveraging our Content Migration Tooling.

See also

Migration Project

Content typically refers to document content (Word; PDF; Excel etc), or HTML presented content (Web Pages). Content could also mean structure (Folders), lists (conversations, tasks, calendars). All content has some form of meta data associated with it.

A need for content migration will normally arise from an overarching project.

Typically such a project would be :

  • A migration project to a new EDRMS, WCM or Collaboration system such as SharePoint.
  • A consolidation project whereby you consolidate to a single EDRMS, WCM or Collaboration system such as SharePoint.

Such a project will have it’s own understood drivers and benefits case.

We believe it is important to recognise that this overarching project is different from the content migration itself as the overall project will address not just content but also people and processes.

The exception to this is an archive project in which the main driver is correctly retaining the content as opposed to actively or extensively working with it. In such a project the element of people and process is reduced and the content migration process comes to the fore.

Content Migration Process

To satisfy the requirements of a migration process a content migration process normally needs to be built or at very least configured.

The process could be simple or complex. In order to facilitate the later we use PowerShell.

The process will undoubtedly migrate content but may also:

  • Configure the destination
  • Deploy structure such as sites, libraries or folders.
  • Deploy meta data such as lookup lists
  • Set Permissions
  • Transform the content
  • Transform the meta data

The process will additionally include:

  • Reporting
  • Reconciliation
  • Tracking
  • Validation

In short the content migration process is tailored to the needs of the project and further ensures all content is correctly transferred and validated.

Content Migration Tooling

Content migration tooling avoids reinvention of the wheel.

Good migration tooling encapsulates all common functionality that your migration process will need so that it can be built more easily and cost effectively.

Professional content migration tooling normally leverages PowerShell scripting for accuracy and repeatability.

We continually develop our own migration tooling so that we can work with you to deliver a very effective Content Migration Process in minimal time and at minimal cost. We have connectors for most source repositories.


Sensitive Information Types in Office 365 allow you identify sensitive content that is held in Exchange and SharePoint Online and restrict its use.

You can leverage existing rules (e.g. Credit card numbers) or define your own.

The rules are applied as part of the search crawl.  The content of a document or email is analysed and if, for example, a credit card number is found a property is set on the document.

Depending on the licence that you have for Office 365 you can then run searches to identify the offending content or apply policies that restrict its use.

Sensitive information types are not guaranteed to find every offending document but they are a great broad brush approach to information security and compliance.

If you are working with scanned images that have been OCR’d and converted to PDF+Text then there is a good chance that these will be identified.

Further reading;


Microsoft has added Communication sites to SharePoint Online.

These allow users to create aesthetically pleasing micro sites within a SharePoint Online tenancy.  See below;

Communication sites are a useful addition to the capabilities of SharePoint Online and make it easy for users to create a nice responsive site.

Customisation capabilities, however, are not as rich as you had with classic SharePoint publishing sites so we will be working with those for a few years yet.

The standard supplied modern web parts are ok and with effort you can write your own using the SharePoint framework.

Further reading;


HP provide an export connector (release script) for Kofax Capture to enable you to export scanned documents into HPE Content Manager (formerly HP Records Manager / Trim Context).

This has been around for a while and is used in most HPE Implementations in it’s most basic form.

You can find the reference information here.

Sometimes it’s good to look a better ways of doing things.

This article assumes that you are comfortable with the basic operation of the export connector but are looking at ways to improve, basically getting a more joined up capture system.

We are going to look at;

  • The Basic Experience
  • A Better Experience (For a lookup scenario)
  • Implementing that experience
    • Configuring the Export Connector
    • Writing a Lookup Function
    • Calling the Lookup Function
    • Fine Tuning

Ok so here goes.

Basic Experience

A lot of times the export connector is used in manual mode.

Every time a document is indexed the user sees the export connector (The panel underneath Trim Control Panel), clicks “Create Record”.  They then get the Record Creation screen which they fill in using the mouse.  If the names of your Kofax field and Trim fields align then they are defaulted (See Trim_Title in this example).

Better Experience

So a better experience is not to see the Export Connector at all.  If the record can be created using just Kofax then manual indexing will be quicker and if you are using ICR / OCR / Recognition it can be potentially automated.

So we want something like below.  We don’t really want to see that ugly record creation screen.

User just keys in the unique reference and the rest of the data should be pulled in from Records Manager, they can eyeball the image to make sure it matches, then the record should be automatically created.


Ok so we know what we want but how to do.

Configuring the Export Connector

So to ensure that the export connector is working but not visible we set it to automatically invoke.


Writing a Lookup Function

So when the user keys in a unique reference we want to lookup information from Records Manager.  So where is this going to come from?  Well normally each record you scan is going into a folder and that folder will often carry all the meta data we need to visually check an image.

So our lookup is going to be to Records Manager which means a lookup function using the SDK.

This we can do using the .NET scripting built into Kofax.

What the script does is;

  • Connects to Trim
  • Finds the folder that matches our unique reference
  • Copies the meta from Trim back to Kofax so that the indexing user can see it
  • Ensures that when release the scanned document will be put in the correct folder (by setting the special Kofax field TRIM_Container
  • Ensures that the title is correct on the scanned document by setting the special Kofax field TRIM_Title

Calling the Lookup Function

The lookup function can be called as the post processing event on your unique lookup field.

Fine Tuning

Ok so you get the gist of one way of getting a better, more joined up capture experience for Kofax to Records Manager.

To get this ready for production you will also have to consider;

  • Kofax users moving backwards and forwards through batches and potentially changing values.
  • Setting a default destination container (This stops the manual record creation screen from randomly appearing in older export connector versions).

In Summary

The out of the box Kofax to Records Manager integration provides a good starting point.

With judicious use of scripting and configuration, however, you can make the two products really tightly integrated.

This can really reduce the time taken to scan documents especially with higher volume capture scenarios.






A Few Tips for Working with SPFX Web Parts

Ok so a quick re-cap.

Microsoft are have made to the page and web part model in SharePoint – the new SharePoint Framework.

If you create a modern team site in SharePoint you will be able to create a welcome page that uses this new framework.

Creating a modern page


Adding News

Add the new headlines web part to add a news rollup.  You can add news which will automatically rollup to the news tab on the SharePoint mobile app for following sites.


Adding a Useful Rollup

This can be done using the highlighted content web part.

To make this more intuitive in this example we have created a new content type.  Intranet Subject Page.  This inherits from site page and has been added to site pages library.

Now we can add our web part and configure it to only rollup up our “Subject” pages and ignore news and landing pages.


So this web page will now (ok, when matching content has been added and search crawl has run) show all pages from the entire site collection where the content type is Intranet Subject Site Page.

Making the Modern Page Your Home Page


In Summary

We’ve just scratched the surface of what you can do with modern team sites and SPFX web parts.  The take away from this is very much;

  • Try and get some experience with the new web part model, it will become more widely used as Microsoft release the accompanying publishing page model.
  • The new model works very well in tandem with the accompanying apps – such as the SharePoint App for Mobile.
  • Check out
  • This information is correct as of Q1 2017 (i.e. Microsoft is going to be improving this part of SharePoint this year).