Data migration

• US 7,831,568 B2
• Filed: 08/29/2006
• Issued: 11/09/2010
• 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
• Primary Examiner(s): LEROUX, ETIENNE PIERRE
• Application Number:
  US11/512,520
• Publication Number:
  US 20080126375A1
• Time in Patent Office: 1,533 Days
• Field of Search: 707/3, 707/5, 707/203, 707/674, 709/204
• US Class Current: 707/674
• 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 matter 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 processor;

a data storage device;

a customer profiling application stored on the data storage device and executable by the processor, wherein the customer profiling application when executed by the processor;

with regard to a target application to be deployed;

receives scoping information for configuration of the target application to be deployed in response to scoping questions presented via a user interface; and

generates and stores a configuration for the target application to be deployed within a configuration workspace stored on the data storage device;

with regard to legacy applications;

asks questions through a user interface regarding legacy applications in use;

receives answers to the questions through the user interface; and

stores, on the data storage device, the received answers as customer information including information detailing customer data from legacy applications; and

a data migration planning process stored on the data storage device and executable by the processor, wherein the data migration planning process when executed by the processor;

determines a plan to migrate the customer data from the legacy applications to the target application as a function of the configuration of the target application to be deployed stored in the configuration workspace and the stored customer information detailing the customer data from the legacy applications; and

stores the plan to migrate the customer data from the legacy applications to the target application in the configuration workspace stored on the data storage device.

2. The system of claim 1, wherein the data migration planning process identifies customer data source information including at least one of:

data source type;

data source connectivity information;

locations of data items within the data source;

data item types; and

data item descriptive information.

3. The system of claim 1, wherein the data migration process identifies data sources within at least one customer legacy application and at least one target application data destination for the customer data.

4. The system of claim 1, wherein the data migration process provides a recommendation of at least one data migration tool to migrate data from the customer legacy applications to the target application.

5. The system of claim 4, wherein the at least one data migration tool includes at least one legacy application plugin.

6. The system of claim 4, 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.

7. A method comprising:

receiving scoping information for configuration of a target application to be deployed in response to scoping questions presented via a user interface;

generating and storing, on a data storage device, a configuration for the target application to be deployed within a configuration workspace;

receiving and storing, on the data storage device, customer information including information detailing customer data from legacy applications, the customer information received in response to data migration planning question and received through a user interface, the received customer information identifying at least one customer data migration preference;

determining a plan to migrate the customer data from the legacy applications to the target application as a function of the received customer information and the configuration for the target application to be deployed; and

storing, on the data storage device, the plan to migrate the customer data from the legacy applications to the target application to be deployed.

8. The method of claim 7, wherein the data migration planning question answers identify customer data source information including at least one of:

data source type;

data source connectivity information;

locations of data items within the data source;

data item types; and

data item descriptive information.

9. The method of claim 7, wherein the customer information provides information to identify data sources within at least one customer legacy application and at least one target application data destination for the customer data.

10. The method of claim 7, further comprising:

providing a recommendation of at least one data migration tool 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.

11. The method of claim 10, wherein the at least one data migration tool includes at least one legacy application plugin.

12. The method of claim 10, 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.

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

receive scoping information for configuration of a target application to be deployed in response to scoping questions presented via a user interface;

generate and store a configuration for the target application to be deployed within a configuration workspace;

receive and store customer information including information detailing customer data from legacy applications, the customer information received in response to data migration planning question and received through a user interface, the received customer information identifying at least one customer data migration preference;

determine a plan to migrate the customer data from the legacy applications to the target application as a function of the received customer information and the configuration for the target application to be deployed; and

store the plan to migrate the customer data from the legacy applications to the target application to be deployed.

14. The machine-readable storage medium of claim 13, wherein the customer information provides information to identify data sources within at least one customer legacy application and at least one target application data destination for the customer data.

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

provide a recommendation of at least one data migration tool 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.

16. The machine-readable storage medium of claim 15, wherein the at least one data migration tool includes at least one legacy application plugin.

17. The machine-readable storage medium of claim 15, 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.