diff --git a/docs/migrate/fourkites.mdx b/docs/migrate/fourkites.mdx index 9e8a4097..e0b5dcc9 100644 --- a/docs/migrate/fourkites.mdx +++ b/docs/migrate/fourkites.mdx @@ -1,7 +1,7 @@ --- title: "Migrating from FourKites" sidebarTitle: "FourKites" -description: "Map FourKites ocean tracking fields, parameters, and errors to their Terminal49 equivalents. Includes webhook setup, carrier coverage, and a migration checklist." +description: "Map FourKites ocean tracking fields, webhooks, and errors to Terminal49 equivalents. Includes carrier coverage and a migration checklist." --- diff --git a/docs/migrate/gnosisfreight.mdx b/docs/migrate/gnosisfreight.mdx index 610defff..9d0ab3a5 100644 --- a/docs/migrate/gnosisfreight.mdx +++ b/docs/migrate/gnosisfreight.mdx @@ -1,7 +1,7 @@ --- title: "Migrating from Gnosis Freight" sidebarTitle: "Gnosis Freight" -description: "Map Gnosis Freight's Container Lifecycle Management (CLM) Platform fields, OAuth2 auth, and container polling to their Terminal49 equivalents. Includes authentication, request mapping, and migration checklist." +description: "Map Gnosis Freight CLM Platform fields, OAuth2 auth, and container polling to Terminal49 equivalents. Includes request mapping and checklist." --- If you have Gnosis Freight's CLM platform in production, this page maps it onto Terminal49 field by field, so you can cut over without reverse-engineering our schema. diff --git a/docs/migrate/home.mdx b/docs/migrate/home.mdx index 2803cc57..68209ef7 100644 --- a/docs/migrate/home.mdx +++ b/docs/migrate/home.mdx @@ -1,7 +1,7 @@ --- title: "Migrate to Terminal49" sidebarTitle: "Overview" -description: "Move your container tracking integration to Terminal49 from SeaRates, project44, FourKites, Vizion, OpenTrack, ShipsGo, GoComet, Beacon, or Gnosis Freight in a weekend." +description: "Migrate container tracking to Terminal49 from project44, FourKites, Vizion, ShipsGo, GoComet, Gnosis Freight, SeaRates, OpenTrack, or Beacon." --- Terminal49 integrates directly with 36\+ ocean carriers and North American terminals. If you are running another provider today, these guides map your current integration onto ours, field by field, so you can cut over without reverse-engineering our schema. diff --git a/docs/migrate/project44.mdx b/docs/migrate/project44.mdx index ea5e8714..b166262f 100644 --- a/docs/migrate/project44.mdx +++ b/docs/migrate/project44.mdx @@ -1,7 +1,7 @@ --- title: "Migrating from Project44" sidebarTitle: "Project44" -description: "Map Project44 ocean tracking fields, parameters, and errors to their Terminal49 equivalents. Covers webhooks, container holds and fees, and a migration checklist." +description: "Map project44 ocean tracking fields, webhooks, and errors to Terminal49 equivalents. Covers container holds, per diem fees, and checklist." --- If you are using Project44 for ocean visibility, this guide maps the ocean portion of Project44 onto Terminal49 field by field, so you can replace the ocean leg without reverse-engineering our schema. diff --git a/docs/migrate/shipsgo.mdx b/docs/migrate/shipsgo.mdx index 71697091..3cc8f896 100644 --- a/docs/migrate/shipsgo.mdx +++ b/docs/migrate/shipsgo.mdx @@ -1,7 +1,7 @@ --- title: "Migrating from ShipsGo" sidebarTitle: "ShipsGo" -description: "Map ShipsGo container tracking API fields, parameters, and errors to their Terminal49 equivalents. Includes webhook setup, carrier coverage, widget replacement, and a migration checklist." +description: "Map ShipsGo container tracking API fields, webhooks, and errors to Terminal49 equivalents. Covers carrier coverage, widget replacement, checklist." --- If you have the ShipsGo container tracking API in production, this page maps it onto Terminal49 field by field, so you can cut over without reverse-engineering our schema. diff --git a/docs/migrate/vizion.mdx b/docs/migrate/vizion.mdx index 9bd41651..c8d25ecc 100644 --- a/docs/migrate/vizion.mdx +++ b/docs/migrate/vizion.mdx @@ -1,7 +1,7 @@ --- title: "Migrating from Vizion" sidebarTitle: "Vizion" -description: "Map Vizion container tracking reference IDs, webhooks, and API fields to their Terminal49 equivalents. Includes authentication, request mapping, and migration checklist." +description: "Map Vizion container tracking reference IDs, webhooks, and API fields to Terminal49 equivalents. Includes authentication, mapping, and checklist." --- If you have the Vizion tracking API in production, this page maps it onto Terminal49 field by field, so you can cut over without reverse-engineering our schema.