IP Library Granted Patent US 10,733,207
Granted Patent B2
US 10,733,207 · App. 16/252,227 · Granted Aug 4, 2020

Automated staged data migration

Inventors: Evan Richman (Seattle, WA); Todd Schwartz (Seattle, WA); Trent Robert Schwartz (Seattle, WA); Bradley Younge (Denver, CO); John Dennis (Oakland, CA); Roger Neil Moore (Seattle, WA); Christopher Rayner (Seattle, WA)
Assignee: SKYKICK, INC.
G06F16/27G06F16/214H04L51/04H04L51/22H04L67/306H04L67/325H04L67/34H04L61/1511
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,733,207
App. No.
16/252,227
Granted
Aug 4, 2020
Kind
B2
Abstract

Systems, methods, and apparatuses can provide staged migration from one or more user accounts from a source system to a destination system using an application local to the source systems. The automated staged data migration can provide coordinated staged data migration of large amounts of data in a single automated process. The system can provide automated and remotely controlled staged migrations of data that may perform source system type detection and work with multiple types of systems.

Claims (56)

1. A method of migrating data from a plurality of user accounts from a source system to a destination system, the method comprising:

receiving, at a migration assistant, instructions to migrate the plurality of user accounts in stages including a first stage, wherein the first stage is completed by a first end time, wherein the migration assistant is separate and distinct from the destination system;

receiving, by the migration assistant, a completion signal from a migration engine at the first end time, the completion signal indicating that the plurality of user accounts have been migrated, wherein the migration engine is separate and distinct from the migration assistant;

after the completion signal:

receiving, by the migration assistant, forwarding commands for forwarding future data for the plurality of user accounts to the destination system, the future data being received after the plurality of user accounts have been migrated to the destination system; and

generating, by the migration assistant, reconfigure commands for execution by a first set of client computers, the first set of client computers being associated with the plurality of the user accounts, and the reconfigure commands being configured to cause the first set of client computers to be automatically connected to the destination system.

2. The method of claim 1 , wherein the reconfigure commands instruct the migration assistant to point change one or more settings of one or more client application to point to the destination system.

3. The method of claim 1 , further comprising:

during the first stage:

identifying, by the migration engine, new data that is added to the source system for the first set of one or more user accounts, and

replicating, by the migration engine, the new data to the destination system using the migration controller server.

4. The method of claim 3 , wherein identifying new data is performed at a plurality of times.

5. The method of claim 4 , wherein the plurality of times include the first end time.

6. The method of claim 1 , further comprising:

in response to the completion signal:

sending, by the migration controller server to the migration assistant, a command to disassociate each of the plurality of user accounts from the source system.

7. The method of claim 1 , wherein the first set of one or more user accounts are email accounts, the method further comprising:

in response to the completion signal:

sending, by the migration controller server to the migration assistant, one or more commands to convert the first set of one or more user accounts to mail-enabled user accounts.

8. The method of claim 7 , further comprising:

sending, by the migration controller server to the source system, one or more additional commands to:

apply an external address to the mail-enabled user account; and

reassign user aliases of a user account to the respective mail-enabled user account.

9. The method of claim 1 , further comprising:

querying, by the migration controller server, the source system to obtain information to identify changes necessary for a migration project; and

sending, by the migration controller server, commands to the source system to implement the changes.

10. The method of claim 1 , wherein replicating the data from the source system to the destination system includes:

sending commands from the migration controller server to a migration assistant executing on a local device within a local network that includes the source system.

11. The method of claim 1 , wherein the plurality of user accounts are a first set of user account, the plurality of the stages include a second stage completed by a second end time, and the method further comprises performing, by the migration controller server:

during the second stage, identifying new data that is added to the source system and replicating the new data to the destination system;

at the second end time, generating, by the migration assistant, a forwarding rule to forward future data for a second set of user accounts to the destination system; and

sending, by the migration assistant, commands to a second set of client computers associated with the second set of user accounts to reconfigure the second set of client computers to connect to the destination system.

12. A non-transitory computer readable medium storing a code for controlling a migration controller server to perform an operation for migrating data from a plurality of user accounts from a source system to a destination system, the code comprising:

receiving, at a migration assistant, instructions to migrate the plurality of user accounts in stages including a first stage, wherein the first stage is completed by a first end time, wherein the migration assistant is separate and distinct from the destination system;

receiving, by the migration assistant, a completion signal from a migration engine at the first end time, the completion signal indicating that the plurality of user accounts have been migrated, wherein the migration engine is separate and distinct from the migration assistant;

after the completion signal:

receiving, by the migration assistant, forwarding commands for forwarding future data for the plurality of user accounts to the destination system, the future data being received after the plurality of user accounts have been migrated to the destination system; and

generating, by the migration assistant, reconfigure commands for execution by a first set of client computers, the first set of client computers being associated with the plurality of the user accounts, and the reconfigure commands being configured to cause the first set of client computers to be automatically connected to the destination system.

13. The non-transitory computer readable medium of claim 12 , wherein the reconfigure commands cause the first set of client computers to change one or more settings of one or more client applications to point to the destination system.

14. The non-transitory computer readable medium product of claim 13 , wherein the code further comprises:

between the first start time and the first end time:

identifying new data that is added to the source system for the first set of one or more user accounts, and

replicating the new data to the destination system using the migration controller server.

15. The non-transitory computer readable medium of claim 14 , wherein the first set of one or more user accounts are email accounts, and wherein the code further comprises:

in response to the completion signal:

sending one or more commands to convert the first set of one or more user accounts to mail-enabled user accounts.

16. The non-transitory computer readable medium of claim 15 , wherein the code further comprises:

sending one or more additional commands to:

applying an external address to a mail-enabled user account; and

reassign user aliases of a user account to the respective mail-enabled user account.

17. The non-transitory computer readable medium of claim 13 , wherein replicating the data from the source system to the destination system includes:

sending commands from the migration controller server to a migration assistant executing on a local device within a local network that includes the source system.

18. The non-transitory computer readable medium of claim 13 , wherein the plurality of user accounts are a first set of user account, the plurality of the stages include a second stage completed by a second end time, wherein the code further comprises:

during the second stage, identifying new data that is added to the source system and replicating the new data to the destination system;

at the second end time, generating a forwarding rule to forward future data for a second set of user accounts to the destination system; and

sending commands to a second set of client computers associated with the second set of user accounts to reconfigure the second set of client computers to connect to the destination system.

Assignments (8)
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 →
RELEASE OF SECURITY INTEREST Recorded Sep 2, 2021
From: SKYKICK, INC.
To: AVENUE VENTURE OPPORTUNITIES FUND, LP
Reel/Frame 057374/0965 →
SECURITY INTEREST Recorded Sep 2, 2021
From: SKYKICK, LLC
To: MS PRIVATE CREDIT ADMINISTRATIVE SERVICES, LLC
Reel/Frame 057372/0544 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 25, 2019
From: RICHMAN, EVAN; SCHWARTZ, TODD; SCHWARTZ, TRENT ROBERT; YOUNGE, BRADLEY; DENNIS, JOHN; MOORE, ROGER NEIL; RAYNER, CHRISTOPHER
To: SKYKICK, INC.
Reel/Frame 048137/0577 →
Continuity (3)
Continuation 14873060 · Oct 1, 2015
Provisional Application 62058608 · Oct 1, 2014
Related Publication 20190155818A1 · May 23, 2019