IP Library Granted Patent US 12,339,822
Granted Patent B2
US 12,339,822 · App. 18/455,784 · Granted Jun 24, 2025

Method and system for migrating content between enterprise content management systems

Inventors: Michael T. Mohen (Millington, MD); Christopher Dyde (Haddonfield, NJ)
Assignee: OPEN TEXT CORPORATION
G06F16/22G06F16/00G06F16/214G06F16/258G06Q10/0631
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 12,339,822
App. No.
18/455,784
Granted
Jun 24, 2025
Kind
B2
Abstract

Migrating content between enterprise content management systems is described. A source object identifier is identified for metadata tables for content for a source enterprise content management system, based on a migration job definition. The metadata tables are retrieved from the source enterprise content management system, based on the source object identifier. A target object identifier is identified for a target enterprise content management system, based on the metadata tables and the migration job definition. An object identifier map is created that maps the source object identifier to the target object identifier. The metadata tables are stored to the target enterprise content management system, based on the object identifier map. The content for the source enterprise content management system is retrieved. The content is stored as content for the target enterprise content management system.

Claims (58)

1. A system for migrating between content management systems, the system comprising:

a processor; and

a processor-based application that is executable by the processor to:

in response to receiving, for a migration event, a migration event definition specifying content to be migrated, and a definition of users and roles that are to have access to the content after migration:

execute a procedure call to a source database management system associated with a source content management system to identify a source identifier for a plurality of source metadata tables for the content to be migrated;

retrieve the plurality of source metadata tables from the source content management system using the source identifier;

execute a second procedure call to a target database management system associated with a target content management system to identify a target identifier;

store the plurality of source metadata tables for the content to be migrated as a plurality of target metadata tables of the target content management system based on a mapping of the source identifier to the target identifier;

retrieve the content to be migrated from the source content management system;

store the content for the target content management system; and

define users and roles having access to the content after migration based on the definition of users and roles that are to have access to the content after migration.

2. The system of claim 1 , wherein:

the source identifier is a primary key that uniquely identifies the plurality of source metadata tables for the content to be migrated for the source content management system; and

the target identifier is a primary key for the plurality of target metadata tables.

3. The system of claim 1 , wherein the plurality of source metadata tables includes pointers to documents in the content to be migrated, a single value table, and a repeat value table, wherein the repeat value table specifies multiple keywords for each document in the content to be migrated.

4. The system of claim 1 , wherein:

retrieving the plurality of source metadata tables from the source content management system comprises storing the plurality of metadata tables in a NoSQL non-relational database hosted in a staging environment; and

storing the plurality of source metadata tables to the target content management system comprises retrieving the plurality of source metadata tables from the NoSQL non-relational database hosted in the staging environment.

5. The system of claim 1 , wherein the source content management system is coupled to the target content management system over a network, and wherein the target content management system is hosted on a distributed computing environment.

6. The system of claim 1 , wherein the source content management system is coupled to the target content management system over a network, and the source content management system is hosted on a distributed computing environment.

7. The system of claim 1 , further comprising a migration appliance coupled to the source enterprise content management system and target content management system by a network, wherein the migration appliance comprises the processor and processor-based application.

8. A computer-implemented method for migrating content between content management systems, the method comprising:

in response to receiving, for a migration event, a migration event definition specifying content to be migrated, and a definition of users and roles that are to have access to the content after migration:

executing a procedure call to a source database management system associated with a source content management system to identify a source identifier for a plurality of source metadata tables for the content to be migrated;

retrieving the plurality of source metadata tables from the source content management system using the source identifier;

executing a second procedure call to a target database management system associated with a target content management system to identify a target identifier;

storing the plurality of source metadata tables for the content to be migrated as a plurality of target metadata tables of the target content management system based on a mapping of the source identifier to the target identifier;

retrieving the content to be migrated from the source content management system;

storing the content for the target content management system; and

defining users and roles having access to the content after migration based on the definition of users and roles that are to have access to the content after migration.

9. The method of claim 8 , wherein:

the source identifier is a primary key that uniquely identifies the plurality of source metadata tables for the content to be migrated for the source content management system; and

the target identifier is a primary key for the plurality of target metadata tables.

10. The method of claim 8 , wherein the plurality of source metadata tables includes pointers to documents in the content to be migrated, a single value table, and a repeat value table, wherein the repeat value table specifies multiple keywords for each document in the content to be migrated.

11. The method of claim 8 , wherein:

retrieving the plurality of source metadata tables from the source content management system comprises storing the plurality of source metadata tables in a NoSQL non-relational database hosted in a staging environment; and

storing the plurality of source metadata tables to the target content management system comprises retrieving the plurality of source metadata tables from the NoSQL non-relational database hosted in the staging environment.

12. The method of claim 8 , wherein the source content management system is coupled to the target content management system over a network, and wherein the target content management system is hosted on a distributed computing environment.

13. The method of claim 8 , wherein the source content management system is coupled to the target content management system over a network, and the source content management system is hosted on a distributed computing environment.

14. The method of claim 8 , further comprising coupling a migration appliance to the source content management system and target content management system by a network, wherein the migration appliance is configured to migrate the content from the source content management system to the target content management system.

15. A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein, the computer-readable program code comprising instructions executable to:

in response to receiving, for a migration event, a migration event definition specifying content to be migrated, and a definition of users and roles that are to have access to the content after migration:

execute a procedure call to a source database management system associated with a source content management system to identify a source identifier for a plurality of source metadata tables for the content to be migrated;

retrieve the plurality of source metadata tables from the source content management system using the source identifier;

execute a second procedure call to a target database management system associated with a target content management system to identify a target identifier;

store the plurality of source metadata tables for the content to be migrated as a plurality of target metadata tables of the target content management system based on a mapping of the source identifier to the target identifier;

retrieve the content to be migrated from the source content management system;

store the content for the target content management system; and

define users and roles having access to the content after migration based on the definition of users and roles that are to have access to the content after migration.

16. The computer program product of claim 15 , wherein:

the source identifier is a primary key that uniquely identifies the plurality of source metadata tables for the content to be migrated for the source content management system; and

the target identifier is a primary key for the plurality of target metadata tables.

17. The computer program product of claim 15 , wherein the plurality of source metadata tables includes pointers to documents in the content to be migrated, a single value table, and a repeat value table, wherein the repeat value table specifies multiple keywords for each document in the content to be migrated.

18. The computer program product of claim 15 , wherein:

retrieving the plurality of source metadata tables from the source content management system comprises storing the plurality of source metadata tables in a NoSQL non-relational database hosted in a staging environment; and

storing the plurality of source metadata tables to the target content management system comprises retrieving the plurality of source metadata tables from the NoSQL non-relational database hosted in the staging environment.

19. The computer program product of claim 15 , wherein the source content management system is coupled to the target content management system over a network, and wherein the target content management system is hosted on a distributed computing environment.

20. The computer program product of claim 15 , wherein the source identifier identifies the plurality of source metadata tables for the content to be migrated.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 8, 2023
From: MOHEN, MICHAEL T.; DYDE, CHRISTOPHER
To: EMC CORPORATION
Reel/Frame 064841/0959 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 8, 2023
From: EMC CORPORATION
To: OPEN TEXT CORPORATION
Reel/Frame 064850/0606 →
Continuity (5)
Continuation 17468393 · Sep 7, 2021
Continuation 16284715 · Feb 25, 2019
Continuation 13910342 · Jun 5, 2013
Provisional Application 61782238 · Mar 14, 2013
Related Publication 20230401187A1 · Dec 14, 2023
References Cited (15)
US D751599S · Connolly · 2016 [cited by applicant]
US D765674S · Kim · 2016 [cited by applicant]
US 9448692B1 · Mierau · 2016 [cited by applicant]
US D775633S · Wu · 2017 [cited by applicant]
US D817998S · Lee · 2018 [cited by applicant]
US 11762823B2 · Mohen · 2023 [cited by applicant]
US 20050216568A1 · Walkush · 2005 [cited by applicant]
US 20060112247A1 · Ramany · 2006 [cited by examiner]
US 20070168060A1 · Nixon · 2007 [cited by applicant]
US 20120030247A1 · Yambal · 2012 [cited by examiner]
US 20130173546A1 · Cline · 2013 [cited by applicant]
US 20150370444A1 · Jitkoff · 2015 [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office in U.S. Appl. No. 18/448,564, mailed Aug. 23, 2024, 6 pages. [cited by applicant]
Notice of Allowance issued by the U.S. Patent and Trademark Office in U.S. Appl. No. 18/448,564, mailed Apr. 14, 2025, 8 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office in U.S. Appl. No. 18/165,592, mailed Feb. 6, 2025, 19 pages. [cited by applicant]
Cited By (1)
US 12,393,561