<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Traceability Archives - Strator</title>
	<atom:link href="http://staging1789117972.strator.com/en/tag/traceability/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Strator</description>
	<lastBuildDate>Tue, 23 Jun 2026 07:37:04 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>http://staging1789117972.strator.com/wp-content/uploads/2026/02/cropped-Strator_logo_star_blueBg-32x32.png</url>
	<title>Traceability Archives - Strator</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Strator&#8217;s Document Migration Methodology: GxP-Ready</title>
		<link>http://staging1789117972.strator.com/en/strators-document-migration-methodology-gxp-ready/</link>
					<comments>http://staging1789117972.strator.com/en/strators-document-migration-methodology-gxp-ready/#respond</comments>
		
		<dc:creator><![CDATA[Jens Coopman]]></dc:creator>
		<pubDate>Mon, 08 Jun 2026 13:06:09 +0000</pubDate>
				<category><![CDATA[Experts & Expertise]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Data migration]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[Traceability]]></category>
		<category><![CDATA[Transformation]]></category>
		<guid isPermaLink="false">http://staging1789117972.strator.com/?p=3238</guid>

					<description><![CDATA[<p>The post <a href="http://staging1789117972.strator.com/en/strators-document-migration-methodology-gxp-ready/">Strator&#8217;s Document Migration Methodology: GxP-Ready</a> appeared first on <a href="http://staging1789117972.strator.com/en/front-page">Strator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section_0 et_pb_section et_section_regular et_flex_section">
<div class="et_pb_row_0 et_pb_row et_flex_row">
<div class="et_pb_column_0 et_pb_column et-last-child et_flex_column et_pb_css_mix_blend_mode_passthrough et_flex_column_24_24 et_flex_column_24_24_tablet et_flex_column_24_24_phone et_flex_column_24_24_widescreen et_flex_column_24_24_ultraWide">
<div class="et_pb_text_0 et_pb_text et_pb_bg_layout_light et_pb_module et_flex_module"><div class="et_pb_text_inner"><p>Document migration is not simply a matter of moving information from one system to another. Migration must also ensure that documents, metadata, and relationships retain their integrity throughout the entire process. </p>
<p>If a migration is not planned and executed systematically, it may result in a loss of documents, loss of metadata, or loss of document integrity, and therefore evidential value. In regulated environments, this may have compliance implications. In other organisations, it may result in the loss of business-critical information or reduced confidence in the reliability of the migrated data. </p>
<p>For these reasons, Strator follows a documented migration methodology designed to ensure quality and control throughout the migration process, thereby preserving the integrity and value of your organisation's information.</p>
</div></div>

<div class="et_pb_image_0 et_pb_image et_pb_module et_flex_module"><span class="et_pb_image_wrap"><img fetchpriority="high" decoding="async" src="http://staging1789117972.strator.com/wp-content/uploads/2026/06/Method-v2-cropped.svg" alt="Strator migration methodology" title="Method v2 cropped" width="1999" height="1119" srcset="http://staging1789117972.strator.com/wp-content/uploads/2026/06/Method-v2-cropped.svg 1999w" sizes="(min-width: 0px) and (max-width: 0px) 0px, (min-width: 1px) 1999px, 100vw" class="wp-image-3245" /></span></div>
</div>
</div>

<div class="et_pb_row_1 et_pb_row et_flex_row">
<div class="et_pb_column_1 et_pb_column et-last-child et_flex_column et_pb_css_mix_blend_mode_passthrough et_flex_column_24_24 et_flex_column_24_24_tablet et_flex_column_24_24_phone et_flex_column_24_24_widescreen et_flex_column_24_24_ultraWide">
<div class="et_pb_text_1 et_pb_text et_pb_bg_layout_light et_pb_module et_flex_module"><div class="et_pb_text_inner"><p><span data-contrast="auto">Our methodology is based on the principles of ISO 13028 and has been further developed through experience gained from a large number of migration projects. In addition, it has been extended to support GxP-regulated environments, where specific requirements apply to documentation, traceability, and documented control.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559740&quot;:360}"> </span></p>
</div></div>

<div class="et_pb_heading_0 et_pb_heading et_pb_module et_flex_module preset--group--divi-heading--divi-text--default"><div class="et_pb_heading_container"><h1 class="et_pb_module_header">GxP-Regulated Environments </h1></div></div>

<div class="et_pb_text_2 et_pb_text et_pb_bg_layout_light et_pb_module et_flex_module"><div class="et_pb_text_inner"><p><span data-contrast="auto">For organisations operating under GxP regulations, the migration methodology can be applied in two ways — under our QMS or under yours.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559740&quot;:360}"> </span></p>
<p><span data-contrast="auto">The migration can be performed under Strator's Quality Management System. In this case, the methodology's process model, templates and documentation are used as the governing framework for the project, adapted to the risk profile of the specific migration. Strator is responsible for the complete migration documentation and reporting.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559740&quot;:360}"> </span></p>
<p><span data-contrast="auto">Alternatively, the migration may be carried out under the customer's instructions and Quality Management System. In this case, the relevant elements of the methodology, templates and best practices are used to support the customer's existing procedures and documentation requirements, thereby enabling the project to benefit from both proven artefacts and experience gained through previous migration projects – all within the framework of the customer's own QMS.</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559740&quot;:360}"> </span></p>
</div></div>

<div class="et_pb_heading_1 et_pb_heading et_pb_module et_flex_module preset--group--divi-heading--divi-text--default"><div class="et_pb_heading_container"><h1 class="et_pb_module_header">Non-Regulated Environments</h1></div></div>

<div class="et_pb_text_3 et_pb_text et_pb_bg_layout_light et_pb_module et_flex_module"><div class="et_pb_text_inner"><p>Many organisations do not require the level of documentation typically associated with GxP-regulated environments.</p>
<p>In these cases, Strator applies the same process and the same fundamental principles of quality and control from the methodology, while adapting the scope of documentation, testing and controls to the specific risks and business requirements of the project. </p>
<p>This allows the organisation to benefit from working methods and quality principles developed for regulated environments without having to perform activities or produce documentation that do not add value in the specific context. </p>
<p>The result is a migration process focused on what matters most: ensuring that documents and associated metadata are transferred correctly, and that the quality of the outcome can be demonstrated to a degree that matches the organisation's requirements and risk profile. </p>
</div></div>
</div>
</div>
</div>

<div class="et_pb_section_1 et_pb_section et_section_regular et_flex_section">
<div class="et_pb_row_2 et_pb_row et_flex_row">
<div class="et_pb_column_2 et_pb_column et-last-child et_flex_column et_pb_css_mix_blend_mode_passthrough et_flex_column_24_24 et_flex_column_24_24_tablet et_flex_column_24_24_phone et_flex_column_24_24_widescreen et_flex_column_24_24_ultraWide">
<div class="et_pb_heading_2 et_pb_heading et_pb_module et_flex_module preset--group--divi-heading--divi-text--default"><div class="et_pb_heading_container"><h1 class="et_pb_module_header">Consider Strator for your next migration project</h1></div></div>

<div class="et_pb_module et_pb_button_module_wrapper et_pb_button_0_wrapper preset--group--divi-button--divi-text--default_wrapper"><a class="et_pb_button_0 et_pb_button et_pb_bg_layout_dark et_pb_module et_flex_module preset--group--divi-button--divi-text--default" href="https://bookings.cloud.microsoft/bookwithme/user/81a72dcce3f14052bdb841a0b4e4ab73%40strator.com?anonymous&#038;ismsaljsauthenabled=true" target="_blank">Contact us</a></div>
</div>
</div>
</div><p>The post <a href="http://staging1789117972.strator.com/en/strators-document-migration-methodology-gxp-ready/">Strator&#8217;s Document Migration Methodology: GxP-Ready</a> appeared first on <a href="http://staging1789117972.strator.com/en/front-page">Strator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>http://staging1789117972.strator.com/en/strators-document-migration-methodology-gxp-ready/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Strator&#8217;s Expertise in SMART Migration</title>
		<link>http://staging1789117972.strator.com/en/strators-expertise-in-smart-migration/</link>
					<comments>http://staging1789117972.strator.com/en/strators-expertise-in-smart-migration/#respond</comments>
		
		<dc:creator><![CDATA[Jens Coopman]]></dc:creator>
		<pubDate>Thu, 04 Jun 2026 11:18:09 +0000</pubDate>
				<category><![CDATA[Cases]]></category>
		<category><![CDATA[Experts & Expertise]]></category>
		<category><![CDATA[Data migration]]></category>
		<category><![CDATA[data storage cost]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[reduction]]></category>
		<category><![CDATA[SMART Migration]]></category>
		<category><![CDATA[Traceability]]></category>
		<category><![CDATA[Transformation]]></category>
		<guid isPermaLink="false">http://staging1789117972.strator.com/?p=3196</guid>

					<description><![CDATA[<p>The post <a href="http://staging1789117972.strator.com/en/strators-expertise-in-smart-migration/">Strator&#8217;s Expertise in SMART Migration</a> appeared first on <a href="http://staging1789117972.strator.com/en/front-page">Strator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section_4 et_pb_section et_section_regular et_flex_section">
<div class="et_pb_row_5 et_pb_row et_flex_row">
<div class="et_pb_column_5 et_pb_column et-last-child et_flex_column et_pb_css_mix_blend_mode_passthrough et_flex_column_24_24 et_flex_column_24_24_tablet et_flex_column_24_24_phone et_flex_column_24_24_widescreen et_flex_column_24_24_ultraWide">
<div class="et_pb_text_7 et_pb_text et_pb_bg_layout_light et_pb_module et_flex_module"><div class="et_pb_text_inner"><p>Being an early adaptor of SMART Migration by Migrate DMS since version 1.0 in 2020 means Strator has a serious head start compared to others in the industry. By actively contributing to the evolution of the platform over the years, we have gained years of hands-on experience and insights with an engine specifically built for things other tools struggle with. That is to say, we truly know the platform inside and out.</p>
<p>&nbsp;</p>
<p>Using this expertise, we assist our clients in different ways. We move vast amounts of data both into and out of SharePoint, and are able to offload and archive very specific data sets inside SharePoint tenants well past 100TB. Because the tool is designed to process data in transit, not just copy it, we can transform formats, remap version history, and route content to calculated destinations while keeping every piece of metadata intact. This way we ensure that our clients can rely on their new digital work environment to be precise, compliant and fully traceable, even at a scale where ordinary tooling would break down.</p>
<p>&nbsp;</p>
<p>Below we would like to share with you some cases to demonstrate the kind of work we do.</p>
</div></div>

<div class="et_pb_divider_1 et_pb_divider_hidden et_pb_space et_pb_divider_position_top et_pb_module"><div class="et_pb_divider_internal"></div></div>

<div class="et_pb_heading_6 et_pb_heading et_pb_module et_flex_module preset--group--divi-heading--divi-text--default"><div class="et_pb_heading_container"><h1 class="et_pb_module_header">Case Highlights</h1></div></div>

<div class="et_pb_text_8 et_pb_text et_pb_bg_layout_light et_pb_module et_flex_module"><div class="et_pb_text_inner"><p><strong>1. 4TB from a legacy ECM into SharePoint, with version history intact</strong></p>
<p><span>A client needed to migrate 4TB of documents out of an aging ECM platform and into SharePoint sites. The hard part: the source had versioned its documents in a non-SharePoint-standard model, so a straight copy would have lost the version lineage entirely. This would completely destroy any traceability for the client’s documents.</span></p>
<p><span></span></p>
<p><span>Using SMART Migration's in-transit transformation together with its version-history transfer, we converted the documents to PDF to ensure long term support and safe archiving. We also remapped the source's non-standard version model into native SharePoint versions on the way in. This way, the full archive landed in SharePoint as PDF with complete version history and metadata preserved, while nothing was left behind in the retired ECM.</span></p>
<p><span></span></p>
<p> </p>
<p><strong>2. Surgical offload across a 100TB SharePoint tenant, cutting storage cost</strong></p>
<p>A client needed to bring down the cost of a SharePoint tenant exceeding 100TB without losing access to any data. The challenge was pinpointing exactly which files should leave SharePoint at that scale. Working with the client, our experts established a clear set of use cases defining precisely which files should be archived or offloaded.</p>
<p> </p>
<p>Using SMART Migration's offload capability, we moved those files to a long-term archive on a 3rd-party platform like Amazon S3, Azure Blob Storage, Nextcloud, and local file share while keeping every file fully restorable on demand. The storage consumed inside SharePoint dropped sharply, reducing the client's SharePoint storage cost drastically, with no data loss and no change to how users access their content. This saved our client both money and hastle.</p>
<p> </p>
<p> </p>
<p><strong>3. Deep fileshare into calculated locations with folder-specific logic</strong></p>
<p>A client's deeply nested legacy fileshare had to be moved into SharePoint while the client was still actively using the system. Because the destination for each item depended on its folder context rather than a simple one-to-one path mapping, this would be an impossible task for most people. We were also asked to clean up the digital workspace and reorganize the filing system during the transfer, so a simple lift-and-shift was out of the question.</p>
<p> </p>
<p>Our solution was to use SMART Migration’s expression-based routing to compute each file’s destination from folder specific rules, landing content in a clean, logically organized structure instead of a flat copy of the old tree. We did this by first defining how we wanted the end product to look, creating a logic within the migration which allowed files to be automatically sorted in the new SharePoint. This is how we managed to pull off this complicated migration according to the exact wishes of our clients, while cleaning up the new workspace and keeping traceability to old file locations intact.</p>
<p> </p>
</div></div>

<div class="et_pb_heading_7 et_pb_heading et_pb_module et_flex_module preset--group--divi-heading--divi-text--default"><div class="et_pb_heading_container"><h1 class="et_pb_module_header">How Can Strator Help You with SMART Migration?</h1></div></div>

<div class="et_pb_text_9 et_pb_text et_pb_bg_layout_light et_pb_module et_flex_module"><div class="et_pb_text_inner"><p>To put it simply, we have extensive experience with SMART Migration. Transformation with retention of traceability and metadata, archiving, reducing costs and storage, and even doing thorough clean-ups and reorganization - these are a few of the ways in which we can help our clients.</p>
<p> </p>
<p>If you believe your systems are due a clean-up, or need to decrease your data costs, feel free to reach out to us. We would love to hop on a call, and explore how we can help you improve your digital workspace through SMART Migration.</p>
</div></div>
</div>
</div>
</div>

<div class="et_pb_section_5 et_pb_section et_section_regular et_flex_section">
<div class="et_pb_row_6 et_pb_row et_flex_row">
<div class="et_pb_column_6 et_pb_column et-last-child et_flex_column et_pb_css_mix_blend_mode_passthrough et_flex_column_24_24 et_flex_column_24_24_tablet et_flex_column_24_24_phone et_flex_column_24_24_widescreen et_flex_column_24_24_ultraWide">
<div class="et_pb_heading_8 et_pb_heading et_pb_module et_flex_module preset--group--divi-heading--divi-text--default"><div class="et_pb_heading_container"><h1 class="et_pb_module_header">Consider Strator for your next migration project</h1></div></div>

<div class="et_pb_module et_pb_button_module_wrapper et_pb_button_2_wrapper preset--group--divi-button--divi-text--default_wrapper"><a class="et_pb_button_2 et_pb_button et_pb_bg_layout_dark et_pb_module et_flex_module preset--group--divi-button--divi-text--default" href="https://bookings.cloud.microsoft/bookwithme/user/81a72dcce3f14052bdb841a0b4e4ab73%40strator.com?anonymous&#038;ismsaljsauthenabled=true" target="_blank">Contact us</a></div>
</div>
</div>
</div><p>The post <a href="http://staging1789117972.strator.com/en/strators-expertise-in-smart-migration/">Strator&#8217;s Expertise in SMART Migration</a> appeared first on <a href="http://staging1789117972.strator.com/en/front-page">Strator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>http://staging1789117972.strator.com/en/strators-expertise-in-smart-migration/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Object Caching 120/141 objects using Disk
Page Caching using Disk: Enhanced 

Served from: staging1789117972.strator.com @ 2026-09-11 09:46:16 by W3 Total Cache
-->