<p>Turns out the Craft needed to run another set of migrations for Commerce, so I ran the <code>./craft migrate/all</code> a couple more times to fully update the database.</p>

<p>If anyone is doing this, it's worth backing up the DB after each set of migrations to save running them again if you run into an error.</p>

CC BY-SA 4.0
2019-08-27T15:22:38.607Z
2019-08-27T15:22:38.607Z
Ant Cooper
<p>I'm migrating a large Craft + Commerce site up to Craft 3. I've completed all the initial steps and get as far as the "<em>To complete the update, some changes must be made to your database. Finish up</em>" message. </p>

<p>The first time I tried this it timed out, so I used the <code>./craft migrate/all</code> to perform all the database updates. This worked well - not surprised it timed out over http given the amount it has to do!</p>

<p>Problem is when going back to the Admin URL I still get the database message, if I click <em>Finish up</em> it still times out, I guess it is trying to reapply the migration.</p>

<p>Is there a way to let the Craft install know I have already done this?</p>

<p>Thanks</p>

CC BY-SA 4.0
2019-08-16T20:29:13.933Z
"Problem is when going back to the Admin URL I still get the database message," - that shouldn't have happened. Maybe your site was still in maintenance mode from the initial update attempt failure and after you ran the console command, the CP wanted to take it out of maintenance mode, Craft tried to make a database backup and it timed out before that could complete?
Brad Bell
<craft3><updates>
Updating large database from Craft 2 > 3 via command line
# Updating large database from Craft 2 > 3 via command line

(Asked by: username_0 on 2019-08-16)

I'm migrating a large Craft + Commerce site up to Craft 3. I've completed all the initial steps and get as far as the "*To complete the update, some changes must be made to your database. Finish up*" message.

The first time I tried this it timed out, so I used the `./craft migrate/all` to perform all the database updates. This worked well - not surprised it timed out over http given the amount it has to do!

Problem is when going back to the Admin URL I still get the database message, if I click *Finish up* it still times out, I guess it is trying to reapply the migration.

Is there a way to let the Craft install know I have already done this?

Thanks

**Tags:** craft3, updates
> **Comments:**
> **username_1**: "Problem is when going back to the Admin URL I still get the database message," - that shouldn't have happened. Maybe your site was still in maintenance mode from the initial update attempt failure and after you ran the console command, the CP wanted to take it out of maintenance mode, Craft tried to make a database backup and it timed out before that could complete?  

---

## 1 answers

### Answer by username_0 on 2019-08-27. Score: 2

Turns out the Craft needed to run another set of migrations for Commerce, so I ran the `./craft migrate/all` a couple more times to fully update the database.

If anyone is doing this, it's worth backing up the DB after each set of migrations to save running them again if you run into an error.


---

