Vital ECM MHT

This article describes the step-by-step process for migrating a cloud customer from an on-premise environment to Epicor AWS. Follow the steps below carefully to ensure a smooth transition.

1. Pre-Migration Verification

1. Order Confirmation

   • Confirm the order has been received in EpicCare and that the customer has a valid EpicCare account.

2. Create Admin User

   • DocStar cloud requires a unique admin for each instance.

   • Naming convention: admin@customerEmailSuffix.com

3. Database Backups

   • Back up all databases (e.g., AAAA0001.bak, AstriaHost.bak) before initiating the migration.

2. Document Management and Queries

• Account Validation:

  • Run a SQL script to ensure no documents are assigned to admin@docstar.com. If found, reassign appropriately. 

• DocPath Data:

  • Run the following query to identify all active and past DocPaths that the system used and take a screenshot:

USE AAAA0001;

SELECT * FROM ( 
    SELECT DISTINCT SUBSTRING ([Path], 0, (PATINDEX('%0001%', [Path]) + 4)) AS s 
    FROM Document) d
CROSS APPLY (
    SELECT COUNT(*) AS c 
    FROM Document 
    WHERE [Path] LIKE s + '%') c

ORDER BY s;

• Screenshot Documentation:
  Capture screenshots of:

  • The query results.
    • 
  • Folder properties windows for all relevant DocPaths and database folders.
    These screenshots will be used by Docstar to verify folder sizes, names, and file counts.
    • 

3. Create an EpicCare Ticket

1. Submit via: EpicCare Portal

2. Assign to: ECM-Cloud Services

3. Include:

   • Query results and screenshots.

   • Request for SFTP credentials.

4. Credential Receipt:
   Once the case is validated, you will receive SFTP credentials to transfer files to the Docstar AWS environment.

4. Initiating and Completing the File Transfer

• Transfer Notification:

  • Notify CloudOps via your EpicCare ticket when the file transfer has started.
  • Once the transfer is complete, update the ticket with the customer's requested go-live date.
    Note: Early Monday morning cutovers are possible if enough advance notice is provided (the India cloud team is available on Sundays).

• Data Verification:
  CloudOps will:

  • Confirm the total size and file counts received.
  • Validate the total file counts that have been moved into production.
  • Update the ticket once all data has been fully restored and is ready for use.

5. SFTP File Transfer Using FileZilla

Follow these instructions to transfer files using the SFTP client, FileZilla:

Installation and Setup

• Download and Install FileZilla:
  Download FileZilla Client from HERE and install the appropriate version.

  • 

Configuration Using Site Manager

1. Open Site Manager:

   • Click on File in the top menu and select Site Manager.

   • 

2. New Site Configuration:

   • Click New Site and enter the following details:
     • Protocol: SFTP – SSH File Transfer Protocol
     • Host: dataexchange.docstar.com
     • Port: 22
     • Logon Type: Key File
     • User: (Username provided via a separate email)
     • Key File: (Select the private key file provided via a separate email)
   • 

3. Connect and Transfer Files:

   • Once connected, you will see the FTP site contents.
     • 
   • To download files or directories, drag them from the remote pane to the local pane, or right-click and select the download option.
     • Backup Files
       • AAAA0001.bak
       • AstriaHost.bak
     • DocPath
       • AAAA0001 Folder Contents
       • Entity Exchange
     • 

Optimizing Transfers

1. Simultaneous Transfers:
   By default, FileZilla performs 2 simultaneous downloads. To speed up the transfer:
   • Go to Edit > Settings.
     • 
   • Select Transfers.
   • Change the Maximum simultaneous transfers from 2 to 10.
     • 
   • Click OK to apply the changes.
     • 

6. Final Cutover

• Perform Delta
  • Take note of the timeframe that you began the initial file transfer
    •  (You will use this date in the MAXAGE variable)
  • Once you have received word from the Cloud team that the initial setup and restore is compete, you will perform a robocopy using the CMD command below 
    • Note that you will need to change the source to the original AAAA0001 DocPath and the destination to a new folder called "Delta"

robocopy C:\source c:\destination *.* /S /R:1 /W:1 /MT:30 /MAXAGE:20240315

7. Additional Notes

• Private Key File:
  Each customer transition will be provided with a unique private key file by the Docstar cloud team. This key is required for the SFTP connection in FileZilla.

• Multi-Tenant Support:
  Docstar does not support multi-tenant accounts in their cloud environments. Each customer must have an individual account for support access and must log in through Dashlane.

Troubleshooting Table

By following these detailed steps, you will ensure a successful migration of a cloud customer from an On-Premise environment to Epicor AWS Cloud. If you encounter any issues during the process, please consult the troubleshooting section or reach out to the support team lead for further assistance.