Einstein Language is retired. Migrations need to map each existing call to the right modern replacement; the steps below cover the planning, not the deprecated build.
- Inventory every Einstein Language call
Search the codebase for the Einstein Platform Services base URL or the intent, sentiment, and NER endpoints. List every consumer, the dataset it depends on, and the downstream consumer of the prediction.
- Classify each call by use case
Group calls into conversational intent, record classification, sentiment scoring, and entity extraction. The replacement path depends on the use case category, not the original API endpoint.
- Pick the modern replacement
Conversational intent goes to Einstein Bots. Record classification goes to Einstein Case Classification or Prediction Builder. Sentiment goes to Einstein Sentiment in Service Cloud. Entity extraction usually goes to a Prompt Builder template returning structured output.
- Re-train or re-template on the new path
Most replacement features need their own training data or prompt design. The old Einstein Language dataset can seed the new path but rarely transfers directly because the surface differs.
- Cut over with a parallel-run period
Run the new path alongside the old call for one to two weeks, comparing outputs. Cut over when the new path matches or beats the old on the team's evaluation set.
The replacement for live conversational intent classification. NLU is embedded in the bot builder.
The replacement for case-level text classification. Trains on historical cases and fills in Type and Reason fields.
The replacement for case and chat sentiment scoring. Embedded in Service Cloud.
The replacement for entity extraction and custom text understanding. Structured output schemas make the returned data machine-readable.
The fallback when no embedded feature fits. Custom model trained externally and registered in Einstein Studio.
- Einstein Language is not currently accepting new connected apps. Treat any new integration request as a migration to a modern path.
- Existing apps that have not migrated are on borrowed time. Even if calls still succeed, the API has a retirement timeline and support is winding down.
- The old auth pattern (JWT signed against a downloaded private key) does not transfer to the new paths, which use standard Salesforce authentication and metadata.
- Trailhead modules and old documentation still reference Einstein Language. Confirm with current release notes before recommending it for a new project.
- Replacement paths produce different output formats. Downstream consumers need to be updated, not just the API call.