The part that gets skipped
Most rushed onboardings connect the email domain, import a list and call it live. The portal works. It just does not reflect how the business actually operates, so within a month people are back in spreadsheets.
What has to happen first
- Domain authentication and sending reputation, before a single campaign goes out.
- A property audit — what you will actually record, and what the existing fields mean.
- Lifecycle stages defined in your language, not the default one.
- Consent and subscription types set up properly, because retrofitting them is painful.
Every one of these is boring, and every one of them is cheaper to do before the data goes in than after.
Then the data
Import order matters. Companies first, then contacts, then deals, so associations resolve as they land rather than needing a second pass. Keep the source files and a rollback, because the first import is rarely the last.
This is also where duplicates get decided — see how the match logic works for what will and will not be caught.
Then the build
Forms, lists, workflows and reporting, built against the map rather than invented as you go. Anything automated gets a goal and an exit, so nothing keeps running after the outcome has happened.
A portal that is technically live and practically unused is the most expensive outcome available, because you are paying the licence either way.
Then the handover
One person on your side has to be able to run it. That means a runbook, naming conventions that make sense to your team, and a list of what to check first when something looks wrong.