Csmig NPM | npm.io

csmig

Migrating Data from Legacy CMS to Contentstack.

csmig
Prerequisites
Usage
Commands
csmig

Prerequisites

Basic understanding of CLI
Contentstack account
Node Version 16v+

Usage

$ npm install -g csmig
$ csmig COMMAND
running command...
$ csmig (-v|--version|version)
csmig/1.3.1 win32-x64 node-v16.14.1
$ csmig --help [COMMAND]
USAGE
  $ csmig COMMAND
...

Commands

csmig help [COMMAND]
csmig run [FILE]
csmig cf [FILE]
csmig cs [FILE]
csmig dp [FILE]
csmig wp [FILE]

`csmig help [COMMAND]`

display help for csmig

USAGE
  $ csmig help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

`csmig run`

Run to migrate Legacy CMS Data to Contentstack

USAGE
  $ csmig run

`csmig cf`

Run to migrate Contentful Data to Contentstack

Once the package is installed globally, you must run this command in the terminal.

USAGE
  $ csmig cf

Enter both the filename and the file path, for example, /user/admin/wordpressFile.xml.
Contentstack regional options are available to you. Choose the area where you want to carry out your CS task.
- NA
- EU
- AZURE-NA
- AZURE-EU
- GCP-NA
You must enter your password and Contentstack email to log in.
Enter the file name (extension included or not) and the precise location of the file.
- Only the JSON file format is supported.
- Since Contentstack does not support all IDs, we are adding the prefix to prevent migration issues.
- For each prefix ID that Contentstack does not support, logs are produced.
Whether you import converted data into the new stack or the old stack is entirely up to you.
Here is a list of the organizations. You must select the organization you want to select by typing its name or pressing the "down key."
You will enter the stack name after choosing the organization, and a new stack will be created.
The new stack has now successfully imported and converted the Contentful data.

`csmig cs`

Run to migrate Contentstack Data to Contentstack

Once the package is installed globally, you must run this command in the terminal.

USAGE
  $ csmig cs

Enter both the filename and the file path, for example, /user/admin/wordpressFile.xml.
Contentstack regional options are available to you. Choose the area where you want to carry out your CS task.
- NA
- EU
- AZURE-NA
- AZURE-EU
- GCP-NA
You must enter your password and Contentstack email to log in.
Select the region where you want to import the data from your source region stack.
- From the NA region to the EU region, we can move the stack.
  - From the NA region to the EU region, we can move the stack.
  - From the NA region to the AZURE-NU region, we can move the stack.
  - From the NA region to the AZURE-EU region, we can move the stack.
  - We can migrate the stack to the same region.
  - The local system allows us to import the stack data.
  - The stack data can be exported to the local system.
- As an illustration, in this case, we have chosen the NA region for the AZURE-NA regions.
Select the source organization after choosing the destination region option.
Your source data will be successfully exported after choosing the source organization and the source stack.
After the export is finished, you must sign in to the destination area. We have chosen the Azure region in this instance, so we entered our Azure-NA region credentials.
Users have two options after successfully logging in to the Azure region: they can import into the new stack or not.
Select the Destination Organization
Name your new stack.
Select if the data should be imported with the new master locale or not.
From the link, enter the new locale code. Note: From the link, which is highlighted in blue, one can choose a new locale code.
The import will begin automatically following the entry of the new master locale code.

`csmig dp`

Run to migrate Drupal Data to Contentstack

Once the package is installed globally, you must run this command in the terminal.

USAGE
  $ csmig dp

Enter both the filename and the file path, for example, /user/admin/wordpressFile.xml.
Contentstack regional options are available to you. Choose the area where you want to carry out your CS task.
- NA
- EU
- AZURE-NA
- AZURE-EU
- GCP-NA
You must enter your password and Contentstack email to log in.
Users can select which Drupal version they want to convert.
- Drupal 7
- Drupal 8 or 8+
Users have to add some MySQL credentials.
- Enter Hostname:
- Enter Username:
- Enter Password (optional)):
- Enter Port No. (optional):
- Enter database name:
Eg:-
- Enter Hostname: localhost
- Enter Username: admin
- Enter password (optional):
- Enter Port No. (optional):
- Enter database name: db_name
Whether you import converted data into the new or old stack is entirely up to you.
Here is a list of the organizations. You must select the organization you want to select by typing its name or pressing the "down key."
After choosing the organization, you will enter the stack name and create a new stack.
Note: If the user selects the old stack or existing stack, its master locale should be “English - United States” and make sure the stack is empty, or else migration will fail
The new stack has now successfully imported and converted the Drupal data.

`csmig wp`

Run to migrate WordPress Data to Contentstack

Once the package is installed globally, you must run this command in the terminal.

USAGE
  $ csmig wp

Enter both the filename and the file path, for example, /user/admin/wordpressFile.xml.
Contentstack regional options are available to you. Choose the area where you want to carry out your CS task.
- NA
- EU
- AZURE-NA
- AZURE-EU
- GCP-NA
You must enter your password and Contentstack email to log in.
Enter both the filename and the file path, for example, /user/admin/wordpressFile.xml.
- It only accepts files in the XML format.
Enter the prefix to make custom content type (Optional)
Whether you import converted data into the new stack or the old stack is entirely up to you
Here is a list of the organizations. You must select the organization you want to select by typing its name or pressing the "down key."
After choosing the organization, you will enter the stack name and create a new stack. Note: If the user selects the old stack or existing stack, its master locale should be “English - United States” and make sure the stack is empty, or else migration will fail
The new stack has now successfully imported and converted the WordPress data.