Data migration

• US 20080126375A1
• Filed: 08/29/2006
• Published: 05/29/2008
• Est. Priority Date: 08/29/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Viehmann, Robert, Sattler, Juergen, Gaffga, Joachim, Markert, Frank, Wolf, Werner
• Granted Patent: US 7,831,568 B2
• Time in Patent Office: Days
• US Class Current: 707/101
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

The present subject mater relates to configuring computer systems and, more particularly, to data migration. Various embodiments of the present subject matter provide systems, methods, and software to receive and store customer information including information detailing customer data from legacy applications. Some embodiments further determine a plan to migrate the customer data from the legacy applications to a target application as a function of the received customer information and the target application.

Claims

1. A system comprising:

a customer profiling application, wherein the customer profiling application receives and stores customer information including information detailing customer data from legacy applications; and

a data migration planning process, wherein the data migration planning process determines a plan to migrate the customer data from the legacy applications to a target application.

2. The system of claim 1, wherein:

the customer profiling application asks questions and receives answers through a user interface; and

the received answers identify one or more customer data migration preferences.

3. The system of claim 1, wherein the data migration planning process identifies customer data source information including one or more of:

data source type;

data source connectivity information;

locations of data items within the data source;

data item types; and

data item descriptive information.

4. The system of claim 1, wherein the data migration process identifies data sources within one or more customer legacy applications and target application data destinations for the customer data.

5. The system of claim 1, wherein the data migration process provides a recommendation of one or more data migration tools to migrate data from the customer legacy applications to the target application.

6. The system of claim 5, wherein the one or more data migration tools include one or more legacy application plugins.

7. The system of claim 5, wherein:

the plan to migrate the customer data from the legacy application to the target application includes a file format for at least a portion of the customer data; and

identifies a data loading process to load data from a file in the file format to the target application.

8. A method comprising:

receiving and storing customer information including information detailing customer data from legacy applications; and

determining a plan to migrate the customer data from the legacy applications to a target application as a function of the received customer information and the target application.

9. The method of claim 8, further comprising:

asking data migration planning questions and receiving answers through a user interface, wherein the received answers identify one or more customer data migration preferences.

10. The method of claim 8, wherein the data migration planning question answers identify customer data source information including one or more of:

data source type;

data source connectivity information;

locations of data items within the data source;

data item types; and

data item descriptive information.

11. The method of claim 8, wherein the data migration planning question answers provide information to identify data sources within one or more customer legacy applications and target application data destinations for the customer data.

12. The method of claim 8, further comprising:

providing a recommendation of one or more data migration tools to migrate data from the customer legacy applications to the target application, wherein recommended data migration tools are identified as a function of the data migration planning question answers.

13. The method of claim 12, wherein the one or more data migration tools include one or more legacy application plugins.

14. The method of claim 12, wherein:

the plan to migrate the customer data from the legacy application to a target application includes a file format for at least a portion of the customer data; and

identifies a data loading process to load data from a file in the file format to the target application.

15. A machine-readable medium, with encoded instructions, which when executed, cause a machine to:

receive and store customer information including information detailing customer data from legacy applications; and

determine a plan to migrate the customer data from the legacy applications to a target application as a function of the received customer information and the target application.

16. The machine-readable medium of claim 15, wherein the instructions, when further executed, cause the machine to:

ask data migration planning questions and receiving answers through a user interface, wherein the received answers identify one or more customer data migration preferences.

17. The machine-readable medium of claim 15, wherein the data migration planning question answers provide information to identify data sources within one or more customer legacy applications and target application data destinations for the customer data.

18. The machine-readable medium of claim 15, wherein the instructions, when further executed, cause the machine to:

provide a recommendation of one or more data migration tools to migrate data from the customer legacy applications to the target application, wherein recommended data migration tools are identified as a function of the data migration planning question answers.

19. The machine-readable medium of claim 18, wherein the one or more data migration tools include one or more legacy application plugins.

20. The machine-readable medium of claim 18, wherein:

the plan to migrate the customer data from the legacy application to a target application includes a file format for at least a portion of the customer data; and

identifies a data loading process to load data from a file in the file format to the target application.