The Seal Platform
WebsiteGet StartedContact Us
The Seal Platform
  • Website
  • Contact Sales
  • Logging in & System Requirements
  • Get Started Here
  • Moving to Seal
    • Migration
    • Implementation
  • Manage
    • Where do I start?
    • Creating Types
      • Documents
      • Work Done
      • Files
        • Extracting Fields with AI
      • Scripts
        • Writing Scripts with the Seal Module
        • Script Action Buttons
      • Charts
      • Converting Between Types
    • Adding Content and Fields
      • Computed Titles
      • Formatting Text
      • Formulas
      • Numbered Lists
      • Setting Assignees
      • Setting Out-of-Specifications
      • Setting Review Requirements
      • Submission Tables
    • Executing Types: Test Instances
    • Work Instructions
    • Change Sets
    • Checks
    • Active Versions
    • Training
    • API
  • Operate
    • Where do I start?
    • Re-executing Instances
    • Reviewing
  • MISC
    • Glossary
    • Inbox
    • Search Page and Saved Views
    • User Permissions and Roles
    • Tags
    • Github Integration
    • Change Management
    • Seal Changelog
  • Video Guides
    • Creating Templates
    • Creating and Reviewing Instances
    • Sending and Completing Trainings
  • Validation
    • Why do I need to validate my platform?
    • What is needed from my end for validation?
    • How is my system validated?
      • Baseline Validation
      • Configuration Validation
      • Compliance Validation
      • What about IQ, OQ, or PQ?
      • Automatic Revalidation
        • Change Controls
      • How do I know if my system is compliant to a standard?
        • Setting up your System
        • Performing Compliance Validation
    • GxP Validation for enterprise customers
    • Can I download a Validation Report?
      • Software Functionality Verification
    • Common Validation FAQs
  • Product Quality
    • Seal's Guarantee of Quality
    • Product Development Lifecycle
    • Platform Operation Tests
    • Incident Procedure
  • IT & Security Policies
    • Seal's Tech Stack
    • Data Storage and Security
    • Cloud Servers vs On-Premises File Servers
    • Data Backup and Disaster Recovery
    • Disaster Recovery Plan
    • Handling Confidential Data
    • Common IT FAQs
  • Regulatory Standards
    • 21 CFR Part 11
    • EU Volume 4 Annex 11
    • ISO 13485 Medical Devices
    • Clinical Laboratory Improvement Amendments (CLIA)
  • Support
    • Contact us
Powered by GitBook

Copyright © Seal 2025. All Rights Reserved.

On this page
  1. Moving to Seal

Migration

Migrating from your paper-based documents or existing software to Seal is simple and straightforward. Our intuitive tools and import features are designed to make the transition smooth, quick, and efficient - ensuring that all your data can be transferred without hassle.

Will I lose functionality of my previous systems?

Maintaining full functionality is our top priority. We take extra care to ensure that all critical features and processes are preserved throughout the transition. By thoroughly understanding your current system, we identify key functionalities that must be maintained, and configure Seal accordingly.

Our post-migration testing and validation processes ensure that the quality, functionality, and integrity of your data is maintained.

The Migration Process

Our dedicated team of deployment strategists will work closely with your team and oversee the entire migration process.

1

Determine Scope and Depth of Migration

Our team begin by thoroughly assessing your current system: understanding the data, applications, and infrastructure involved. This includes identifying what components need to be migrated, and areas which may require additional reconfiguration.

We will work closely with your team to define the migration’s depth, ensuring we cover all functional, technical, and compliance needs.

2

Establish Timelines

Once the scope is clearly defined, we will collaboratively establish realistic timelines for each phase of the migration, based on the migration urgency. Regular checkpoints will be scheduled to monitor progress.

3

Execute Migration

Migration is conducted in a phased and controlled manner to minimise downtime. This will include transferring data, configuring systems, and making relevant data links and workflows.

Throughout this process, we will work closely with your team to mitigate arising issues.

4

QA Checks

Post migration, data integrity checks and post-migration testing is conducted. This ensures that your data remains intact, with full functionality and compatibility. Once completed, Seal is ready for use — with your old data in the system.

Last updated 24 days ago