Recheck legacy transfer instructions
Dentsply Sirona announced a transition from Connect Case Center to DS Core in most countries. Its current lab-facing DS Core page describes case downloads and several supported formats. Legacy Connect instructions therefore need a current regional/account check rather than reuse as a universal procedure.
Confirm the practice’s software environment and the receiving lab’s enabled route. This guide does not assert that Pristine has a DS Core integration or that every account exposes the same export options. Product names are used descriptively, without affiliation.
Identify what is actually available
| Question | Acceptance evidence |
|---|---|
| Current route | The actual supported account and case-sharing workflow in the relevant region. |
| Available records | Named scan roles, relationships and supplementary instructions in the accepted case. |
| Export purpose | The file type needed for the receiving CAD task, not merely any downloadable file. |
| Receiver access | The responsible lab can retrieve and identify the intended package. |
| Continuation | The tested output supports the agreed next task in the receiving environment. |
A platform’s advertised format list is not proof that a particular uploaded case contains every needed record. Examine the actual available package with the submitting and receiving teams. Missing instructions still require clarification.
Test a complete handoff
Use an authorized representative case. Compare its available records with the intended assignment, then confirm how the receiver obtains the agreed outputs. Keep the accepted source state and label any exported copies so that later changes are traceable.
Illustrative exception: a scan can be viewed in a platform, but the agreed native continuation package is not available through the selected route. Resolve the output requirement before design begins; viewing and downloading are different acceptance questions.
Keep responsibilities visible
The practice supplies and approves the clinical records; the receiving lab confirms the route and production requirements; the designer follows the agreed assignment and reports uncertainty. These roles should be recorded for the actual collaboration rather than inferred from a portal status.
If the account route changes, rerun the acceptance check and update the saved instructions. Avoid promising transfer availability, integration, timing or manufacturing compatibility from a general description of DS Core or CEREC. Consult current vendor support for account-specific steps.
Source notes
Primary documentation checked October 6, 2026. Software details describe the cited product documentation; the handoff frameworks and illustrative examples are original editorial guidance. Confirm current version and account requirements with the publisher.
Prepared by Pristine Dental Design · October 6, 2026. Guidance for professional case communication and review. Actual prescriptions, manufacturer requirements and receiving-team approvals govern design and production.