IP Library Granted Patent US 10,027,738
Granted Patent B2
US 10,027,738 · App. 14/872,984 · Granted Jul 17, 2018

Optimizing data migration processes

Inventors: Evan Richman (Seattle, WA); Todd Schwartz (Seattle, WA); Trent Robert Schwartz (Seattle, WA); Bradley Younge (Denver, CO); Alexander Samuel-Charles Barclay (Tacoma, WA)
Assignee: SKYKICK, INC.
H04L67/06G06F17/30923H04L51/14H04L51/22H04L67/10H04L67/1095H04L63/083H04L63/104
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,027,738
App. No.
14/872,984
Granted
Jul 17, 2018
Kind
B2
Abstract

Systems, methods, and apparatuses can present optimized data migration. Embodiments can provide improved data migration processes using a data migration assistant that executes on a source system to facilitate the migration of documents and data to a destination system. The migration assistant can communicate with a migration controller server to authenticate and identify the migration assistant and migration project that the migration assistant is to be used for. The migration controller server can use the identifier to determine commands corresponding to the migration project to send to the migration assistant to collect data and make changes to the source system.

Claims (56)

1. A method comprising:

executing a migration assistant on a computer of a source system;

establishing, by the migration assistant, a first communication connection between the migration assistant and a migration controller server;

sending, from the migration assistant to the migration controller server using the first communication connection, an identifier that identifies a migration project for migrating documents from the source system to a destination system;

receiving, by the migration assistant, a request from the migration controller server to collect metadata regarding the source system for migrating the documents from the source system to the destination system;

in response to receiving the request from the migration controller server, establishing, by the migration assistant, a second communication connection between the migration assistant and a source document server of the source system;

querying, by the migration assistant using the second communication connection, the source document server to collect the metadata, the metadata corresponding to documents stored on the source document server;

sending, by the migration assistant over the first communication connection, the metadata to the migration controller server;

receiving, by the migration assistant from the migration controller server, one or more commands for the migration project, the one or more commands specifying changes to be made to a configuration of the source system as part of the migration project, wherein the migration controller server generates the one or more commands based on the metadata;

implementing, by the migration assistant, the one or more commands to make the specified changes to the source system; and

sending, by the migration assistant to the migration controller server, a confirmation that the specified changes have been implemented.

2. The method of claim 1 , when the migration assistant sends the identifier in response to installation on the computer of the source system, and wherein the identifier includes a registration code entered at a user interface of the migration assistant.

3. The method of claim 2 , wherein the migration controller server uses the identifier to authenticate the migration assistant and determine the migration project, and the method further comprises:

receiving, by the migration assistant, an authentication response from the migration controller server that the migration assistant has been authenticated.

4. The method of claim 1 , wherein the metadata specifies a number of user accounts in the source document server and identifying information for each user account.

5. The method of claim 1 , further comprising performing, by the migration assistant:

prior to querying the source document server, receiving instructions from the migration controller server, instructions specifying the metadata to collect.

6. The method of claim 5 , wherein the instructions specify that the metadata is to include distribution groups and their membership and security groups and their membership.

7. The method of claim 1 , wherein the source document server is an e-mail server, and wherein the instructions specify to collect rules about an operation of the source document server, and wherein the rules are related to one or more of:

user mailboxes, primary SMTP address for each mailbox, usernames, aliases assigned to mailboxes, permissions for the mailboxes and its folders and subfolders, a list of distribution groups and their aliases, a list of mailboxes that are members of the distribution groups, mailbox permissions, and user information.

8. The method of claim 7 , further comprising performing, by the migration assistant:

storing the rules into a data file; and

sending the data file to the migration controller server via the second communication connection.

9. The method of claim 8 , wherein storing the rules includes:

serializing the rules into the data file, and wherein the data file is an XML file.

10. The method of claim 1 , wherein a plurality of documents to be migrated include emails of a specific mailbox on the source system, wherein the one or more commands include:

a disassociation of the specific mailbox from the source system; and

a forwarding rule for the specific mailbox to forward email to a specified external email address associated with the destination system.

11. The method of claim 10 , wherein the one or more commands further include:

a conversion of the specific mailbox to have a status that the specific mailbox for a specific email address is located at a location outside of its local environment.

12. The method of claim 1 , wherein the one or more commands are for a cutover migration or are for a staged migration.

13. The method of claim 1 , wherein the one or more commands include: collect business rules specifying which users can access which documents of the source document server.

14. The method of claim 1 , wherein the one or more commands include a command to disable communication of a user with the source document server.

15. The method of claim 1 , wherein the one or more commands include a command to reconfigure a plurality of service connection points that store Internet addresses that are provided to devices for connecting to the source document server.

16. A computer product comprising a non-transitory computer readable medium storing a plurality of instructions for controlling a computer system of a source system, the instructions comprising:

executing a migration assistant on the computer system of the source system;

establishing, by the migration assistant, a first communication connection between the migration assistant and a migration controller server;

sending, from the migration assistant to the migration controller server using the first communication connection, an identifier that identifies a migration project for migrating documents from the source system to a destination system;

receiving, by the migration assistant, a request from the migration controller server to collect metadata regarding the source system for migrating the documents from the source system to the destination system;

in response to receiving the request from the migration controller server, establishing a second communication connection between the migration assistant and a source document server of the source system;

querying, by the migration assistant using the second communication connection, the source document server to collect the metadata, the metadata corresponding to documents stored on the source document server;

sending, by the migration assistant over the first communication connection, the metadata to the migration controller server;

receiving, by the migration assistant from the migration controller server, one or more commands for the migration project, the one or more commands specifying changes to be made to a configuration of the source system as part of the migration project, wherein the migration controller server generates the one or more commands based on the metadata;

implementing, by the migration assistant, the one or more commands to make the specified changes to the source system; and

sending, by the migration assistant to the migration controller server, a confirmation that the specified changes have been implemented.

17. The computer product of claim 16 , when the migration assistant sends the identifier in response to installation on the computer system of the source system, and wherein the identifier includes a registration code entered at a user interface of the migration assistant, wherein the migration controller server uses the identifier to authenticate the migration assistant and determine the migration project, wherein the instructions further comprise:

receiving, by the migration assistant, an authentication response from the migration controller server that the migration assistant has been authenticated.

18. The computer product of claim 16 , wherein the instructions further comprise:

prior to querying the source document server, receiving instructions from the migration controller server, the instructions specifying the metadata to collect, wherein the instructions specify that the metadata is to include distribution groups and their membership and security groups and their membership.

19. The computer product of claim 16 , wherein the source document server is an e-mail server, and wherein the instructions specify to collect rules about an operation of the source document server, wherein the instructions further comprise:

storing the rules into a data file; and

sending the data file to the migration controller server via the second communication connection.

20. The computer product of claim 16 , wherein a plurality of documents to be migrated include emails of a specific mailbox on the source system, wherein the one or more commands include:

a disassociation of the specific mailbox from the source system;

a forwarding rule for the specific mailbox to forward email to a specified external email address associated with the destination system and

a conversion of the specific mailbox to have a status that the specific mailbox for a specific email address is located at a location outside of its local environment.

Assignments (11)
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Feb 19, 2025
From: SKYKICK, LLC; EFOLDER, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 070268/0489 →
MERGER Recorded Sep 19, 2024
From: PROJECT JOULE MERGER SUB, INC.
To: SKYKICK GLOBAL HOLDINGS, INC.
Reel/Frame 068636/0471 →
RELEASE OF SECURITY INTEREST Recorded Sep 10, 2024
From: MS PRIVATE CREDIT ADMINISTRATIVE SERVICES, LLC
To: SKYKICK, LLC
Reel/Frame 068545/0172 →
SECURITY INTEREST Recorded Sep 2, 2021
From: SKYKICK, LLC
To: MS PRIVATE CREDIT ADMINISTRATIVE SERVICES, LLC
Reel/Frame 057372/0544 →
RELEASE OF SECURITY INTEREST Recorded Sep 2, 2021
From: SKYKICK, INC.
To: AVENUE VENTURE OPPORTUNITIES FUND, LP
Reel/Frame 057374/0965 →
CHANGE OF NAME Recorded Sep 1, 2021
From: SKYKICK, INC.
To: SKYKICK, LLC
Reel/Frame 057395/0001 →
SECURITY AGREEMENT Recorded Jan 31, 2020
From: SKYKICK, INC.
To: AVENUE VENTURE OPPORTUNITIES FUND, LP
Reel/Frame 051763/0466 →
RELEASE OF SECURITY INTEREST Recorded Jan 30, 2020
From: VENTURE LENDING & LEASING VIII, INC.; VENTURE LENDING & LEASING IX, INC.; VENTURE LENDING & LEASING VII, INC.
To: SKYKICK, INC.
Reel/Frame 051761/0604 →
SECURITY INTEREST Recorded Dec 7, 2018
From: SKYKICK, INC.
To: VENTURE LENDING & LEASING IX, INC.; VENTURE LENDING & LEASING VIII, INC.
Reel/Frame 048918/0322 →
SECURITY INTEREST Recorded Apr 4, 2017
From: SKYKICK, INC.
To: VENTURE LENDING & LEASING VII, INC.; VENTURE LENDING & LEASING VIII, INC.
Reel/Frame 041849/0862 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 17, 2016
From: RICHMAN, EVAN; SCHWARTZ, TODD; SCHWARTZ, TRENT ROBERT; YOUNGE, BRADLEY; BARCLAY, ALEXANDER SAMUEL-CHARLES
To: SKYKICK, INC.
Reel/Frame 040363/0506 →
Continuity (2)
Provisional Application 62058605 · Oct 1, 2014
Related Publication 20160099998A1 · Apr 7, 2016