How to import organizations and end users into Syncro
Check Syncro's dedicated source-specific importers first. When a CSV workflow fits your source, use the organization and end-user templates, verify parent IDs and required fields, then review the import results.
Prepare Syncro CSV imports for organizations and end users, map required fields and IDs, avoid duplicates, and review import results before a migration cutover.
On this page
Check dedicated importers first
The Syncro import and export comparison links current module CSV tools and source-specific importers; review each tool before mapping records manually.
Syncro's migration hub links distinct tools. Use the Atera-to-Syncro guide for that source. The Autotask importer handles selected PSA accounts, contacts, tickets and notes; it is intended for a fresh Syncro account and warns about duplicates when a customer database already exists. The ConnectWise importer handles selected PSA companies, contacts, tickets and notes with API credentials and a Client ID. These are not Datto RMM or ConnectWise Automate/RMM history imports.
Syncro's Ninja deployment script installs agents using matching organization/customer names. It is separate from historical-record transfer. Native tool availability does not mean RMMBackup supports every source product named here.
Syncro may label these records Customers/Contacts or Organizations/End Users. Match the template to the labels in your account.
Import organizations first
Syncro's organization CSV workflow starts at Admin > Customers - Customer Import and provides a Complete CSV template. A new organization import must populate at least two of the documented identity fields: first name, last name, business name, email, and phone. Account-level required fields can block imports, so review those settings before preparing the file.
Use Syncro's current template and column reference. Keep the source export unchanged, transform a copy, and place custom values only in the documented format. Review names, email addresses, and phone numbers carefully because Syncro uses identifying fields when mapping records and duplicate data can produce incorrect matches.
Map end users to organizations
End users depend on an existing organization. Syncro's End User template includes customer_id for that relationship and contact_id for an existing end user. Leave contact_id blank for a new end user; preserve it when the documented goal is updating an existing record.
Download a fresh end-user template from the target account. Do not change its headers, and verify each organization ID before upload. Syncro documents using one file for multiple organizations when the correct customer_id appears on each row.
Review results and prevent duplicates
After an organization import, review Admin > Reports > Import Results. Syncro's official troubleshooting guidance calls out missing or changed headers, missing required identity data, invalid formatting, extra spaces, required account fields, and UTF-8 errors. Correct rejected rows in a new working copy and retain the result report.
Test with a representative sample before a full import. Compare accepted rows with records in Syncro, then verify organization relationships, end-user contact details, custom fields, and duplicate behavior. Do not treat a completed job message as field-level validation.
Move managed assets through the documented workflow
Organization and end-user CSV imports do not recreate a managed RMM device with its old operational history. Syncro documents separate migration tools and agent deployment methods for moving assets from another RMM. Create or import organizations first, then follow the applicable official asset migration and installer instructions.
For an Atera source, use the Atera-to-Syncro migration guide. For other sources, pair the RMM migration checklist with current Syncro migration documentation.
Keep imports separate from historical backups
RMMBackup does not write organizations, end users, or assets into Syncro. Its Syncro integration backs up supported source records as read-only history and provides snapshot ZIP downloads. Keep source exports and RMMBackup history for fields, configuration, and events that the destination import does not accept.