Alright, so after about a decade of RoboForm for Teams, we finally made the jump to 1Password Business last quarter. The migration was... an event. Since everyone here is obsessed with granular details, here's my take.
The good is genuinely good. The secret key + master password model is a huge step up in security posture, and our infosec team stopped scowling for a whole day. Travel mode is a killer feature for our remote folks. The shared vault structure is way more logical than what we were wrestling with. And the CLI tool? Actually useful for some light automation, which RoboForm never even pretended to offer.
The bad, however, has some rough edges. The billing model feels like it was designed by someone who's never met a real business. Counting every user with *any* vault access, even if they're just a guest in a single shared vault? That's a clever way to inflate the seat count. Our RoboForm plan was cheaper for a reason—it was simpler, even if it was dumber. Also, the browser extension can be a little too clever for its own good, sometimes not offering to save a login on a custom auth flow. I've seen it happen on a few of our own internal tools we're A/B testing.
The ugly was the migration itself. The official import tool is... optimistic. We had a solid 15% of logins that needed manual cleanup—duplicates, weird custom fields from RoboForm that turned into garbled notes, shared items that lost their grouping. Took a solid week of janitorial work to feel confident.
Overall, it's a more powerful tool, no question. But the complexity tax is real, both in cost and in setup. If you're coming from something simpler, budget for hidden migration time and scrutinize that user count on your invoice.
just sayin'
Data over dogma.
I'm the Head of Data at a 300-person SaaS company, and I directly manage our internal analytics stack. We've been on 1Password Business for two years, after evaluating it against LastPass and RoboForm for Teams, and I handle the technical integration for service account secrets.
**Core Comparison**
1. **Security Model & Secret Storage**: 1Password's secret key + master password provides actual end-to-end encryption. In practice, this meant we could securely store not just logins but also database credentials and API keys in vaults, which we couldn't do confidently with RoboForm. The Travel Mode feature let us deprovision vaults for employees crossing borders, which was a hard requirement from legal.
2. **Cost Structure & Seat Counting**: The pricing is not transparent. At our size, we pay ~$7.50/user/month. The bill increased 22% after our first audit because it counts any user with *view* access to a shared vault as a billed member. RoboForm's simpler per-seat model was cheaper, but you got less. If you have many read-only external guests, this cost escalates quickly.
3. **Technical Integration & Automation**: 1Password's CLI and integrations are a genuine advantage. We use the `op` CLI in GitHub Actions to pull secrets for deployments and in our dbt projects for warehouse credentials. This is a concrete workflow RoboForm couldn't support. The downside is the 1Password Secrets Automation add-on is a separate, costly SKU.
4. **User Experience & Reliability**: The browser extension is generally superior but has specific failure modes. We've documented cases where it fails to capture logins on pages with dynamic form IDs or non-standard JavaScript auth flows (like our React-based admin panel). RoboForm was less "smart" but more consistent on these edge cases. 1Password support resolved our ticket on this in about 72 hours with a workaround.
**My Pick**
I recommend 1Password Business if you need to vault service credentials or have strict compliance needs, but you must tightly control shared vault membership to manage cost. If you're just managing employee web logins and want the simplest cost structure, RoboForm is the pragmatic choice. To decide, tell us your ratio of internal users to external guests and whether you need to store non-website secrets.
Garbage in, garbage out.