Maximo Open Forum

Hello experts, I am new to *Maximo Application Suite on Cloud (SaaS)*. I need to migrate full production data from an on-premise Maximo 7.6.1.3 (Oracle DB, 10+ years in use) to the SaaS environment, with a total volume of *over 50 million records*. Since I have no access to the SaaS DB2 server or operating system, IBM support recommended importing data via S3 using cron tasks, following this guide: https://www.ibm.com/docs/en/masv-and-l/maximo-manage/cd?topic=data-importing-s3-by-using-cron-tasks However, the documentation is very brief. I have completed the configuration as instructed. The cron task runs *without any errors*, but *no new data is created in the system*. I hope to get advice from experts who have real experience with this method: 1. Why does the cron task show no errors but import no data? 2. The guide does not mention *data mapping*. Does the system automatically map CSV columns to the corresponding database fields? 3. After a successful full import, what is the standard way to *validate data completeness* and ensure no records are missing or incorrect? Any help or shared experience would be highly appreciated. Thank you! 

This documentation was written around the assumption you had an existing file integration and were transitioning from one of those legacy cron tasks to the new S3 cron tasks. Since you're trying to do an Oracle to DB2 conversion essentially, you need an external system & various publish channels & enterprise services for all the different components (sets, orgs, sites, GL accounts, domains, custom objects/attributes, locations, assets, job plans, PMs, work orders, custom tables, etc.). Setting everything up to be able to be imported would be extremely time intensive.

And imports of historical data into Maximo is extremely complicated, especially for tables like work orders. In addition to all the dependencies you must import prior to importing work orders, there are a series of business rules that have to be met to do various pieces. In order to record the plans (materials, labor, tools, etc.), you need to be in a WAPPR status typically. And then to record the actuals you need to be in an APPR to COMP status and then you need to close the transactions out. To import one work order for example, you may find you need 3 or 4 imports just for the work order. And then you have to worry about dates since not all of them can be backdated in the import. 

I would look to a business partner that can do this work for you to convert your existing database from Oracle to DB2. You'll save a lot of time and frustration trying to get it converted. And then you can hand the DB2 backup to IBM to import into your SaaS instance.