Migration
Leave without burning the bridge. Arrive without losing history.
Import from an export file, read the mapping, rehearse with a dry run, then cut over when you are ready. Reverse it if it looks wrong.
In buildImporters are being built. This is the plan, not a shipped feature.
Four steps
Export from your current tool
Markate, Jobber or Housecall Pro. Customers, addresses, notes and history.
Read the field mapping
See which old field lands where, and what has no home, before anything is written.
Run the dry run
A rehearsal in a sandbox copy with counts, warnings and a list of anything unmapped.
Cut over, or reverse
Commit the import, or roll it back as a single group.
The reverse is true too: you can export everything out of Apex, including attachments and history, on every plan.
Questions, answered first
Which exports can I import?
Exports from Markate, Jobber and Housecall Pro. You export from the old tool and upload the file. Apex never asks for your old login.
What is a dry run?
A full import into a sandbox copy. You see every record mapped, every warning, and a count of what would change, and nothing touches your live data.
Can I undo an import?
Yes. Every import is reversible until you archive it, and it is tagged so the records it created can be removed together.
Do you keep old request history?
The goal is that nothing is silently dropped. Anything that cannot be mapped is listed in a report instead of discarded.
Is migration available today?
Importers are in build and not on sale yet. This page describes the plan.