If I leave the platform or consultant, can I export my data and workflows?

Data, history, and workflow logic are different assets

A product may export contact rows but not attachments, activity history, prompts, field mappings, or the rules that move work between systems. A proprietary backup may help the same vendor restore an account while being useless to a replacement platform.

Ask what every export contains, which documented format it uses, and whether identifiers and relationships remain understandable. During a trial, export sample records and inspect them instead of accepting a portability claim at face value.

Keep control of the operating accounts

The business should hold the primary accounts for domains, phone numbers, customer data, automation tools, and essential software. Consultants can receive individual, least-privilege, time-bounded access without owning the service or sharing an administrator password. Record billing ownership, recovery contacts, and how access is removed.

For custom work, define ownership and delivery of configuration, code where applicable, operating notes, and credentials created for the project. Another qualified person should be able to understand the trigger, destinations, main rules, and failure path.

Price the exit as honestly as the entry

Switching still requires connections to be rebuilt, data reconciled, rules tested, users trained, and a cutover scheduled. Ask which parts are vendor-specific, whether exports or API access change after cancellation, what egress or assistance costs apply, and how long retained copies remain available.

Review cancellation and deletion terms in the current agreement. Confirm how deletion can be requested or evidenced, subject to obligations that apply to the business. Standard interfaces, a small number of dependencies, and documented field maps reduce rediscovery, but no architecture makes migration effortless.

• Can we export records, attachments, status history, and audit data?
• Can workflow rules be exported or only documented and rebuilt?
• What functionality and access end immediately at cancellation?
• Who can operate a safe parallel run and cutover?

Make exit readiness part of delivery

A project should finish with a working result and a clear account of what the business owns, what depends on a vendor, and what support remains. Store documentation where the business controls access rather than inside a consultant's private workspace.

Revisit portability before adding another critical process to the same platform. The goal is not to switch constantly; it is to retain a practical choice when price, product direction, risk, or business needs change.