Original page

Switching to Hourglass

Move your CRM in weeks, keeping every record and its history

A planned migration with a test run, team-by-team go-lives and our onboarding team beside you, so selling and serving never stop.

Hourglass admin for many business units: 14 units, 3,820 users and six brands, beside a new permission set waiting for an admin's approval.

The migration playbook

Four steps to a calm switch

Plan, test, go live and tidy up, with your data intact at every step.

  1. Plan the move

    Map objects, fields and owners with our team. Decide which teams go first.

  2. Run a test import

    Import into a sandbox and check the results. Fix mappings before anything goes live.

  3. Go live team by team

    Start with one hub and one team. Old and new run side by side for a while.

  4. Retire the old tools

    Move integrations and reports across. Switch off what you no longer need.

Suggested updates for Bellmere Bank, prepared by the Data Agent: a new contact, a missing industry and a duplicate merge, with Approve changes, Review each and Dismiss buttons.

What changes

What a calm switch looks like

An import card for moving from another CRM: contacts, accounts and opportunities mapped to contacts, companies and deals, 48,210 records ready and a test import passed.

What your data team notices

The hardest part of a migration is the fear of losing history. Hourglass imports records with their timelines, so a rep’s first day in the new CRM looks familiar.

Teams move when they’re ready, and the onboarding team checks every step with you.

Learn more about integrations and moving your data

Avoiding the usual risks

Why software projects stall, and how a planned move avoids it

Switches that go wrong tend to fail in the same few ways. Each step of a move to Hourglass is there to stop one of them.

  • Moving everything at once

    Go live one team at a time, starting with the tools that cause the most handoffs.

  • Losing records and their history

    Contacts, deals and tickets come over with their timelines, so no one starts from a blank record.

  • Skipping the test run

    Import into a sandbox first, and fix the mappings before anything goes live.

  • Teams that never switch over

    Training for each team as it moves, and one record that every team works from.

  • Systems left disconnected

    Two-way syncs keep your ERP, billing and support tools in step, with rules for which one wins.

  • No one owning the plan

    A rollout plan made with our onboarding team, and checked with you at every step.

TRUSTED BY TEAMS IN BANKING, RETAIL, MANUFACTURING AND SOFTWARE

Illustrative customers for this demo.

  • Mercantile Bank
  • KeepCup
  • Suzuki
  • Arduino
  • Allica Bank
  • Panoramic Doors
  • Konica Minolta
  • Threekit
  • Alacrity Solutions
  • MVC Group
  • Viessmann
  • Eventus

Customer stories

Teams that made the switch

They moved off separate tools and legacy systems one team at a time, and kept their history.

Illustrative stories for this demo.

See customer stories

“We were paying for seven tools that didn’t talk to each other. Moving marketing, sales and support onto Hourglass gave every team the same numbers.”

Hannah Cho

Chief Revenue Officer, Eventus

  • 7

    tools replaced by Hourglass

  • 5 weeks

    to move every team over

Tell us what you’re working on, and we’ll show you how Hourglass fits