diff --git a/docs/docs/migration/0.0.60-to-1.0.0.md b/docs/docs/migration/0.0.60-to-1.0.0.md
index 57ae854728..f79c7bd82b 100644
--- a/docs/docs/migration/0.0.60-to-1.0.0.md
+++ b/docs/docs/migration/0.0.60-to-1.0.0.md
@@ -36,7 +36,7 @@ Here:
 You can use a command similar to the following:
 
 ```bash
-PGPASSWORD=[DBPassword] pg_restore --clean --if-exists --disable-triggers -d [DBName] -1 -U postgres -h [DBHostName] [DBName].dump
+PGPASSWORD=[DBPassword] pg_restore --clean --if-exists --disable-triggers -d [DBName] -U postgres -h [DBHostName] [DBName].dump
 ```
 
 Here:
@@ -47,7 +47,6 @@ Here:
 - `[DBName]` is one of five database listed above
 - `--clean --if-exists` switches make `pg_restore` drop the dataset objects before importing the data so that we don't need to worry about `duplicate keys` error.
 - `--disable-triggers` switch will temporarily disable foreign key constraints and triggers so that we won't encounter `violates foreign key constraints` errors due to the restore sequence of the table data.
-- `-1` switch make `pg_restore` perform the restore as one transaction.
 
 - 4> Once data restore is complete for all database, you can redeploy the new Magda deployment to turn on the [backup mode](../how-to-recover-with-continuous-archive-backup.md) to backup the database.