Maximo Open Forum

 View Only

Related Content

  • 1.  Attachment migration approach: Maximo 7.6.1.3 to MAS SaaS

    Posted 14 days ago
    Hello experts,
    I need to migrate an on-premise Maximo 7.6 to MAS SaaS with full dataset migration, and all attachments need to be accessible post-migration. Could you advise feasible solutions? Can attachments be uploaded into the SaaS environment and what is the procedure?
    After migration via Object Structure, record IDs have changed, leaving me stuck on follow-up work. Would exporting only CSV files and requesting SaaS admins perform identical direct DB import be a viable alternative?

    #Administration

    ------------------------------
    pan yj
    shuto
    ------------------------------


  • 2.  RE: Attachment migration approach: Maximo 7.6.1.3 to MAS SaaS

    Posted 14 days ago

    In a traditional migration from on premises to SaaS, you would upload the attachments to the S3 bucket. Since you're re-importing, you could have provided the attachments as part of the import. On the object structure, if you include DOCLINKS as a child object and include the non-persistent attribute DOCUMENTDATA it would contain the actual file contents to import into the next system. This will increase your file size significantly though so it's not great for migrating everything. 

    You could try and send these via the REST API (Handling attachments - IBM Documentation) or using a tool like MXLoader to help you do it. But I'm not sure that scales really well either for this volume.

    I think the easiest path is to migrate the files to the S3 bucket manually (synchronizing all the files) and then come up with a process of mapping of old to new owner IDs. You'll need to do this for each dry run since the IDs will change every attempt. IE WONUM 1001 might be workorderid  95784 in the first run and 109280 in the second execution. But I think you will want to maintain this tracking anyways in case you need to refer back to mistakes that might have occurred during the data migration. 



    ------------------------------
    Steven Shull
    Naviam
    ------------------------------