Kickstart in Adobe Cloud Storage | Community
Skip to main content
Level 2
June 26, 2026
Question

Kickstart in Adobe Cloud Storage

  • June 26, 2026
  • 5 replies
  • 154 views

Testing transition to Adobe Cloud storage via a Kickstart which is how we load our planned work.

We converted our sandbox to Cloud so a small group of sys admin can test. I created a cloud portfolio and cloud campaigns and cloud templates.  

First tried loading campaigns and projects with the existing legacy portfolios, campaigns and templates and all went well.

Using the same formatting, I created kickstarts with the cloud portfolio, campaigns and templates and I get the error that “Your file is correct, but nothing was imported”.

Any ideas what the issue is since the error is very vague?  We are having all sorts of other issues with legacy and cloud not playing well together or with Fusion for that matter so there is something going on. 

    5 replies

    Lyndsy-Denk
    Community Advisor
    Community Advisor
    June 26, 2026

    I’m very interested to hear more about how people are doing with Adobe Cloud Storage as we’re moving over soon.

    (For those not in the know, this is related mostly to Unified Approvals. Read more here: Move to Workfront on Adobe cloud storage | Adobe Workfront)

    KerrySt1Author
    Level 2
    July 20, 2026

    see below at bottom of string

    skyehansen
    Community Advisor and Adobe Champion
    June 26, 2026

    can we see the kickstart or … some sort of one line sample?

    KerrySt1Author
    Level 2
    July 2, 2026

    see below

    skyehansen
    Community Advisor and Adobe Champion
    July 2, 2026

    there’s a lot going on here and you might benefit from submitting a support ticket with your kickstart file.

     

    First: I’m not sure if you’re aware that some of the lines are marked true and others are false? And I’m not sure which lines you intended to be imported as a kickstart. I’m sure that’s not what’s affecting the kickstart but just wanted to mention it up front as it makes it easier to troubleshoot when we have a better idea of which lines are the problem lines so we can focus down on the problem. Obviously it’s also true that without being able to see the entire line, we’re still not sure which cell is causing the issue. All this to say, if you can just give us the column headers that you filled out and the content you filled them out with, that would help. Tab name would also help (it’s also a point of troubleshooting… this is why I suggested a ticket)

     

    Second: I always recommend kickstarting one line. If you’re able to get one line working you can get more lines working. It makes it easier to troubleshoot as well -- otherwise we’re looking at a screenshot wondering what you were expecting.

     

    Last: Have you considered creating your ideal scenario in Workfront and then kickstarting it out? (I guess your explanation was quite vague and I didn’t get the sense that you had tried that -- i.e. did you create a project in a cloud portfolio (or whatever you need… not sure what campaign equates to), and kickstart that out to inspect how the kickstart is configured?)

    Adobe Support
    June 29, 2026

    Hi ​@KerrySt1, Adobe Cloud Storage changes how document permissions work, documents inherit permissions from their parent task, issue, or project rather than being shared individually, and the folder structure is auto-generated by the system. If your Kickstart templates include any document-related data or linked folder references, those may not behave the same way in a Cloud Storage environment.

    Can you share more about what specifically isn't working? If the issue persists after testing, I'd also recommend opening a support case with Adobe since this involves a sandbox environment conversion to Adobe Cloud Storage, team can look at the backend configuration and confirm whether what you're seeing is expected behavior or something that needs to be addressed before you move production.

    KerrySt1Author
    Level 2
    July 2, 2026

    Hi, I have included a screenshot of just the columns that are related to storage. In the screenshot, all of these projects are using legacy templates loaded in to legacy campaigns into a legacy portfolio and everything loaded successfully. I then changed the the rows to include projects using a template created in the cloud loading in to a campaign created in the cloud in a portfolio created in the cloud not converted and I get the 400 error stating that my file is correct but nothing was imported. 

     

     

    KerrySt1Author
    Level 2
    July 2, 2026

    Here is the screenshot of the cloud kickstart that threw the error.

     

    Level 2
    July 20, 2026

    I’m interested in learning if you were able to resolve your error.  I’ve had multiple conflicts moving from legacy to Cloud in the past few weeks.  Thinking good thoughts for you!

    KerrySt1Author
    Level 2
    July 20, 2026

    see answer below

    KerrySt1Author
    Level 2
    July 20, 2026

    We are still trying to wrap our heads around how we are even going to approach this as we have so many legacy projects in flight and so many campaigns that stay in process for months. We may have to create duplicate portfolios for both storage and how do we even program all that in Fusion. (We rely heavily on Fusion for lots of automation). Still trying to find our plan of attack.  BUT turns out I was able to resolve the Kickstart issue. 

    We use kickstarts to load planned campaigns and projects and alot of data that goes with them. When l was creating I changed the name on the tab and that was the issue. 😝 Wish the error had told me that. I simply had Sheet 1 as the name and it needed to be PROJ Projects. It wasn’t related to the storage selection. 

    skyehansen
    Community Advisor and Adobe Champion
    July 20, 2026

    very important thing to learn! Glad you found your error.