Oblyss Logo
Sign In
Get Started
Oblyss Logo
Get Free Trial
Sign in
Data Migration & Onboarding

Switching software should not mean starting from zero.

Ten years of customers, jobs, and warranty records do not live in your head. They live in a spreadsheet, an old CRM, and a filing cabinet. Moving to Oblyss brings that history with you, drops it onto a foundation repair pipeline that is already built, and puts a real person next to your team while you learn it.
Book guided onboarding
Onboarding Checklist
Import by CSV, lead API, or a one-time MarketSharp, Salesforce, or Go High Level data migration, included in the onboarding and data migration package.

Onboarding checklist

Bedrock Foundation setup

4 of 6 steps complete

Team members added

Done

Locations & timezones

Done

Supplier catalog imported

Done

18-stage pipeline

Preloaded

Customer & job import

In review

Invite technicians

Up next
Why crews stay stuck

The reason you have not switched is not the software. It is the move.

You already know your current setup is holding you back. The estimates live in one app, the schedule in another, the customer history in a scheduler’s memory. What keeps you on it is the fear of the changeover: the week nobody can find a job, the leads that fall through the cracks, the warranty someone swears was on file. Foundation repair makes that fear bigger than it is for most trades. A customer from four years ago calls because they are selling the house and the buyer wants the warranty. If that record did not come across in the move, you are digging through email at nine at night. The history is not a nice-to-have. It is the job. So the move has to protect three things: the contacts you have sold to, the jobs you have completed, and the warranties you are on the hook for. Get those across cleanly and the rest is just learning where the buttons are.

What a clean move looks like

Your customers, jobs, and open work come across. You land on a foundation repair pipeline that is already set up, not a blank board you have to invent. Your supplier costs and margins are loaded so the first estimate you build is priced right. And someone walks your office and your techs through it before you trust it with a live lead.
Getting your data in

Three ways in, depending on where your data lives now.

Some of it is in a tidy export. Some of it is in a platform built for a different trade. Some of it is still arriving as fresh leads while you switch. There is a path for each.
CSV upload

The spreadsheet you already have

Export your customers and jobs to a CSV and upload them. Fields map to Oblyss contacts and job records, so the office can pull up a homeowner from day one instead of starting a fresh database.

Lead ingestion API

Leads that keep coming

Generate an API key and ingest URL and point your sources at it. New leads from Angi, Meta, Google LSA, your website forms, or a Zapier or Make automation land straight in the pipeline while you finish the switch.

Platform migration

Coming off another CRM

Moving off MarketSharp, Salesforce, or Go High Level? A one-time data migration, included in the onboarding and data migration package, extracts your records from the old system and imports them into Oblyss, so your history moves with you rather than getting left behind.

Prefer to key in a handful of active jobs by hand and start fresh on the rest? That works too. Most companies do a mix: a bulk import of the customer list, a migration of the open jobs, and the lead API switched on so nothing new slips past during the change. Want the full field-level detail? See the integrations page.

The migration, step by step

Your old CRM does not get the last word on your data.

A platform migration is a one-time move. Your records are read out of the old system and imported into Oblyss, mapped to the right fields: contacts to contacts, jobs to jobs, notes to the activity log. You review what came across before it goes live, so nothing surprising shows up in front of a customer.

We do not put a stopwatch on it and promise you a number of days, because the honest answer depends on how much data you have and how clean it is. What we do promise is that you see exactly what imported and sign off before your team works out of it. A MarketSharp, Salesforce, or Go High Level move is a one-time data migration, extract and import, not a live two-way sync or integration. It’s part of the onboarding and data migration package, so plan the cutover with that in mind.

  • Field mapping so customers, jobs, and notes land in the right place, not a junk drawer.
  • A review pass before go-live, so you confirm the import before it faces a customer.
  • Lead API running in parallel, so new business keeps flowing during the switch.

Import review

Awaiting sign-off

Contacts imported

1,842 ready

Jobs imported

2,310 ready

Warranty records

604 attached

Rows needing a look

37 flagged
Status Awaiting your sign-off
You do not build the pipeline

It arrives already shaped like a foundation repair job.

Most software hands you an empty board and a blinking cursor. You are supposed to know, on day one, every stage a job passes through. Oblyss ships with a default 18-stage foundation repair pipeline, grouped by phase, with stage gates that stop a job from jumping ahead of itself. It reflects how these jobs actually run, from the first inspection to the final draw.

It is a starting point, not a straitjacket. Rename a stage, recolor it, reorder the board, or add one that fits how you work. Everything you change stays wired to the parts that depend on it, so a milestone draw tied to a stage still fires when you rename that stage. Dig into the mechanics on the pipeline and workflows page.

  • 18 stages, preloaded and grouped by phase so the board reads like your real process.
  • Editable defaults for stages, payment schedules, and callback rules.
  • Supplier costs loaded so your first estimate is priced on real margins.

Default FR pipeline

Foundation Repair

Lead · Inspection Scheduled

Pre-Production

Estimate Sent · Contract Signed

Pre-Production

Permitting · Scheduled

Pre-Production

In Production · QC

Production

Final Draw · Warranty Issued

Close-out

Close
Out

Complete
Guided onboarding

What the first setup actually covers.

You are not dropped into an empty account with a help article. Onboarding walks the setup in an order that makes sense, so the platform is ready before your first live lead hits it.
01

Add your team and set roles

Invite owners, schedulers, CSRs, and techs. Each role sees only what its job needs, so a tech does not land in your financials and a CSR does not see revenue they should not.

02

Set up your locations

Add each branch with its address and timezone. Running more than one office? See how multi-location management keeps each branch on its own calendar and reporting.

03

Load your catalog and margins

Import your supplier products and set sell prices from your real costs, so estimates are priced on your margins from the start rather than guesses you fix later.

04

Confirm the pipeline and schedules

Adjust the preloaded 18-stage pipeline, set your default payment schedule and any per-state draw overrides, and turn on the callback rules you want.

05

Import your history

Bring in customers, jobs, and warranties by CSV or migration, review the import, and switch on the lead API so new leads keep arriving.

06

Train the team and go live

Walk the office and the field through their day, book the first real appointment, and invite technicians to install the field app on their phones.

A guided onboarding package covers this setup with the Oblyss team, and optional training sessions go deeper on pipeline, catalog import, and how your crews use the platform in the field.
After you are live

The training does not walk out the door with the setup call.

A new hire starts in three months and needs to learn the system. A feature you skipped at launch suddenly matters. The help does not disappear the day you go live. A built-in learning center holds walkthroughs and foundation repair knowledge articles you can search from inside the app, and an in-app assistant sits in the corner to answer setup questions as they come up.

When the platform ships something new, a What’s New panel tells you what changed and why, so your team is not the last to find out a feature they wanted is already there.

Bring your questions to the call

Every foundation repair company is a little different: the states you work in, the way you draw milestones, the mix of residential and commercial. The onboarding call is where we map your real setup, not a generic one. Come with your current workflow and your messiest job, and we will show you where it lands in Oblyss.
Book onboarding & import
The questions owners ask before they switch

Frequently asked questions

How do I get my existing customers and jobs into Oblyss?

Three main ways, and most companies use a mix. Upload a CSV export of your customers and jobs, or run a one-time data migration from MarketSharp, Salesforce, or Go High Level, included in the onboarding and data migration package or key in a few active jobs by hand. Whichever path you take, you review what came across before it goes live.

It depends on how much data you have and how clean it is, so we do not quote a fixed number of days up front. What stays constant is the process: your records are imported, you get a review pass to confirm everything landed correctly, and you sign off before your team works out of it. Bring your data volume to the onboarding call and we will scope it with you.

That is exactly the record you cannot afford to lose, so it is part of the import. Completed jobs and their warranties come across and attach to the customer, so when a homeowner calls at resale, the warranty is on file where anyone on your team can find it. Read more on warranty management.

No. Oblyss ships with a default 18-stage foundation repair pipeline, grouped by phase with stage gates, so you start from a board that already matches how these jobs run. You can rename, reorder, add, or remove stages to fit your process, and the changes stay wired to milestone billing and automations.
Yes. Generate an API key and ingest URL and point your lead sources at it, so leads from Angi, Meta, Google LSA, your website, or a Zapier or Make automation land in the pipeline during the changeover. Nothing has to pause while your history imports.
No. MarketSharp, Salesforce, and Go High Level are each supported as a one-time data migration, included in the onboarding and data migration package: your records are extracted and imported into Oblyss. There is no live sync or ongoing integration, so plan a clean cutover rather than running both systems in parallel long term.
Guided onboarding walks your setup with the Oblyss team, and optional training sessions go deeper on pipeline, catalog import, and field use. After go-live, an in-app learning center and assistant answer day-to-day questions, so a new hire three months from now can get up to speed without a separate call.
We map your real setup: your locations, your states, your draw schedules, your catalog, and your open jobs. It is not a generic tour. Bring your current workflow and a messy example job, and we will show you where each piece lands so you can see the move before you commit to it.

Bring your history. Skip the blank page.

Book a guided onboarding and data import session, and we will scope your move, map your data, and set up a foundation repair pipeline that is ready before your first live lead.
Book onboarding & import
Start a free trial