APPLICATION MIGRATION FACTORY processes Lotus Notes applications and their data according to the following 3 strategies:
Application data is extracted from Notes databases and kept in an open format (XML, HTML ...), for long-term preservation or for future migration.
Migration & Conversion
The application data is extracted from the Notes databases and injected into a third-party application (SharePoint, OneDrive, Google Drive, market solutions ...). A conversion to PDF is proposed.
The Notes application is rewritten (new development) in a third-party technology (SharePoint, .Net, JEE) and the Notes data is extracted and imported.
The same Notes application can be both Archived, Migrated and Transformed: the non-active data is extracted from the application to be archived while the active data is imported into the new application.
APPLICATION MIGRATION FACTORY is configured specifically with one or more migration lines to handle the policies chosen by the client.
Each Migration line is characterized by the type of source and the target chosen.
Type of source and target chosen for the migration lines
TO ENGAGE THE ARCHIVING, MIGRATION OR TRANSFORMATION STRATEGIES, APPLICATION MIGRATION FACTORY WORKS AROUND THE FOLLOWING 4 COMPONENTS:
Collect information from Notes databases hosted on Domino servers or stored locally on user workstations.
Regroups all the characteristics of a Notes database (template, volume, user activity, code, security, complexity, access, etc.).
Audit Server & Apps Station
Audit User Desktop Station
Retrieval, onto a server, of databases hosted locally on users' PCs.
Analyze & Segmentation Station
Allows for the first treatments to be carried out on the data gathered during the Audit phase.
Data is classified into different homogeneous groups.
First Costestimation for standard Notes databases.
Analysis & Segmentation Stage
Provides more in depth information, if necessary related to the Business owners.
Provides Cost estimation for Complex Notes Databases.
Data Ownership Station
Optional: establish a link between all the Notes databases and the Business Units of the company.
Determine which database belongs to which Business Unit for the project cost.
Business Survey Station
Designed to better understand the use of the Notes applications by directly interviewing the people in charge of them.
Cost Estimation Station
Provides for complex databases a list of compatible technology platforms (SharePoint, J2E, etc...) and associated migration costs (estimation).
Phase 2 : Decision
Powered by the detailed results of the Analysis phase, the Business Departments decide on the migration process of their applications.
Business Decision Station
The Business Decision workshop is the key moment in the migration project. The Businesses decide, based on the deliverables provided during the Analysis, the strategy to choose for each application (Archive, Migrate, Transform) and the chosen target platform. Budgets, Planning, Resources are validated, the migration can begin and the Factory is activated.
Go - No Go Stage
Implementation of a factory PrepareRunDecom
Phase 3 : Prepare
Factory Setup Stage
This step prepares, configures and activates the Factory. Two options: SAAS Mode or ON PREM Mode, depending on the project and its volume.
Data Preparation Stage
This step ensures the availability and compliance of migrated applications and their data.
Local Data Upload Station
Optional during the Compliance step.
If there is data to be retrieved from the users' desktops (base local archives), we must (before processing them) copy them to a centralized server.
If the database is encrypted, we must use the user's Notes ID to decrypt it before copying it to the server.
Data Access Station
Mandatory during this compliance phase. Just before exporting the data from the Notes database (Mail or Application), we need to make sure that there are no encrypted documents in the database.
If this is the case, we must identify the users carrying the decryption key and initiate the decryption job.
If the user has left the company and his ID is unavailable, encrypted data is lost.
Builds the name repository between the current system represented by the Domino Directory (Names.nsf) and the target system, usually represented by the Active Directory.
Phase 4 : Run
Extract data from Notes databases as open format data files (XML, HTML, XSL ...).
Extract content to open format files.
For long-term storage, application in Read-Only or export to other platforms.
Ensure that the extracted data is displayed correctly (human action is required).
Choice of a read / write format of a HTML, PDF or Word document.
Configuration of the conversion process according to the chosen formats.
Rebuild the application on the platform that has been chosen. This can result in a simple data import until a complete rewrite of the application.
Import the data from the Notes database. The passage through additional workshops may be necessary.
When customizing the application on the new platform by changing elements of presentation on the information is needed.
Applications that need to be completely rewritten for the target platform.
This station is the last in the provisioning stage and just prior to the delivery.
Quality Control Station
At the end of the development, before delivery.
Make sure that the application meets the specifications and that the specifications have been implemented.
Ensures the delivery process of the application and if necessary, assistance with the installation.
Delivery Support: 3, 6 months.
Scalable, corrective maintenance.
Adjusting the application infrastructure.
Phase 5 : Decom
Decommissioning of old Notes applications (archiving and backup of the legacy applications) and servers (verifying the end of access to the old application, installing a redirect to the new application, etc.).
End of Project
Deactivation of the Factory
Our Application Services Center
RESOURCES AND EXPERTISE COVERING THE FOLLOWING TECHNOLOGIES: MICROSOFT -JAVA & OPEN SOURCE -UI/UX -WEB & MOBILE -EMBEDED