Glossary

Migration words.

The terms used across the platform pages. Each one is a decision the cutover will ask for.

A to Z

Every term, in plain language

A call, email, meeting, or task attached to a record. Plan where each type lands.

The window when the new system becomes the one people edit.

The pass that merges records sharing a key before they are loaded. Do it in the source, or the target inherits the mess.

The records that changed after the main load and before the freeze. They need their own pass.

The hours when the old system stops taking changes, so the final load is not already stale.

The morning people are told the new system is the real one. The checklist for that morning is part of the path.

Notes, emails, stage changes, and files. Deals can move without history. People notice on Monday.

Where each object and field lands, including the ones you refuse to bring.

The kind of record: contact, company, deal, ticket, custom module. A module name is not automatically the target object.

The person responsible for a record after go-live. Empty owners in the source become empty owners in the target.

A period when both systems are checked against each other before people are told to stop using the old one.

The source system and the target system, named together. Salesforce to HubSpot is a different path from a spreadsheet to a CRM.

A field with a fixed set of values. Twenty source values need an owner who decides which ones survive.

The tested way back to the old system if the cutover fails. A rollback you have not tried is a hope.

The system you are leaving. It still holds the history until the cutover says otherwise.

The system you are moving to. It does not clean the data for you.

Talk to a partner

A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.