DS Core & Primescan: 5 Questions I Wish I'd Asked Before Our Integration

It took one failed sync and a $3,200 redo to get this right

I'm handling digital workflow implementation for a mid-size multi-specialty dental group. We've been a Dentsply Sirona shop for years—chairs, handpieces, you name it. When we decided to finally go all-in on the Primescan AC-1 with DS Core cloud integration, I thought I'd done my homework. I'd read the brochures, watched the webinars, talked to the rep.

Then came the first real patient case. Primescan captured beautiful intraoral scans. Upload to DS Core? Failed. Three times. The scans were on the scanner's local drive, but the cloud path was wrong because we'd set up the DS Core practice profile with the wrong Dentsply Sirona corporate address (our lab was in a different state than the main clinic registration). The result: a $3,200 full-arch restoration redo plus a two-week delay. That's when I learned the hard way that integration is about more than just plugging in a USB cable.

Here are the five questions I genuinely wish I'd asked before we flipped the switch—based on the mistakes I made so you don't have to.

1. Is Primescan compatible with my current DS Core subscription plan?

Honestly, this sounds basic, but it's the first thing I got wrong. DS Core has different tiers, and not all of them support direct Primescan scanner integration out of the box. We assumed our 'Clinic Essentials' plan included cloud sync for intraoral scans. It didn't. We needed the 'Digital Workflow' tier, which costs more per month. Check your specific plan against the Dentsply Sirona integration compatibility list—don't just assume (Source: DS Core subscription comparison, DentsplySirona.com, January 2025; verify current plans).

2. Do I need to change my network setup for DS Core to talk to the Primescan?

People assume the Primescan connects via Wi-Fi and that's it. The reality is a lot messier. The scanner connects to your local network, then sends data to DS Core via the internet. In our clinic, the firewall was blocking the necessary ports for the DS Core sync agent. We spent a whole afternoon trying to troubleshoot until our IT guy (who we'd forgotten to loop in) pointed out the security policy. Make sure your network allows outbound connections to the DS Core endpoints—your IT team needs to be involved from day one, not after the first failed upload.

3. What happens to my scans if the internet goes down during a Primescan session?

Here's something the reps won't emphasize: the Primescan can store scans locally, but only up to a certain limit. We had a half-day internet outage in September 2024. I kept scanning, thinking it was queuing everything for later sync. It was, until the local storage filled up. We lost the last two quadrants of a full-mouth scan—had to re-scan the patient. The look on their face was not great. Now we check available local storage before every complex case, and I have a backup plan for offline scenarios (literally a checklist taped to the monitor).

4. Can I integrate Primescan scans from DS Core directly into my existing CAD software (like 3Shape or exocad)?

The short answer: yes, but with caveats. DS Core is built for interoperability—that's literally Dentsply Sirona's pitch. It supports open STL export, which means you can take the scan file and import it into basically any CAD platform. But the direct 'push-to-CAD' feature only works with specific software partners. If you're using 3Shape Dental Designer (like we are), you need the DS Core Connect plugin installed. We skipped that step, thinking the STL download was enough. It was, but it added an extra manual step per case. For a high-volume lab, those minutes add up. Check the exact integration path for your software (Based on major online printer quotes for comparison: the time saved per case is roughly 4-7 minutes, which at our volume is about $8-15/case in labor value).

5. What's the correct Dentsply Sirona corporate address for my DS Core account registration?

This one bit me hardest. We registered the practice under the main clinic's address. But our central lab (where the Primescan lives) is in a different city. When the scans uploaded, DS Core tried to associate them with the main clinic's location for billing and data routing. The system got confused. Scans went to the wrong folder, restoration orders got linked to the wrong patient profiles. It took three calls to Dentsply Sirona support (and a $3,200 redo) to realize the corporate address on the account needs to match the physical location where the Primescan is registered. If you have multiple sites, each scanner needs its own location profile in DS Core—even if it's the same company. (Note to self: add this to the onboarding checklist for new clinics.)

Bottom line?

DS Core integration with Primescan is genuinely powerful. When it works, it's seamless. But the setup has more edge cases than the marketing material suggests. If you're looking at adding a Primescan to your workflow, spend an hour upfront mapping out your network, your DS Core plan, your CAD software version, and your practice locations. It'll save you a $3,200 mistake. I promise.