Migrating Your User Data to Scute
Welcome to our user data migration guide! This document will walk you through the process of moving your user data into Scute’s system. We’ll cover everything you need to know, from understanding how we store user information to practical examples of using our API.Understanding User Data in Scute
Before we dive into the technical details, let’s understand how Scute organizes user information. Each user in our system has two main components:Basic User Information
Every user has these fundamental attributes:- A unique identifier (UUID)
- Contact information (email and/or phone)
- Name
- Account status (active, pending, inactive, or imported)
- Verification timestamps for email and phone
Custom User Attributes
Need to store additional information about your users? We’ve got you covered! You can add custom fields with various data types: 📝 Available Data Types:string- For general text databoolean- For yes/no flagsinteger- For whole numbersdate- For timestamps and calendar datesphone- For phone numbers with validationemail- For email addresses with validationtext- For longer text contenturl- For web links
Moving Your Users to Scute
The API Endpoint
Here’s how you can create new users through our API:API Request & Response
Example Usage
CURL Example
Create User with CURL
Shell Script Example
Migration Script
Important Things to Keep in Mind
Data Validation
- Email addresses must match standard format
- Phone numbers should be in international format
- Custom fields must match their declared types
Security Best Practices
- Always use HTTPS for API calls
- Keep your API keys secure
- Handle personal information with care
Tips for a Smooth Migration
- Back Up Your Data: Always keep a backup of your source data before starting
- Start Small: Test with a small batch of users first
- Verify as You Go: Check each batch after migration
- Monitor Progress: Keep track of successful and failed migrations