Switch to Axiom
A clearer way to change software.
There is no universal one-click import. The useful work is understanding your current setup, mapping the records you need, and checking a sample before anyone depends on it.
- Last verified
- 2026-09-15
- Method
- Export, map, trial import
- Sample mapping
- Northbridge Studio
The route
From the tools you have to a checked cutover.
Current setup
Describe the tools you use today, who owns them, and which records matter. Axiom does not need your incumbent passwords on this website.
Methods
Most moves start with a file export and a field map. There is no universal one-click import, and no published live connector for Salesforce, HubSpot, Slack, DocuSign or Monday.
Assessment
We look at object types, owners, custom fields and history. Sample rows on this site are illustrative, not a guarantee that your tenant will import cleanly.
Mapping
Owners, stages and custom fields need an agreed map before a trial import. Unmapped fields stay out rather than being guessed.
Trial import
A limited sample is reviewed against the field map — contacts, opportunities, agreements, projects or conversations, depending on the workflow.
Validation
Check counts, ownership and a handful of records by hand. Exceptions stay listed instead of being silently dropped.
Cutover
Cutover is a planned change, not an afternoon switch for a whole company. Overlap with existing tools is expected until you choose to stop using them.
Checks
After cutover, confirm access, a few critical records and that completed agreements still have their original evidence. Rollback is not a published one-click product behaviour.
What can move
Record types, not a promise of parity.
This table is a starting conversation. It is not a green board of finished connectors. Last verified 2026-09-15.
| Source | Status | Known limitations | Last verified |
|---|---|---|---|
| Contacts and companies | Needs mapping | Owners and custom fields need a field map before import. | 2026-09-15 |
| Open opportunities | Supported | Stage names can be aligned to Connect stages where Connect is in use. | 2026-09-15 |
| Completed agreements | Requires review | Finished files are not newly signed by Veritas. Evidence stays with the original provider. | 2026-09-15 |
| Project boards | Needs mapping | Statuses, owners and comments need a field map before a board comes across. | 2026-09-15 |
| Private messages | Not supported | Do not assume Slack DMs or private channels can be exported. | 2026-09-15 |
| Custom automations | Not supported | A custom workflow usually has to be rebuilt by hand. | 2026-09-15 |
Incumbent systems
How those records typically move.
Salesforce, HubSpot, Slack, DocuSign and Monday usually start as an export and a field map. We will tell you what can come across and what has to be rebuilt.
| Source product | Status | Method | Known limitations | Last verified |
|---|---|---|---|---|
| Salesforce | Discuss | Customer export, then a field map | Not a live Axiom connector. Relationships, owners, custom fields and history need review. | 2026-09-15 |
| HubSpot | Discuss | Customer export, then a field map | Not a live Axiom connector. Activity history is not promised in full. | 2026-09-15 |
| Slack | Discuss | Workspace export, if you can produce one | Private messages, private channels and files are not assumed to be exportable. | 2026-09-15 |
| DocuSign | Discuss | Copy of completed files and the original evidence | Finished files are not newly signed by Veritas. In-progress envelopes are not a published import. | 2026-09-15 |
| Monday | Discuss | Board export for later review | Statuses, comments and attachments need a field map before a board comes across. | 2026-09-15 |
Import, integration, rebuild
These are different jobs.
A file import copies records. An ongoing integration would keep two systems in step. Workflow recreation and training are separate from the data move.
Deleting imported rows later does not undo every action taken in a new system. Rollback is not described here as a product button.