Backup (Pull) Connectors: Development and Enhancement Requests

Backup (Pull) Connectors: Development and Enhancement Requests

A backup/pull connector allows Universal Migrator to connect to source systems and backup/extract the data out.

Backup Connector Requirements

Whether you are requesting a brand new backup connector or enhancements to an existing one, the following requirements must be met.

For Browser-Based Systems

For internet applications that are accessed through a web browser (apps like Clio or NetDocuments) you must provide the following:
  1. An administrator login into the web based system
  2. Two-factor authentication must either be disabled or linked to the developer implementing the pull connector
  3. If the source system prohibits credential sharing, the login must be exclusively used by the developer implementing the pull connector.

For "On-Premise" Applications

For applications that run on a regular desktop computer, the following must be provided:
  1. Unprohibited Read-Only access to the live SQL-Server database
    1. The user account must be able to:
      1. Query the SQL database
      2. Run SQL Server Profiler against the database
      3. Create backups of the SQL database
  2. Unprohibited Read-Only access to the live file server
    1. The user account must be able to:
      1. Read any file on the system
      2. View all network connections and file shares 
  3. An admin login into the application
    1. Two-factor authentication must either be disabled or linked to the developer implementing the pull connector
    2. The user account must be able to:
      1. View all data through the desktop application.
      2. Create and edit test/dummy contacts/matters/notes/tasks/documents/etc.
Generally speaking, a copy of the SQL Server database will be transferred to the lab of the developer implementing the pull connector.
Firms who do not want data transferred off-premise must provide a migration workstation that can access the live SQL Server database and the live file server.  Data will be copied from production to the migration workstation instead of to the developer's lab.

For All System Types

In the course of mapping a new system, questions may arise about how fields are used or what they mean.  You must provide a point of contact who can meet upon request to answer questions regarding the source system.

How Backup Connectors Get Built / Enhanced

During the process, the developer will match screens in the application to data in the database and create a data mapping.  These mappings will be reviewed on test data that the developer will create and then verified against other contacts/matters/data in the system.
Once the mapping is complete, a Universal Backup of the data will be created and provided to you.  You will verify that all field mappings are correct and the backup captures all relevant data points.

How long does the process take?

Every system is different but:
  1. Most enhancements are delivered within 24 hours
  2. Most buildouts are complete within 7-14 calendar days

    • Related Articles

    • Feature & Enhancement Requests

      Help Us Help You If a feature doesn't exist, it is because you haven't asked for it yet! The Universal Migrator is always being expanded and enhanced. When we add new features and new platforms, it is because people like you requested it and we feel ...

    • Create a POSTGRES Backup

      This article assumes that you know your Postgres credentials and PgAdmin is Installed. Connect into PgAdmin. Right-Click on the database and click Backup Click on the folder icon to choose a location for your backup When you reach the location to ...

    • Restore a POSTGRES Backup

      Once someone sends you a backup created by following these instructions, you can restore it by following the steps below. Navigate to the location your TAR file is saved at. Extract the TAR File A TAR file is similar to a ZIP file. Using 7Zip, open ...

    • Create a MSSQL BAK Backup

      To create a BAK backup, do the following steps: 1. Shrink the Database (Optional) Open Management Studio and connect to the database server. Change the Recovery Model to Simple: 1. Right click on the database you wish to backup and select Properties. ...

    • Create a MSSQL BACPAC Backup

      To create a BACPAC backup, do the following steps: Open Management Studio and connect to the database server. Right click on the database you wish to backup and select Tasks > Export Data-tier Application... In the dialog that appears click "Next >" ...