Migrate your SuperOffice CRM data

Standard contact card object with all standard fields (name, email, phone, address, custom properties). Well-documented schema, no edition gating. We map 1:1 in most migrations.

Company record linked to contacts via the associate table. Schema is stable across all tiers. We preserve the Company-Contact relationship by sequencing Companies first in the import order.

SuperOffice uses Sale as the pipeline object, with a type-stage link table defining pipeline behavior. We preserve the sale stage, amount, and linked quote. Automations on sale stage changes do not migrate and must be rebuilt.

Project object with type and status managed via ProjType and ProjStatus list tables. Project-type-status links are preserved as custom properties in the destination if the target CRM does not support the same list-table model.

Quote root linked to one Sale; each Quote has one or more QuoteAlternative versions with line items. Discount and earning fields are tracked at the Alternative level. We map Quote structure but note that destination CRMs often lack the Quote-Alternative hierarchy and flatten to a single quote record.

Activities (calls, tasks, appointments) linked to Contact or Company records. Timestamps, duration, and completion status migrate cleanly. Activity associations to other objects require relationship remapping.

Selections are SuperOffice's named dynamic lists of Contacts, Companies, or Sales. They are not standard CRM objects in most target systems — we export them as tagged records and apply the selection name as a custom property or tag in the destination.

Documents stored in SuperOffice's document archive can be exported via section-tab export or DataBridge. We handle file exports as binary blobs with metadata, but note that document-link relationships to specific records require post-migration verification.

Custom fields on Contacts, Companies, Sales, and Projects are supported via the userDefined table structure. We map each custom property individually; dropdown lists must be recreated in the destination if they do not already exist.

SuperOffice Users have a Role controlling module-level access rights. User records include email, name, and license status. We map active users to the destination but role structures (module vs. field-level rights) are destination-specific and must be reviewed per CRM.

Tags in SuperOffice are applied across Contact, Company, Sale, and Project objects. We export tags as a comma-separated list or normalize them to a Tags object in the destination where the target supports it natively.

Pipeline stages are tied to the SaleType list table and link to specific stages. Stage names, order, and probability percentages are exported as a configuration object. We apply stage mapping at migration scoping and note that stage count limits vary by tier.