Home
Environments and migrations
Introduction to Environments & Migrations Safe iterations using environments Configuring the CLI Write and test migration scripts Apply migrations to primary environment Running legacy migration scripts Keeping multiple DatoCMS projects in sync

Sorry, no results found for "".

Environments and migrations > Running legacy migration scripts

Running legacy migration scripts

If you have migration scripts written for the old datocms-client package, you don't need to convert them to the latest @datocms/cma-client package.

You can simply move them to a legacyClient directory:

Terminal window
mkdir migrations/legacyClient
mv migrations/*.js migrations/legacyClient

The CLI will take care of passing those migration scripts to the old API client, while all the new migration scripts will be written directly in the migrations directory, and will use the new API client.

Did this doc help you?
Yes
No
Would you like to add more information?
Optional
To receive further updates or address your feedback, kindly share your email address with us.
Optional

If you need a reply, please contact support instead.

Need help?
Explore our forum, contact support, or connect with our sales team . You can also chat live with other users in our Slack channel.